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]]
[GroupPrex=<prex>]
[GroupKey=<hashkey>]
[MQTTServer=<mqtt_address>[:<mqtt_port>]]
[AdvancedCong={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 — Species 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 specied, it is saved in
the non-volatile memory. Default port is 80.
For example, CCMEnable=yes CCMServer=http://xxx:8080.
GroupPrex and GroupKey — The options GroupPrex and GroupKey
compose the group code of the Cloud Client Manager server. Once
specied, it is saved in the non-volatile memory.
MQTTServer — Species a IP address or URL address for the MQTT
server and MQTT port after the : (colon). Once specied, it is saved in
the non-volatile memory. Default MQTT port is 1883.
AdvancedCong — Default is no. Yes/no option to enable the Cloud
Client Manager server and MQTT server elds in the GUI. If
AdvancedCong=yes is specied, 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 Congure Cloud management dialog will
display during boot up. If CCMDefault=yes is specied and both the
CCMServer and GroupKey are NULL, the Congure 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 specied, 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
dierent places you can congure the group key in order of priority that is
if #1 is dened it will override #2 etc.
1 Local GUI conguration or groupkey received from CCM in a Group
Change command
2 Dened 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 eect, if CCM is
currently disabled,or if CCM is enabled but group-key is NULL.
• If DCHP is dened and CCM is enabled or not NULL: The CCM Group
key in the DHCP is ignored since it is congured manually in local UI or
from CCM group change.
• If INI is dened and CCM is enabled or not NULL: The CCM Group
key in the INI is ignored since it is congured manually in local UI or
from CCM group change.
Creating and Using xen.ini Files
181