I have been through the ringer resolving several different issues with instant clones. I thought I'd share some of my Lessons learned and some helpful reading. I have only used Instant Clones, and do not have a composer server installed. I can't speak for composer problems.
On your image the registry location for the Horizon client is:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\vmware-viewcomposer-ga
ClonePrep Script logs location:
c:\windows\Temp\vmware-veiwcomposer-ga-new.log
cloneprep.debug.mode ON
This is supposed to leave your failed clone running so you can troubleshoot it. Personally have not been able to make this work but your mileage may vary. Would be very helpful to keep a failing image open while you troubleshoot. I have had to race into console right after creation and do what troubleshooting I could before restart.
Generate a support log bundle from instant clone:
Program files\VMware\VMware View\Agent\DCT
Run support.bat to generate large log bundle
running with loglevels as an argument will allow you to change log detail.
I have not found this to be too useful, mostly collects a bunch of windows system information and logs along with agent logs. But it is a resource.
A good reference document that reviews the instant clone creation process:
STUCK IN CUSTOMIZING:
- Clone Prep tries to activate windows. If it fails, it will not complete customization. Using the registry key above in your master image set : SkipLicenseActivation to 1. One interesting point here is even after setting this, the vmware-veiwcomposer-ga-new.log file still shows the activation attempt and failure. It appears to still try but will not hold up activation. Looking at the log file you have no way of knowing that activation is being skipped. Log file acts just the same if you were trying to activate.
- FIPS-140 mismatch. When you install the connection server and the client agent there is an option for FIPS-140 encryption. Agent and server need to match. With mismatch the Instant Clone completes but stays stuck in Customizing. For this one you just have to know how FIPS is set on server and agent. I have not found any log file or notification that would lead one to identify what is going on.
- DHCP, not 100% on this, need to restest but I had a image with static DNS set, simply changing to dhcp, fixed. It possible everything needs to be DHCP. Don't quote me on this one as I have not gone back and confirmed.
TIDBIT:
Windows event log:
- With fully functioning Instant clones, I get 5805 errors for all internal template clones on the DC.
That's all for now, I hope this is helpful to some.