The workaround is to manually create the network profile, setting it to use WPA2-Enterprise, then use the command line to fix the profile.
Note: There have been reports of Android devices corrupting network profiles; when this happens, the device keeps trying and failing to connect to FVCCNET.
I can't figure out why I can't get it up and running now.It can find the network fine, but when I try to connect, I don't get the password prompt -- it moves straight to "validating identity," scans, and then says "Windows was not able to find a certificate to log you on to the wireless network Foo." The maddening thing is that the card was working fine a week ago, in the same box, using the same OS.I pulled everything out, swapped out the motherboard, and reinstalled Windows on a freshly wiped hard drive, and now I can't get it up and running again. I've taken several runs at it, including attempting to manually change the settings for the network to include WPA-PSK and AES and the password, and I'm a bit worried that I've totally boned everything.In order to connect to FVCC's wireless network, you will need your FVCC Logon ID (aka. If you don't know your FVCC Logon ID and password, please bring a photo ID to MIS.This document is long, but you only need to read the section for the type of device you're trying to use to connect to the network.