We've got a WPA2 secured network that we are having this trouble with in Windows 7 on a fairly widespread basis. The profile just disappears and the users are left with no network connection. Thus, when they call the help desk, their computer is offline and cannot be remotely connected to.
Well, to help remedy this I've exported the wireless profile to a .xml file and created a script with the following:
netsh wlan add profile filename="Wireless Network Connection Name.xml"
However, for some reason, on some of the laptops, it creates the profile but when attempting to connect to it, it still prompts for the security key (although it is in the .xml file). This effectively makes the script useless, as we don't really want to give that out to all of the users.
Anyone know what's going on here?