ZCM 11 SP3 Agent registration with non-persistent VMware View 5.3 VDI Desktops

ZCM 11 SP3 Agent registration with non-persistent VMware View 5.3 VDI Desktops

We want to use ZENworks Configuration Management to manage our Windows 7 FAT desktops and VDI desktops. In our environment we were struggling to get our non-persistent VMware Windows 7 desktops registered in the ZCM Zone. After the Quickprep process (VMware KB) some desktops did not register or registered with an extra guid in the machine name. Both resulting in an unmanageable device without the associated ZCM icons (bundles) on the desktop. After trying many different potential solutions (cleaning parent, logon scripts etc.) to correctly register the devices, we came up with a permanent solution. Register the desktop with a VMware Post-synchronization script and use an agent with custom deployment settings.

ZCM and Vmware View settings in a couple of steps:

1 - Device folder ZCM
Because we do not need all the agent features in our VDI desktop. We added a new device folder for the (stateless) VDI desktops and selected the agent features needed.

1

2 - ZCM Registration key
To register the desktops in this folder we defined a registration key:

2

3 - ZCM Reconcile setting
After the user has logged out, the desktop will be deleted and recomposed.
The recomposed desktop is unique with exception of the hostname, so ZCM has to re-use (reconcile) the device object on hostname. Set the reconcile setting on “Machine name” and enable Differentiation.

3

4 - Deployment package ZCM agent
We do not want to use the build-in deployment packages (https://zenworksserver/zenworks-setup) because they register to the ZCM zone after installation or on first network connection. When using the build-in package the agent get registered in the VMware View composing process or when updating the parent if there is a network connection.

We added a deployment package without a server (delete all entries) and installed the agent in our parent image.

4
 
4-2

5 - VMware Post-synchronization script.
In the Pool settings from the View Administrator we added the following Post sync script (VMware KB😞

script name: zac
script parameter: reg –g –u username –p password https://servername.fqn - k VDI

We added the "Zenreg" user in ZCM with minimal rights to process the registration.

5

Now we can compose the VDI desktops!

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Comments
Hi Maarten, Great post!

Interesting to know is that the upcoming ZCM 11.4 release will allow you to set the reconciliation on the registration rule or key so it will be more flexible to work with both VDI and traditional desktops
Great post and good explanation
We also use ZCM to manage our VDI-Clients. We use other process for VDI-Client lifecycle, but it works also. I have a question about a problem we have with ZCM-Agent and VDI.
If a ZCM-Agent are installed the reconnect to a active VDI-Session is only from the same Device (zero-Client or Horizon-Client on a FAT Client) possible. If you switch to another Devcie and want to reconnect, the VDI-Client Session close and open a new Session on another VDI-Client. Our VDI-Clients are also non-persistent.
Have you try this szenario?
Hi!
With the ZCM-agent installed it's possible to proceed with a VDI session on another device. We have not seen your problem in our environment.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2015-02-18 19:12
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.