Jump to content

Recommended Posts

Posted

We are currently having an issue with our MS Surface Go tablets not automatically connecting pre-login to our Unifi Radius secured SSID. If we click to connect the device, it shows a status of "action needed", yet will connect no problem.

 

I'm struggling to find our why it will not auto-connect, and what the "action" is ti thinks is needed.

 

This is starting to cause a major headache for our SLT as they are not getting the right policies applied and drives mapped if they haven't manually re-connected to the network.

  • 3 months later...
Posted
We have a similar problem with our Surfaces not connecting to our Ruckus running WiFi 6. We have had to create a downgraded SSID running WiFi 4 to get them to work. No research has yet uncovered how to fix it and we've done things like downgraded the driver settings, rolled back the Intel AX201 driver etc.
  • 1 month later...
Posted

I have recently had this, with a different device, but mine turned out to be a setting in group policy.

 

In the Group Policy that allocated your wireless SSID policy go to

 

Computer configuration >Policies > Windows Settings > Security Settings > Wireless Network (IEE 802.11) Policies

 

When here double click on your SSID/Wireless Network Name

 

In the General Tab Select Your Profile Name and click edit (or double click on it)

Wifi1.png

 

In the security tab, click on the properties button next to "Microsoft: Smart Card or other certificate"

Wifi2.png

 

In the Trusted Root Certification Authorities section, scroll to your Certificate Authority issuing the certificate and tick it (this was not a requirement until recently and raises it's head in a recent windows 10 update and in windows 11)

 

Wifi3.png

 

OK and save everything and then do a GPUpdate /Force on the machine.

 

Let me know if this does work for you please :-)

  • Thanks 4
Posted
Also if you list the servers that are doing NPS when we setup windows 11 we found that because in the GPO we did servername.domain.lan but the actually certificate issued was SERVERNAME.domain.lan Win 11 wouldnt auto connect... win 10 had no issues... so just make sure the names match case sensitivley.
  • Thanks 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...