VMware Horizon Community
LukaszDziwisz
Hot Shot
Hot Shot

Vmware OSOT possibly causing CUstomization timeouts and long INstant clone creation

Hello Everyone,

We have recently engaged a 3rd party vendor that specializes in VDI deployment to do a health check on our environment. The number 1 issue that we are seeing is pretty high number of Customization Timeouts when publishing a pool. All those machines get eventually successfully created however this is not what we would expect. Also, once the pool is published the customization timeouts appear to be gone and machines get created properly however it takes roughly 5 minutes per one Instant Clone to be created to fulfill pool requirement ( 1 minute and 30 seconds provisioning and roughly 3 minutes customization step). I'm fully aware of VMFS 6 problems with snapshot so we moved all components, images and pools to VMFS5. We are using Horizon 7.6 and Windows 10 LTSC 1809.

The vendor is suggesting that it might be possibly due to VMware OSOT being too aggressive in disabling stuff but they cannot pinpoint to what it could be. I logged in to my master image and was hoping to simply revert any optimization done however there is nothing available in  history. We are using version b1100 of the tool.  I don't really feel like creating new image from scratch but if there is no other option then I can.

Did anybody encounter this type of an issue? Any possible solutions are very welcome.

Reply
0 Kudos
4 Replies
MrCheesecake
Enthusiast
Enthusiast

I'm not sure how much the LTSC release of 1809 has in common with the normal 1809 builds but others are also reporting delays as a result of a MS issue within Win10:

Windows10-1809 boot time takes 5-6 minutes

Reply
0 Kudos
LukaszDziwisz
Hot Shot
Hot Shot

Yeah I'm fully aware of that issue and we moved all of our images and VMs to VMFS5 until the official fix

Reply
0 Kudos
Anobix67
Enthusiast
Enthusiast

Which OSOT template are you using? A built it on, one of the templates available for download, or a customized one?

If using a general Windows 10 one, try unchecking the Windows Settings options under HKCU at the top. I remember some folks were trying to narrow down which one would cause issues, but in our 1709 build it would prevent from being published/finishing. Unchecking those boxes resolved the issue.

Reply
0 Kudos
LukaszDziwisz
Hot Shot
Hot Shot

thank you, I'll give that a shot. We did use the built-in Windows 10 one. The problem I have now is that I have no history on them and nothing to roll back. I'm not too sure why

Reply
0 Kudos