- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Standard User cannot connect to Wi-Fi with Meraki Cloud Authentication Security
Hello,
i've encountered a pretty strange issue with Meraki SM.
I've configured a SSID security as "Enterprise with: Meraki Cloud Authentication", and assigned a tag to computers (generic tag, called WIFI_Access) .
All computers with that tag can access the Wireless network without any issue, but specifically Windows computers have this issue: Administrator users can connect without any issue, while Standard users cannot connect.
If I connect from Admin user, then switch to Standard, the WiFi stays connected (Using Win + L), but if I disconnect and reconnect from the guest user, the connection fails and Windows says "Unable to connect to this network".
I could not find a solution online, if anyone knows anything about it, please help.
Thank you!
Solved! Go to solution.
- Labels:
-
SSID
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello.
by Meraki Tech Support:
On Windows the certificate will install in the current user that is connected at the moment of the installation of the agent.
For anyone that needs information:
- Create the employee's user as Admin
- Install Meraki agent and configure the computer as the Employee's admin
Extra Steps if you have standard users on your computer, like me:
- Wait for Meraki installations to be completed.
- Create an extra Admin User (itsupport, adminuser, whatever)
- Revoke Admin Permission from the Employee's user.
This solves the issue. Only con is that if you have a Wi-Fi configured to be accessed by Meraki Tag, you will be able to connect to it only as your Standard User (the employee) and not while logged in the Admin User.
That should not be an issue considering that you'd use the Admin User only to give permissions to the Standard Users every now and then whenever they need to install/unlock something.
Hope this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is an MDM setting that can disallow regular users from connecting to non programmed SSIDs:
You can also do similar in GPO, this is old but basically still applicable: https://www.grouppolicy.biz/2010/03/how-to-use-group-policy-to-blackwhite-list-wireless-networks-in-...
I'd think perhaps something like that is programmed
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
thank you for your reply,
i was trying to reach here Device/Vendor/MSFT/Policy/Config/Wifi/AllowWFAQosManagementDSCPToUPMapping
but I have no idea what this path is...
Doesn't look like regedit or GPO.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello.
by Meraki Tech Support:
On Windows the certificate will install in the current user that is connected at the moment of the installation of the agent.
For anyone that needs information:
- Create the employee's user as Admin
- Install Meraki agent and configure the computer as the Employee's admin
Extra Steps if you have standard users on your computer, like me:
- Wait for Meraki installations to be completed.
- Create an extra Admin User (itsupport, adminuser, whatever)
- Revoke Admin Permission from the Employee's user.
This solves the issue. Only con is that if you have a Wi-Fi configured to be accessed by Meraki Tag, you will be able to connect to it only as your Standard User (the employee) and not while logged in the Admin User.
That should not be an issue considering that you'd use the Admin User only to give permissions to the Standard Users every now and then whenever they need to install/unlock something.
Hope this helps.
