registration Policy Group

Desktop Virtualization › Upgrade UNIX Agents Using Software Delivery and the Individual Agent Plug-in Package › Configuration Policies for Desktop Virtualization Support › registration Policy Group

registration Policy Group

A new policy subgroup, registration, has been added under the Common Components policy group for virtual desktop-specific identification. The registration policy group contains the following policies:

Host key

Defines a string that is used to identify uniquely a cloned machine. A host key is required for linked clones because each Recompose of the virtual desktop generates a new virtual machine that registers a new unique computer in the MDB. The result is that, over time, the domain manager would see many computers that no longer exist. If the host key is used, the existing computer records for the virtual desktops in the MDB are reused over time.

A host key contains plain text plus any number of macros. On registration, CAF expands the macros and sends the result to the scalability server. The engine then uses the host key rather than the host UUID/host name/MAC address to identify assets in the MDB. From now on, the host key identifies the agent.

Note: In typical scenarios, the MAC address is not changed during the Recompose of persistent linked clones. However, in some cases VMware changes the MAC address of the persistent linked clones during the recompose operation. Therefore, the use of a host key is typically needed for both nonpersistent, persistent linked clones, and MCS-based virtual desktops as well.

Use the following macros:

Environment variable: $env(name): Example: $env(“COMPUTERNAME”)-VDI
Registry key: $reg(key,value): Example: $reg(“HKLM\SOFTWARE\CA\GuestID”,” GuestUUID”)-VDI
INI file value: $ini(path,section,key): Example: $ini(“c:\id.ini”,”identity”,”uuid”)-VDI

These macros can also be combined in the same string.

Example: $env(“COMPUTERNAME”)-$reg(“HKLM\SOFTWARE\CA\GuestID”,”GuestUUID”)-VDI

Note: By default, the CAFPostInit.dms script sets the host key on the agent with $env(“COMPUTERNAME”). Hence, you do not need to modify this policy. However, if you want to use another macro, verify that all generated host keys are unique by using the appropriate host key macro strings in the CAFPostInit.dms script. Also, verify that the host key is not more than 64 characters long.

Default: empty, <locally managed>

Scalability Servers Configuration: Allows the administrator to configure the agent scalability server, which is based on the virtual machine naming pattern that is used for the desktop pool and range. You can apply multiple ranges. This policy is optional, and if no value is set, all clones report to the same scalability server as the agent of the golden template from which they have been cloned. For more information, see scalability servers configuration.