vlCenter tasks that conflict with VDI functionality

This is an interesting article that I picked from Chris Wolf from Twitter. Yes, OK I admit it, despite what David Cameroon said about tweeteers, I am one. OK.

That admission done with, down to this article. The wording is funny. It doesn’t actually name check VMware View 3.1 (until you get to the bulleted list), nor does it name check specifically any other 3rd party VDI broker either.

The KB article is here and it list some 9 things you can do in vCenter which will make “VDI” environment feel a little poorly and in need of a lie down (actually I feel that way sometimes too). Here’s the list:

• Moving an ESX from one cluster to another.
• Removing and re-adding an ESX host from VirtualCenter
• Un-registering and re-registering a virtual machine on VMware Infrastructure Client or VirtualCenter
• Re-signaturing a LUN which is hosting VDI desktops
• Moving virtual machines from one folder to another within VirtualCenter
• Changing the names of folders in VirtualCenter where virtual machines are stored
• Changing the names of folders in VirtualCenter where templates are stored
• Upgrading VirtualCenter while VDM/View services are running
• Re-installing VirtualCenter

My favorite part of the KB article is line that explains how to resolve these problems, I quoth:

“To avoid losing access to VDI desktops, do not perform any of these actions.”

Neat. That fixes that one then.

There bugger is renaming or moving folders – which is a suprisingly common tasks as your virtual infrastructure grows.