I am evaluating CSSC and want to lock down the client so users can't disable the client, wireless, or add new networks. I currently do this with ADU but want something I can distribute settings easier. Everything else about CSSC has met my expectations except the locking down of settings.
By selecting Configurable Client as the Client Type on the Station Policy, end users can define their own networks. Administrators can control the types of networks that the end user defines using the Network Policy, Wi-Fi Policy, and Authentication Policy categories. During the deployment, administrators define the "work" network and copy these files to the end users' workstations. As part of the client deployment, the access profile entitled "work" is automatically locked, and end users cannot modify them. Additionally, end users can create new networks within the policy boundaries set by the administrator.
Is "Configurable Client" a setting in the management program? Basically I want to setup the networks and users can't add, modify, or delete networks. Also I don't want them to disable the client or wi-fi radio which right now they can under settings in the clients.
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...