Sign in
 
HomeWindows Server “8” Beta20082003LibraryForums
Windows Server TechCenter > Windows Server Forums > Hyper-V > Hyper V Server R2 Disk Management Issues

Answered Hyper V Server R2 Disk Management Issues

    •  
      Tuesday, July 21, 2009 8:49 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hello everyone

      I have a real pain in the ____ problem I am testing Hyper V Server R2 prior to implimenting it into a school and I cannot manage disk management via a MMC. I get unable to connect to virtual disk service the rpc server is unavailable the virtual disk service is enabled. I can view the event viewer and other items I need access to disk managment as I am going to be using software based raid to configure the raid sets. I have had no problems with the test machine when running full version of server 2008 R2 with the hyper V role enabled.

      I do however have this in the event viewer.

      'Hypervisor' driver required by the Virtual Machine Management service is not installed or is disabled. Check your settings or try reinstalling the Hyper-V role.

      I have disabled the firewall on the Hyper V Server and the client connecting as per some documentation still no joy.

      Many Thanks


       

    Answers

    • Tuesday, July 28, 2009 1:26 AM
      Moderator
       
       Answered
      Sign In to Vote
      5
      Sign In to Vote
      Hi,

      Please note, try to disable Firewall on both machines or run the command below on both machines to test, not only the Hyper-V Server.

      netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes

      Thanks.
      This posting is provided "AS IS" with no warranties, and confers no rights.
       
    • Wednesday, July 29, 2009 1:24 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote
      Hi Mervyn

      Unfortunatly the Nic card in the 2 test machines dont seem to be supported in the network monitor.

      I have however managed to connect perfectly fine, what i had to do was put the hyper v server into a domain once it was joined to the domain any of our servers could open the disk management console.

      It seems strang that even though the users where added to the local admin group it did not allow them to connect. Looks like a workgroup scenario really is not supported.

      Many thanks for your help.
       

    All Replies

    • Wednesday, July 22, 2009 9:12 AM
      Moderator
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hi,

      Thank you for posting here.

      By default, Virtual Disk Services is not started, please try to run "sc start vds" on Hyper V Server R2. After that, could you connect to it via MMC?

      If not, you can also manage disk via diskpart tool which is now a standard built-in tool. All operations that you can perform on GUI interface, you can complete via diskpart. For more information, please refer to the article.

      A Description of the Diskpart Command-Line Utility
      http://support.microsoft.com/kb/300415

      DiskPart
      http://technet.microsoft.com/en-us/library/cc770877(WS.10).aspx

      Thanks.
      This posting is provided "AS IS" with no warranties, and confers no rights.
       
    • Thursday, July 23, 2009 8:18 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Many thanks for the information.

      The service was started and i am still unable to connect.

      I actually did not know to the extent of what diskpart can do as in create raid sets.

      Very impressed you learn something new every day.

      Regards

      Chris
       
    • Friday, July 24, 2009 8:58 AM
      Moderator
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hi Chris,

      Thank you for update. I have reproduced this problem on my test machines. It seems a known issue. I can disable Firewall on Hyper-V Server and other MMC snap-in works fine on remote management. I will report this problem to product team. If there is any update, I will post here.

      Thanks.
      This posting is provided "AS IS" with no warranties, and confers no rights.
       
    • Sunday, July 26, 2009 1:01 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Mervyn,

      I have been able to reproduce this issue as well. With Hyper-V Server R2 already RTM, will this issue be resolved via update when R2 is released? Running a single Hyper-V R2 server this isn't a huge problem since I would just use diskpart to perform my tasks, but when using 15-20 Hyper-V R2 servers, this could be a huge issue.

      Just want to make sure this is addressed before we go all out in our environment with R2.
       
    • Monday, July 27, 2009 4:25 AM
      Moderator
       
       
      Sign In to Vote
      1
      Sign In to Vote
      Hi,

      Based on further test, this issue was caused by Firewall settings. On connecting system, run the following command to enable "Remote Volume Management".

      netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes

      Thanks.
      This posting is provided "AS IS" with no warranties, and confers no rights.
       
    • Monday, July 27, 2009 3:07 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Mervyn,

      I had disabled the firewall in my test environment and it did not make a difference to the issue.

      Regards
       
    • Tuesday, July 28, 2009 1:26 AM
      Moderator
       
       Answered
      Sign In to Vote
      5
      Sign In to Vote
      Hi,

      Please note, try to disable Firewall on both machines or run the command below on both machines to test, not only the Hyper-V Server.

      netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes

      Thanks.
      This posting is provided "AS IS" with no warranties, and confers no rights.
       
    • Tuesday, July 28, 2009 3:45 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hi Mervyn

      I have fully reset the lab up from scratch doing the things listed just in case i had changed something while testing.

      I have a new message "You do not have access rights to the logical disk manager on <server name>"

      Once i have clicked ok it says unable to connect to virtual disk service.

      After this the Virtual disk service stops and i have to restart it manually, the virtual disk service was running before i clicked disk management.

      I still have access to the services and event viewer etc just not disk management.

      I have added myself as a local administrator the firewall rules are set correctly.

      I have also tried a different server with different hardware.

      Many Thanks
       
    • Wednesday, July 29, 2009 2:51 AM
      Moderator
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hi,

      If there is any third party antivirus software or Firewall, please try to uninstall them on both two servers. Boot all servers into Clean Boot and run the following command on both two servers:

      netsh advfirewall set currentprofile state off

      Try to test again. Is there any progress?

      Thanks.
      This posting is provided "AS IS" with no warranties, and confers no rights.
       
    • Wednesday, July 29, 2009 8:16 AM
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi

      I have tried with the above setting and the results are still the same.

      I removed AV which was on client and disabled both firewalls.

      Regards

       
    • Wednesday, July 29, 2009 10:26 AM
      Moderator
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hi,

      Please try to capture the network traffic of this problem for research.

      http://www.microsoft.com/downloads/details.aspx?FamilyID=983b941d-06cb-4658-b7f6-3088333d062f&displaylang=en

      Download and install the Network Monitor on connecting machine. Start it, start capturing, reproduce this error, stop capturing and save the captured file and use Windows Live SkyDrive (http://www.skydrive.live.com/) to upload the file and then give me the download address.

      Also, please collect MPS Report on connecting system for research.

      1.    Download proper MPS Report tool from the website below.

      Microsoft Product Support Reports
      http://www.microsoft.com/downloads/details.aspx?FamilyID=CEBF3C7C-7CA5-408F-88B7-F9C79B7306C0&displaylang=en

      2.    Double-click to run it, if requirement is not met, please follow the wizard to download and install them. After that, click Next, when the "Select the diagnostics you want to run" page appears, select "General", <and other necessary catalog>, click Next.

      3.    After collecting all log files, choose "Save the results", choose a folder to save <Computername>MPSReports.cab file. Please use Windows Live SkyDrive (http://www.skydrive.live.com/) to upload the file and then give us the download address.

      Thanks.
      This posting is provided "AS IS" with no warranties, and confers no rights.
       
    • Wednesday, July 29, 2009 1:24 PM
       
       Answered
      Sign In to Vote
      0
      Sign In to Vote
      Hi Mervyn

      Unfortunatly the Nic card in the 2 test machines dont seem to be supported in the network monitor.

      I have however managed to connect perfectly fine, what i had to do was put the hyper v server into a domain once it was joined to the domain any of our servers could open the disk management console.

      It seems strang that even though the users where added to the local admin group it did not allow them to connect. Looks like a workgroup scenario really is not supported.

      Many thanks for your help.
       
    • Thursday, July 30, 2009 7:01 AM
      Moderator
       
       
      Sign In to Vote
      0
      Sign In to Vote

      Hi,

      Glad to hear you have resolved your problem. However, as far as I know, we cannot add Domain user to Local Group of a workgroup computer.

      Thanks.

       

      This posting is provided "AS IS" with no warranties, and confers no rights.
       
    • Thursday, July 30, 2009 4:27 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hi Mervyn

      Sorry the test environment was just a workgroup client and hyper v server, yesterday i added the hyper v server to my production domain to see if it made a difference and i was able to manage the disks for one of my production servers.

      Regards
       
    • Wednesday, September 16, 2009 12:51 AM
       
       Proposed Answer
      Sign In to Vote
      1
      Sign In to Vote
      SigDarkSide

      I have the answer
      I have the answer

      My god this was driving me nucking futs till I found this answer. 

      Seems what we are were seeing is a common common problem and I found the answer here.

      http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/6dd0af1b-3be2-492e-96a0-16cfb7aee379#_You_receive_the

      And that link above takes you to the resolution below.  Simply download this guys script and follow the instructions and all is golden.

      http://code.msdn.microsoft.com/HVRemote

      I am putting the answer in here because I found your posting first and it took another 10 minutes to find the answer.
      • Proposed As Answer by dragon300zx Wednesday, September 16, 2009 12:51 AM
      •  
       
    • Thursday, October 08, 2009 3:28 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Nevermind - it was a firewall issue!

       
    • Saturday, January 09, 2010 9:56 PM
       
       
      Sign In to Vote
      0
      Sign In to Vote
      Hi,

      Please note, try to disable Firewall on both machines or run the command below on both machines to test, not only the Hyper-V Server.

      netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes

      Thanks.
      This posting is provided "AS IS" with no warranties, and confers no rights.

      This worked for me. Enabled the Remote Volume Management rule on my client machine (Windows 7) and was able to access the Virtual Disk Service on the Hyper-V R2 server.

      Thanks,
       
    • Thursday, April 08, 2010 7:01 PM
       
       
      Sign In to Vote
      1
      Sign In to Vote

      Here what I did to add a new hard drive to Hyper V Server R2

      DISKPART>select disk 1 

      DISKPART>create partition primary

      DISKPART>list volume

      DISKPART>select volume 3        <----- newly created volume

      DISKPART>format FS=NTFS label="disk2" QUICK

      DISKPART>ASSIGN LETTER=H

       

       

       

       

       
    • Monday, December 20, 2010 8:59 AM
       
       Proposed Answer
      Sign In to Vote
      0
      Sign In to Vote

      Hi sigdarkside
      I'm really tired in the testing of this, but in the end I got to resolve

      The problem was in name resolution
      because only one scenario was working.
      only when you open remote administration before the server .

      You should use the DNS server or add a record in the hosts (C:\Windows\System32\drivers\etc\hosts)

      It really works

       

      Wild Horse

      • Proposed As Answer by ahmad_986 Monday, December 20, 2010 9:00 AM
      •