A strange odd thing I'm experiencing right now in my Failover Manger. I have a cluster environment that has 8 host servers. About 61 servers total. I had divided the host servers into 3 dedicated preferred segments (Development, QA, and NET) first 3 host servers were devlopment, with settings restricting them to those server hosts. Then I used 2 host servers that were dedicated for QA. Did the same thing and restricted their setting to those 2 preferred servers. The final set was 3 dedicated for Network testing called NET with the same restrictions to those host servers. After about several years I decided to remove NET and open the cluster group to just Development, and QA. Everything went smoothly but I had several VM's that I had to shut down because of the restriction settings for preferred owners were not able to be removed so I had to shut some of the servers down. Once I did that I was able to remove those settings. That's when all the weird things started to happen to about 6 servers that wouldn't start in the failover cluster. I was getting an error code 0x800713cf which goes back to the restrictions that were placed on the Vm's but those restriction have been removed. I had decided to re-import the VM's with there same ID and brought them into view on the Hyper-V manager for which I was able to start the VM's and everything is looking great. But on the Failover Manager the affected VM's are still showing as being off and still generating that same 0x800713cf even though they are completely on. I had reset the entire cluster group but Failover Manager is still showing them as off? very strange. I was hoping anyone has come across this problem before?
Thank You for your time
Art Gonzales