kgsivan wrote:

> 5. This is a strange one - I didn't decrease the pool size in the steps above (our servers have enough overhead to take the full pool size with one server down). I'm assuming that when desktops on the other datastores are deleted (logged off) > one by one, they will be spun up on this restored datastore (one by one)?

Sorry... My bad. You don't need to increase pool size. Instead user "Disable Provisioning" before VM removal and "Enable Provisioning" after patching, and adding the host-back..

(If so, even you don't need to edit the datastore spec.)

Hmm, I haven't disabled provisioning either - I still want desktops to be created in this case, but I guess others may not if they don't have the resources.

I found that when deleting the desktops from the other resources, the "minimum available" count kicks in and spins up some new desktops on the remaining datastores. All fine with me.

When the new datastore comes back, it starts using it again automatically when users log off (desktop deleted) from other datastores.

This seems OK, have now completed the patch on the first server.

I can see this might be a bit of a nightmare with an extensive deployment.

Thanks for the assistance.