Quantcast
Viewing all articles
Browse latest Browse all 11941

Placing Hyper-V host in maintenance mode causes "random" VM's to be placed in maintenance mode too.

I've been running SCOM since version 2007 and SCVMM since 2008. We're now on SCOM 2012 and SCVMM 2012. Since that time we've expanded our Hyper-V environment and migrated VM's to other hosts and clusters. The issue that I'm having is as follows. I have 2 3 node Hyper-V 2008R2 clusters, let's call them Hosts 1-3 as Cluster A and Hosts 4-6 as Cluster B. When I place Host 1 in cluster A in maintenance mode in SCOM, it places virtual machines on Cluster B in maintenance mode. The VMs in question used to live on Host 1 of Cluster A, but now they live on one of the hosts of Cluster B. I'm not an Ops Manager guru, so my question is this. Is there a way to re-home the VM's in SCOM so that SCOM recognizes that VM X no longer exists on Host 1 but Host 5 of Cluster B and only places the VMs that now live on Host 1 in mainteance mode? Or is this even an Ops Manager issue? Is this a SCVMM issue? If so, how do I accomplish said task?

Sorry if that's confusing. I'll try to explain better if it is.


Viewing all articles
Browse latest Browse all 11941

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>