View 4.0 - provisioning stuck

[wzola1]

Hello,

We have a View 4.0 environment with 3 domain controllers: dc1, dc2, dc3.

We use automated desktop pool (non-persistent).

If dc2 is powered off from some reason(e.g.: site failover test once a year), the provisioning works, the new linked-clone computer is created but remains status "customizing."

Why can not use View an other DC in this case?

Thanks,

Zoltan

[wzola1]

If DC2 is available again, the new linked-clone computers will be "Ready" soon.

[mittim12]

Welcome to the forums.   Any hard references to the domain controller in the image that would cause this?    My guess is that the dc is providing DHCP addresses to those clones and when it's offline the clone doesn't receive an IP and gets stuck in the customizing state.      Can you verify that?

[wzola1]

Thanks for the quick answer. DC2 and DC3 are both DHCP servers. Anyway, I also think they don't get IP addresses when DC2 is powered off. I will check the DHCP log soon.