i have been trying for a couple of weeks now to try and deploy WEP keys to a windows 7 test machine. i have gone and tried to find some way of deploying them and thought i had it figured out by using a script. but either the script or something else is not working with each other. here is what i do for the script. netsh wlan export profile name=”CorpWIFI” ' It will make a file called Wireless Network Connection-CorpWIFI.xml and copy to the c drive netsh wlan add profile filename=”C:\Wireless Network Connection-CorpWIFI.xml” netsh wlan connect CorpWIFI after i do this it completes fine but it asks for the wep key. i have looked on various forums and i can not get this to work. any help would be great. i have tried on 3 different machines and all do the same thing.

Why not set this up via GPO? http://www.petri.co.il/creating_wireless_gpo_settings.htm http://www.enhansoft.com/

I concur with Garth on this one (and many others also, just not PowerShell): GPOs are the way to go. The problem with your approach is that you are setting up the wireless profile for the SYSTEM account which is what the task sequence is running as. Wireless profiles are not shared between accounts. Thus, you would have to actually run your script for each user that logs on which is doable using the "user run once" functionality of the registry but is more work that just using a GPO.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

SCCM run script with SYSTEM account, but WEP is user based. GPO is a recommended way. Thanks.

i have tried with what you said to do and it still doesnt work. the GPO only allows me to place the SSID and thats all no WEP key, i require the wep key installed as well. Thnaks Jeff

One point that I overlooked in all of this is why are you using WEP? WEP is no longer considered secure and can easily be cracked by an 8 year old. Here's a decent with some further info: http://social.technet.microsoft.com/Forums/en-US/winserverGP/thread/e74496e2-75fb-4403-8f4c-67fc8a3a95b2. But going back to the original problem, you will have to do what I suggested above, run the script using the user run once registry key so that it gets imported by every user that logs into the system.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

If you export the profile with the key=clear option it will work, if you don't it will only work on the machine you exported it from.