Solved Wireless connection at login with WPA2-Enterprise

Hello,

I currently am running a server-2012 domain environment with several Windows 7 laptops. I setup a radius server to authenticate users with Active Directory to obtain a wireless connection. On each Windows 7 laptop there is a wireless profile created using "user authentication". As it stands right now, only users that are profiled can login to the laptop. Once they are profiled and they enter a username/password, it will then attempt to connect to the network, then obtain an IP address if everything is entered correctly.

What I am trying to accomplish is, for a network connection to be established prior to login. I was working on someone's laptop remotely, and one of the changes I made required a reboot. Once it rebooted, I never gained connection to the laptop, as it doesn't get on the network until logged in. Is there any way I can accomplish this? Thanks for any help you can throw at me.

-Ken

I continued to research my issue online and have figured it out. If anyone else experiences this issue, here's my resolution. Before, I had a Windows group called "wireless users" in active directory that certain users would belong to. Then, I used WPA2-Enterprise with "User Authentication", but it only got you on the network if you were already profiled, *and* if you entered the password correctly. I found that, if the password on the account was changed using a different workstation, and you put the new password in, you wouldn't be able to login to the laptop, or you would get "no logon servers available".

Basically, in the "wireless users" group, I simple added "Domain Computers" to the members, and then changed the WPA2-Enterprise to "Users and Computers" for authentication. This way, laptops will be on the network at logon, and can login with different password if it was changed, and even profile new accounts. Also, any other wireless device (ex. iPad, Android) can connect using credentials that belong to the "wireless users" group.