Windows Update and Hyper-V Cluster
I understood today Windows Update Client is most powerful Sith Lord and no any Jedi stop him 🙂
After stupid mistake (Set Automatic Windows Update Enabled) I saw that all virtual servers moved to another node but only one of VM in Saved State status and never activated . (its another story why VM couldnt moved or activated )
Actually I’m VMware guy and expect that without all VMs moved, source node shouldn’t be rebooted but its ! Actually i have some expectation from VMM but completely forgot Cluster Service , still all resources failover managed by it.
Again , no way to stop Windows Update Client 😉
Disable auto update or change something about resource failover policy
Cool … I know, its my bad , nothing about design …