Hi All,
We have CISCO enterprise level WAPs (1142 upto 3602 models) across multiple sites (lets say 20 sites for this scenario). These WAPs all advertise the same 2 networks, we'll call them INTERNAL and EXTERNAL.
Devices owned by us and issued to users are on the INTERNAL network via a certificate and AD object, devices not owned by us connect based upon the users credentials to the EXTERNAL network (phones tablets etc) - and get put directly to the internet via our proxy/firewall setup and have no access to anything internal.
Now, for our Windows devices certificated to the INTERNAL network we have a Group Policy Object which prevents their connection to the EXTERNAL network.
Our MAC OSX 10.9.x devices also certificate onto the INTERNAL network - however, users can opt to connect these to the EXTERNAL network due to a lack software level policy to prevent it.
This causes headaches for IT support, as users then complain printers/mounted shares/internal only sites don't work.
We can't easily manage MAC addresses for the fleet (keeping track of MAC addresses across 20 sites is far too involved), and we outsource management of our controllers anyway which means on site techs don't have access to blacklist/whitelist MACs on a whim.
What I am looking for is a profile based lock down to the wireless to prevent users connecting to networks named EXTERNAL, not a DHCP change, not a controller level change - I am hunting for a client OS level fix, that straight up hides the EXTERNAL name, or otherwise gives them a message that connection to it is disallowed by their administrator.
So far google has turned up nothing but users who once connected to a network and don't know how to disconnect themselves.. And a few people suggesting that we push a dummy profile that then fails, which is just an ugly response to what should be a cleanly resolvable fault.
Lastly, users need to maintain ability to connect to other networks, for when they take their laptops home.
I tried a forum search, and a google search on this site - I found one relevant topic: https://forums.macrumors.com/archive/index.php/t-817755.html (didn't want to necro it) and it was dealing with someone who lacked the enterprise level system we have.
Thoughts.. ideas? all welcome.
Cheers,
/Glaic
We have CISCO enterprise level WAPs (1142 upto 3602 models) across multiple sites (lets say 20 sites for this scenario). These WAPs all advertise the same 2 networks, we'll call them INTERNAL and EXTERNAL.
Devices owned by us and issued to users are on the INTERNAL network via a certificate and AD object, devices not owned by us connect based upon the users credentials to the EXTERNAL network (phones tablets etc) - and get put directly to the internet via our proxy/firewall setup and have no access to anything internal.
Now, for our Windows devices certificated to the INTERNAL network we have a Group Policy Object which prevents their connection to the EXTERNAL network.
Our MAC OSX 10.9.x devices also certificate onto the INTERNAL network - however, users can opt to connect these to the EXTERNAL network due to a lack software level policy to prevent it.
This causes headaches for IT support, as users then complain printers/mounted shares/internal only sites don't work.
We can't easily manage MAC addresses for the fleet (keeping track of MAC addresses across 20 sites is far too involved), and we outsource management of our controllers anyway which means on site techs don't have access to blacklist/whitelist MACs on a whim.
What I am looking for is a profile based lock down to the wireless to prevent users connecting to networks named EXTERNAL, not a DHCP change, not a controller level change - I am hunting for a client OS level fix, that straight up hides the EXTERNAL name, or otherwise gives them a message that connection to it is disallowed by their administrator.
So far google has turned up nothing but users who once connected to a network and don't know how to disconnect themselves.. And a few people suggesting that we push a dummy profile that then fails, which is just an ugly response to what should be a cleanly resolvable fault.
Lastly, users need to maintain ability to connect to other networks, for when they take their laptops home.
I tried a forum search, and a google search on this site - I found one relevant topic: https://forums.macrumors.com/archive/index.php/t-817755.html (didn't want to necro it) and it was dealing with someone who lacked the enterprise level system we have.
Thoughts.. ideas? all welcome.
Cheers,
/Glaic