Don't really understand, but if the machines where part of an organizations domain using active directory, you can push out a group policy to have the machines only connect to a single ssid if you want. You also can set the order of preference since you still want the user to be able to add their own wireless profile for home and hotspots. You secure wireless using various methods available and what is supported by your devices. It's the client devices at the end that will choose what ssid they will connect to and that is where you have to make the decision onto your policy. If users are allowed to bring in their own devices, you have no control. Then it becomes user training on what and how they should connect to the wireless.
Creating the SSID is the easy part. The magic comes to the Security bit where you have to correctly assign the appropriate user authentication server based on the SSID.
Of course you can have a single SSID (for two or more different corporations) and 802.1x will punt or throw you to the correct authentication server but this is tough work and a lot of knowledge with scripting.
Transferring Crash file from standby:
Login to the Active WLC in HA.
(Cisco Controller) >transfer upload datatype crash
(Cisco Controller) >transfer upload filename <Desired filename>
(Cisco Controller) >transfer up...
This is the start of a display filter cross reference between Wireshark and OmniPeek.
The 1st installment is a table of advanced filters. More filters will be added as time allows.
It is a living doc, so check back for changes every so often
Please feel ...
I have created a Powershell script to automatically add a Wireless Guest User on Cisco WLCs. (tested on 2500 Series)
The script should be completely self explanatory.
Powershell SNMP Module (Install-Module -Name SNMP)
SNMP Write Access to...