Administrator Guide
Parameter Description
badge and in active grace period to authenticate with a single badge tap.
The default value is no.
CCMEnable={yes, no}
[CCMServer=<server_address>[:port]]
[GroupPrex=<prex>]
[GroupKey=<hashkey>]
[MQTTServer=<mqtt_address>[:<mqtt_port>]]
[AdvancedCong={no, yes}]
[CCMDefault={no, yes}]
[Override={no, yes}]
[CAValidation=(yes, no)]
[Discover=(yes, no)]
[IgnoreMqtt=(yes, no)]
Default is no.
CCMEnable — Yes/no option to enable the Cloud Client Manager
CCMServer — Species a IP address or URL address for the Cloud
Client Manager server. Default protocol is HTTPS. If "http://" or
"https://" does not exist, default port is 443. Once specied, it is saved in
the non-volatile memory. Default port is 80.
For example, CCMEnable=yes CCMServer=http://xxx:8080.
GroupPrex and GroupKey — The options GroupPrex and GroupKey
compose the group code of the Cloud Client Manager server. Once
specied, it is saved in the non-volatile memory.
MQTTServer — Species a IP address or URL address for the MQTT
server and MQTT port after the : (colon). Once specied, it is saved in
the non-volatile memory. Default MQTT port is 1883.
AdvancedCong — Default is no. Yes/no option to enable the Cloud
Client Manager server and MQTT server elds in the GUI. If
AdvancedCong=yes is specied, the Cloud Client Manager server and
MQTT server elds in the Cloud Client Manager UI will be enabled. See
also "PRIVILEGE=[None, Low, High] [LockDown= {no, yes}]
[HideSysInfo={no, yes}] [HidePPP={no, yes}] [HidePN={no, yes}]
[EnableNetworkTest={no, yes}]."
CCMDefault — Default is no.
Yes/no option to enable the Congure Cloud management dialog will
display during boot up. If CCMDefault=yes is specied and both the
CCMServer and GroupKey are NULL, the Congure Cloud management
dialog will display during boot up. Input group code to connect to the
default Cloud Client Manager server (us1.cloudclientmanager.com) and
default MQTT server (us1-pns.cloudclientmanager.com).
Override — Default is no. Yes/no option to allow a groupkey from the INI
le to override the previous groupkey. If Override=yes is specied, the
groupkey from the INI le will override the previous groupkey. Groupkey
priority policy is listed as below:
The Groupkey can technically be applied in many places. Below are the
dierent places you can congure the group key in order of priority that is
if #1 is dened it will override #2 etc.
1 Local GUI conguration or groupkey received from CCM in a Group
Change command
2 Dened in INI le "ccmenable=yes groupkey=xxxx"
3 DHCP Option Tag #199
The Groupkey assigned in DCHP option #199 and INI parameter are only
used for "rst time deployment" that is they only take eect, if CCM is
currently disabled,or if CCM is enabled but group-key is NULL.
• If DCHP is dened and CCM is enabled or not NULL: The CCM Group
key in the DHCP is ignored since it is congured manually in local UI or
from CCM group change.
• If INI is dened and CCM is enabled or not NULL: The CCM Group
key in the INI is ignored since it is congured manually in local UI or
from CCM group change.
Creating and Using xen.ini Files
181