Does anyone have any suggestions for allowing temporary profiles to be created by end-users?
Currently we are using the Cisco ACU software to control the wireless configuration on our laptops, but this is "hidden" from end users (they are unaware of the utility and it has been removed from their program menu options) because we don't want them to mess with the configuration or profile settings.
However, with users becoming more aware of Wireless Hotspots, they are starting to demand the ability to make use of these. The downside to this is that SSID values will vary from hotspot to hotspot and so users will need the ability (albeit limit) to create or modify a "Hotspot" profile.
Is this possible by either :
a) protecting the existing profiles (make read-only) and allowing new profiles to be created
b) limiting access to areas of the ACU
c) using a third party application (other than Windows as we don't want them touching network properties) to add or edit a profile.
a is the best option just make sure you use auto profile selection to save problems there
*most* hotspots use broadcast ssid and open authentication so based on that you could make a new profile for them that has no ssid and all defaults this would work in a lot of hotspots then if you have a list of common hotspots then you could add them
Maybe if you want to keep this locked down at a corporate level you do a deal with a set hotspot provider and give your users that profile it is kinda a compromise
Transferring Crash file from standby: Login to the Active WLC in HA.
From CLI: (Cisco Controller) >transfer upload datatype crash (Cisco
Controller) >transfer upload filename (Cisco
Controller) >transfer upload mode tftp (Cisco Controller) >transfer
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 f...