When I started deploying virtual machines with a vRealize Automation (vRA) based on blueprints with vSphere Templates issues started to occur. We are talking about Domain Controllers, vCenter Server, VMware NSX-V, nested ESXi Hosts, and vRealize Automation. The environment was booted successfully at first glance. This is, of course, a little bit different than a production 24×7 environment that you have in your datacenters worldwide. My Lab environment is powered-on when needed and powered-off when not needed. So how did the problem occur? First, we start with some background information. The error message that was popping up all the time was “ PBM error occurred during PreCloneCheckCallback“. The client name data may not be availableĪ few versions of VMWare do not provide the client name, so there may be limitations in UserLock: client restrictions, can't count VDI sessions as Terminal sessions.).Lately, I encountered some issues related to VMware vSAN in my Lab environment. Note that this setting will not work on limited versions of VMWare (see the "The client name data may not be available" section below). If you want UserLock to consider them as Terminal sessions, just run the UserLock Console, hit the F7 key and set the “VdiMode” property to “true” then validate with OK:
How to configure UserLock to consider VDI sessions as Terminal session typesĪdvanced note about VDI sessions: By default, VDI sessions will be considered as Workstation sessions. Create a new VDI template, which is now “UserLock Ready”.If this is not the case, restart the process from the beginning (IMPORTANT: if you do not restart the process from the beginning, the agent file will store the logon event and will continually try to notify the UserLock service and this event will be stored on future templates).Check that the session is no longer displayed in the UserLock Console / User sessions.Check that the session is displayed in the UserLock Console / User sessions.
(IMPORTANT: if you do not restart the process from the beginning, the agent file will store the logon event and will continually try to notify the UserLock service and this event will be stored on future templates).
In order to install UserLock in an environment using VDI, the UserLock Desktop Agent must be installed on the template, and correctly configured. The Wikipedia page describing VDI is available at.
Microsoft, Citrix, VMWare… are examples of VDI providers. When a user logs in, an instance of this template is created and used. Virtual Desktop Infrastructure (VDI) consists of creating a template (image) workstation. How to Install UserLock in an Environment using VDI