Windows 10 WiFi Not Connecting Automatically To Ruckus via RADIUS

[Colindean2000]

We think a recent change to Windows 10 has stopped our Windows 10 laptops from connecting automatically to our Ruckus system...

 

Some context:

We have had for a number of years been using RADIUS from one of our DCs and a WiFi network called Restricted on our Ruckus wireless system and an inline filtering appliance. Laptops that are in a particular security group are allowed to join this WiFi network automatically and it works, it works without issue on Windows 7 clients and was working with Windows 10 clients too until recently.

 

Now Windows 10 clients wont connect automatically to the WiFi upon boot causing them to not process group policy and they sit on the 'Applying Settings' message for a long time before giving up.

 

It seems to be that Windows 10 now checks if there is an Internet connection before it will auto join the WiFi network and where we use an inline filtering appliance, machines do not get the Internet until a user logs on and is authenticated.

 

I've tried allowing msftconnecttest.com via the filter to all machines in the hope that in the background the machine would check if this is available and allow the connection to the WiFi network but this does not seem to have fixed it.

 

Has anyone else had experience of this in a similar set up to us? any suggestions would be most appreciated!

 

Thanks.

[RLR]

We think a recent change to Windows 10 has stopped our Windows 10 laptops from connecting automatically to our Ruckus system...

 

Some context:

We have had for a number of years been using RADIUS from one of our DCs and a WiFi network called Restricted on our Ruckus wireless system and an inline filtering appliance. Laptops that are in a particular security group are allowed to join this WiFi network automatically and it works, it works without issue on Windows 7 clients and was working with Windows 10 clients too until recently.

 

Now Windows 10 clients wont connect automatically to the WiFi upon boot causing them to not process group policy and they sit on the 'Applying Settings' message for a long time before giving up.

 

It seems to be that Windows 10 now checks if there is an Internet connection before it will auto join the WiFi network and where we use an inline filtering appliance, machines do not get the Internet until a user logs on and is authenticated.

 

I've tried allowing msftconnecttest.com via the filter to all machines in the hope that in the background the machine would check if this is available and allow the connection to the WiFi network but this does not seem to have fixed it.

 

Has anyone else had experience of this in a similar set up to us? any suggestions would be most appreciated!

 

Thanks.

 

A similar thread was posted a while back that sounds like a similar thing. This is the fix:

 

http://www.edugeek.net/forums/windows-10/190222-windows-10-1709-nps-wireless-policy-issues-2.html