Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Problem when making VMs highly available; all get grouped together under just 1


  • Please log in to reply
1 reply to this topic

#1 Jakestealth22

Jakestealth22

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:07:29 PM

Posted 26 December 2017 - 10:54 PM

I don't know how to explain this but when I go to make my Hyper-V VMs highly available using the Failover Cluster Manager, for some reason they all get grouped together under just one role. In the wizard, I select all the VMs I want made highly available, but after the wizard completes, only 1 role shows up but with all my selected VMs grouped in it. I also get no errors or warnings in the report after it’s done. EACH INDIVIDUAL machine is supposed to show up as an INDIVIDUAL Virtual Machine role made highly available, NOT grouped as shown in the attached screenshot below. I never had this problem in the past. I'VE BEEN AT THIS FOR HOURS! WHAT THE HECK AM I DOING WRONG?! Any help would be greatly appreciated!!

 

Attached File  screenshot.JPG   80.44KB   0 downloads


Edited by Jakestealth22, 26 December 2017 - 11:09 PM.


BC AdBot (Login to Remove)

 


#2 Jakestealth22

Jakestealth22
  • Topic Starter

  • Members
  • 10 posts
  • OFFLINE
  •  
  • Local time:07:29 PM

Posted 27 December 2017 - 07:19 PM

Update:

I went into the Failover Cluster Manager and created the CSV (cluster share volume). Then, I moved the VMs over to it and it worked!






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users