Using the AutoConfig Service, you can format fields in the Symantec LiveState Configuration Database for a managed Pocket PC, by defining templates in the AutoConfig.cfg file, located on the Symantec LiveState Configuration Server in <drive>:\ccm\config\services.
The templates may contain user-defined text, as well as variables that are substituted into the templates based on information reported by the device. You can define the following fields:
Display Name
Computer ID
Hostname
MAC Address
You can also define extended settings that the device will report.
Define the templates in the AutoConfig.cfg file. When using variables in a template, enclose names with a leading and trailing percent sign. For example:
%osname% %oem% #%autoincrement%
would result in something like PocketPC hpiPAQ h5000 #17.
Variable |
Description |
agent.name |
The name of the Symantec LiveState Delivery Agent for Pocket PC (always "wince" for Pocket PC) |
agent.version |
The release number of the Symantec LiveState Delivery Agent for Pocket PC. For example, 1.15 |
autoincrement |
The next number in the auto-increment sequence maintained by the server, in the format specified by the "AutoIncrementFormat" setting |
hostname |
The hostname if set, otherwise the device serial number |
ip |
The IP address of the device (may be "0.0.0.0") |
oem |
The manufacturer and model number. For example hp iPAQ h5000 |
option |
The published profile option selected by the device user |
os.arch |
The processor type Example: arm |
os.name |
The operating system name Example: PocketPC |
os.version |
The operating system version For example: 4.20 |
os.lang |
The selected language of the device. For example, en |
os.patch |
The operating system patch level (For example"3") |
platform |
The platform name (For example"PocketPC") |
user |
The owner name if set, otherwise the device serial number |
userinfo |
Identifying information provided by the device user in response to a prompt from AutoRun (For example, "Manager") |
In addition to the variable names that use values that are always reported by a device, you can also define extended settings that the device will report. These settings can also be used as variables when creating templates.
Each setting consists of a variable name and a registry key name. When the device reports to the AutoConfig Service, it will include the values of these extended settings in the report.
To use extended settings:
Create a text file named ExtendedSettings.cfg in the same directory as the AutoConfig.cfg file is located.
In the file, put a list of extended settings in the following form
VariableName=RegistryKey
Note: Only registry keys that have the data type REG_SZ or REG_MULTI_SZ can be used for extended settings
Use either the base class names, or the
corresponding abbreviations for the root of the registry key
paths:
Base Class Name Abbreviation
HKEY_CLASSES_ROOT (HKCR)
HKEY_CURRENT_USER (HKCU)
HKEY_LOCAL_MACHINE (HKLM)
The device will report the current values of the defined registry keys, which will be substituted for the appropriate variable names in any auto-formatting templates in which those variables are used.