Setting timeout for snapshot provision on Horizon View 2011

[McBarrette]

Hello there,

I had to build a large scaled Golden Image (approx. 500Gb), but provision fails due to a timeout. I think 90' won't be enough, does anyone knows where we can modify the timeout value (I looked in ADAM DB, unsuccesfully...).

Many thanks!

[Jubish-Jose]

We are using 500GB images and customization works just fine. The size of the HDD shouldn't matter.

When are you seeing the timeout? Is it when the internal VM (cp-template-xxx) is being customized (10 minutes) or is it when the final clone runs custom scripts (20 seconds)? The first one is not configurable, but the second one is.

[Jubish-Jose]

Sorry, I think you mean the cloning timeout due to large VM? How about using thin provisioned disk?

[McBarrette]

Right, I am talking about pool provisioning, I think customization has not even started when timeout happens. 

We currently use other golden images with 80Gb HDD, it works just fine and provisioning a pool takes around 45/60 mins, which is why I thought 90 mins would not be enough for a 500gb VM

I'll take a look at thin provisioning !

[McBarrette]

Seems we're already using Thin provisioning, but I found an unanswered thread for exactly the same issue here : https://communities.vmware.com/t5/Horizon-Desktops-and-Apps/SERVER-FAULT-FATAL-error-deploying-insta...

"We've tried an ADSI addition to the Horizon Broker servers that would extend a provisioning timeout to 180 minutes (described here https://kb.vmware.com/s/article/75019)" This is exactly what I am searching for but dead link :'(

"In some cases we can set the provisioning status to disabled then enabled and that kicks it in the pants and it finishes. Other times it will not." > Tried this and against all odds it was a success but kinda too random for me...

[Jubish-Jose]

Try this link: https://kb.vmware.com/s/article/75019

[McBarrette]

Hi Popvm,

I did find this tip but I got stuck here

• Expand OU=Properties.
• Expand OU=Global

I got into ADAM db but I could not expand Properties since it was empty.

[Jubish-Jose]

There should be something that you have missed. The Properties will not be empty if Connection Server is properly installed. Can you make sure that you are connecting to ADSI on the Connection Server machine and you are connecting to localhost?