Follow

Provisioning of VMware Instant Clones Fails When Using ProfileUnity Client

Product: ProfileUnity-FlexApp

Product Version: 6.5+

Expires on: 365 days from publish date

Updated: March 29, 2018

 

Problem/Symptoms:

VMware Instant Clone VMs will not provision correctly when ProfileUnity Client is present on the VDI base image, or machines will provision, but "black screen" on boot/otherwise not boot properly.

 

Possible Resolution:

The WMware Instant Cloning process injects the default Windows "userinit" value of C:\windows\system32\userinit.exe into the cloned VM at boot, which overwrites the necessary ProfileUnity userinit value of C:\Program Files\ProfileUnity\userinit.exe. To correct:

 

1) Because this happens at machine provisioning/boot, this must be corrected via a GPO Registry object. Open up the ProfileUnity GPO in the Group Policy Management Console

2) Create a new Computer Policy Registry object to be applied by the GPO. Make it look like the following screen capture:

 

NOTE: The "Key Path" should be "Software\Microsoft\Windows NT\CurrentVersion\Winlogon"

NOTE: The "Value Data" entry should be ""C:\Program Files\ProfileUnity\userinit.exe","C:\Windows\system32\wininit.exe","C:\Program Files\VMware\VMware View\Agent\bin\vmlm_helper.exe","C:\Program Files\VMware\VMware View\Agent\bin\wssm.exe","

3) Save the addition to the GPO.

4) Push/reprovision the new Instant Clone pool. The provisioning should work, and the VDI machines should now boot correctly.

 

 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Article is closed for comments.