Domain connected device is sending the hostname instead of username when connecting to Wi-Fi.

Question

We are facing an issue where newly imaged Windows 10 laptops fail to authenticate on our WPA2 enterprise Wi-Fi network, causing users to be unable to sign in because no Wi-Fi equals no authentication. To connect to the Wi-Fi network, authentication is required via MschapV2 and PEAP. The only workaround is to have the users sign in using an Ethernet connection first then they are able to sign in without issue from that point forward using WPA2. Here are some things we have observed:

1.) We have "WLAN-AutoConfig" enabled.  Whenever an employee clicks our Wi-Fi network, it doesn't prompt for a username and password. It simply says "Unable to connect to network" when clicking "Connect to this network". We are able to sign into other outside networks with no problem because they prompt for a username and password.

 

2.) The network team stated that Windows is sending the hostname of the device instead of the username and password when authenticating with the wireless controller.

 

3.) On the sign-in page of Windows I noticed I can click "Use my Windows user account" (I can only do this on other networks, not our WPA2). This seems to be why the computer sends the device's hostname when connecting to the Wi-Fi controller because the username it has stored is "ourdomain_hostname_$" along with a password.

 

4.) Online I read that it could be because of "Cache user information for subsequent connections" being enabled in the GPO.

 

5.) Normally clients are supposed to type a username and password. Once that is done Windows will connect to the Wi-Fi using their credentials and authenticate within AD. I wonder if maybe the order or operations is wrong and it's trying to connect to the Domain first but sends it to the Wi-Fi controller instead?

 

I've been spinning my head with this problem. Any suggestions would be amazing.

 

Thank you.