Hello all,
I have a question regarding possible owners that a VM can have and Cluster Aware Updating. We have several servers that cannot be moved between HyperV hosts, because the high availability is configured in the application the VM is running, or it is not supported for an application (Lync HA, Exchange DAG, etc.). We configured the possible owner of VM's through SCVMM to be only a certain node. However, we want to use Cluster Aware Updating and when we run it, the process fails. Of course there is no way to drain a role that is fixed on a cluster node, but we shut these servers down and had hoped that the roles were not required to be drained that way. It appeared that this was not the case and the update process failed.
The workaround was to set the possible owners to several other hosts as well (they were shutdown, so no problem). This was only for a couple of VM's on this cluster, but we have clusters that have much, much more of these type of hosts so we want to see if there is another solution.
Isn't there any way to make sure that Cluster Aware Updating does not require hosts that are shutdown, to be drained to another node? Or any other brilliant idea? :-) I found out that you can do a "forced" drain through Powershell, but I do not think that that is a good solution and that we cannot apply it via Cluster Aware Updating. Anyone?