Stuck On Customizing...This One Is A Little Different

[christopheralbr]

So I know this has been addressed plenty of times.  VMs are stuck on customizing and eventually timeout.  I've encountered this before, and have usually been able to remediate the situation.  This time is a little unique.

The VMs are able to provision/recompose to the point they were added to the domain, name was changed, Windows is activated and they have an IP address.  I can even console in using the web client and login with my AD credentials.  Unfortunately, the VMs are still reporting as customizing and eventually in an Error state through the Horizon Admin page.  Therefore, I'm unable to connect using our thin clients.  Any ideas?  I've provided a little more information below.  Unfortunately I will not be able to post any event logs.

Connection Server and Composer are 7.4, installed on Windows Server 2016.

Separate SQL server, installed on Windows Server 2016

Desktops:  Windows 10 1607

vCenter 6.5, installed on Windows Server 2016

I've created new pools, taken new snapshots, reinstalled the View Agent on the master template, but to no avail.  Any assistance is greatly appreciated, even if its some clues on what to look for regarding event logs.  I've seen nothing obvious when looking through events on the Composer server.

[sjesse]

Are you using App Volumes as well? I've had cases where an update to an appstack caused the firewall rules to get corrupted and remove all the firewall rules for horizon. Either way check and see if the clones have any firewall rules, if the inbound page is blank thats a sign of what I was seeing in the past.

[christopheralbr]

Thanks for the reply sjesse.  Unfortunately we are not using App Volumes.

To add, I have also tested with the firewall completely disabled on both the clones/template and the Connection Server.

[sjesse]

If you can't share logs on here you will probably need to open a SR. There is probably something in the debug log in %programdata%\Vmware\VDM\logs on the connection server and the clone,and the C:\WINDOWS\TEMP\Vmware\vmware-viewcomposer-* logs.