VDI environment updates/patching

[HOLLYW00D]

Howdy,

Hypothetically speaking, if I were to reboot the servers responsible for our VDI environment without disconnecting/logging off/shutting down any of the clients, would that cause any issues with the clients not being able to re-establish connection once the servers came back up?

Recently, Microsoft Windows updates were pushed out to our two VMmware View servers (VMWareVIEW1 and VMwareVIEW2), as well as our VDI server (VMwareVDI).  These servers rebooted, and then we had issues with clones being able to connect to the pools.  In the end, deleting the clients from the ADAM database was required.  I should add, that we were also updating the all of the hosts for the pools during this time.  When the three aforementioned servers came online, we were not done updating one of the three hosts, clones began connecting and trying to fail over to the other two hosts.  We tried to stop this by disabling the pools while clients were still connecting.

Would I be correct in thinking that a reboot of the three servers, mentioned earlier, should not cause any sort of ADAM db corruption which, in turn, would affect clone/pool connection/relationship?

Thanks in advance for any input.

[memaad]

HI,

After windows upgrade on VMware view connection server, you should be able to connect desktop back ( linked clone ). If you are saying that after reboot you could not connect back to linked clone desktop , then there can be many reason for it. To know the reason for it, first we need to know what was status of view virtual desktop ( linked clone ) in connection server, when you rebooted the view connection server.

Regards

Mohammed

[HOLLYW00D]

Good morning, Mohammed.

The linked clones were online/powered on/connected at the time all three servers rebooted.  I'm quite new to the VM world, but it just doesn't make sense that a reboot of these servers (which includes the composer service) would cause any kind of data corruption and/or orphan the linked clones that were connected before the reboot.

Thanks again.

[mikebarnett]

There is the possibility for issues arising but I wouldn't classify them as corruption. The database could become out of sync with Composer/vCenter, etc if provisioning operations of some sort were executing at the time of the restarts.

Without seeing logs or the DB itself it's hard to speculate exactly what happened. In general View should recover normally from any kind of restart of the servers.

-Mike