CHR1S Posted December 9, 2013 Posted December 9, 2013 The second one is on that host too Chris. Bit of a nightmare! But you would only be shutting one down, the other would stay up for the time being.
Darylrese Posted December 9, 2013 Author Posted December 9, 2013 But you would only be shutting one down, the other would stay up for the time being. Both DC's are on the host which needs restarting though so no DC would exist when host is restarted! There is however now a third DC i didnt know about so yes, now the situation is we should still have a DC available when restarting the host.
CHR1S Posted December 9, 2013 Posted December 9, 2013 Both DC's are on the host which needs restarting though so no DC would exist when host is restarted! Thats why you were shutting ONE DC down, leaving one up, moving it to another host, starting it, then worrying about starting the physical host after.
mattianuk Posted December 9, 2013 Posted December 9, 2013 In our cluster, the dcs are the hosts, I was advised not to virtualise the dc's guess this is why. I shit myself whenever I have to restart even one of the failover cluster hosts. They have a secret way they like to be restarted, and I never get it right... Plus I transfer the vm's to one host, and have a couple of times, restarted that host instead of the empty one. Now I check it several times!!
Darylrese Posted December 16, 2013 Author Posted December 16, 2013 Hi Just to let you all know we managed to get everything working without having to reboot the host! I killed the associated svhost service which unstuck the windows management intrusion service and allowed me to restart all the services successfully. I can now manage machines again and the failover cluster is active Regards 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now