gshaw Posted January 27, 2016 Posted January 27, 2016 Just deployed an Azure AD-joined tablet to one of our staff but it seems to be the case that they have to manually connect to a Wi-Fi network each time at the login screen otherwise sign-in times out \ fails. Is this something odd with the machine I'm working on or is it default behaviour? Azure AD sign in also seems to fail with auto-detect proxy, wouldn't be surprised if this is an issue but again anyone else experiencing the same?
Michael Posted January 27, 2016 Posted January 27, 2016 I import the SSID when a workstation is first connected to the domain, using a script containing the netsh wlan command. It's all automated. After this it should remember the network and shouldn't forget it, unless there's a setting or GPO set otherwise. I can't think why else it forgets this information. 1
gshaw Posted January 27, 2016 Author Posted January 27, 2016 (edited) The only thing that may have something to do with it is the fact the device is a Linx 1010, not entirely convinced of the quality of the drivers or Wi-Fi chip reading some of the comments on the forums The proxy issue could be more problematic though... Edited January 27, 2016 by gshaw
Michael Posted January 27, 2016 Posted January 27, 2016 If you run the following command: netsh wlan show profiles It should tell you what wireless profiles it has stored.
NetworkNinja Posted July 19, 2016 Posted July 19, 2016 Good Evening Gshaw, Visit this link and it will work. well it worked for me https://community.spiceworks.com/how_to/2047-enable-wireless-connection-pre-logon-on-domain
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now