locked
Failed to mount VHD A required privilege is not held by the client RRS feed

  • Question

  • Hi,

    I've installed the evaluation copy of SCVMM2008 R2 on Windows 2008 R2 SP1.  Every time I try to create or P2V a virutal machine I get the same error:

    VMM cannot complete the Hyper-V operation on the Hyper-V4 server because of the error: 'The system failed to mount 'D:\Virtual Machines\Temp\Temp_disk_1.vhd'. Error Code: A required privilege is not held by the client.

    (A required privilege is not held by the client (0x80070522))

    I'm logged into the machine using the Admin Console directly on the server (Rremote desktop) with a Domian admin account.

    Any suggestions on how to correc this?

    Thanks,

    Phil.

    Tuesday, April 5, 2011 10:53 AM

Answers

  • I finally fixed it.  The user account needed the privilege "SeManageVolumePrivilege" or "Perform Volume maintenance tasks".  Once this was assigned the VHD would mount and the stalled P2V would move to the next stage. It also fixed the same error on creating new VMs as well.

    Phil.

    • Marked as answer by Phil 999 Monday, April 11, 2011 2:54 PM
    Monday, April 11, 2011 2:54 PM

All replies

  • is your Virtual Machine Management Service (Vmms.exe) running? Otherwise, please restart the service ad try again.
    Tuesday, April 5, 2011 11:29 AM
  • I've checked and the services is running. The server has had several reboots during my attempts to correct the problem. I tried restarting the service anyway and no change i'm afraid.

     

    Tuesday, April 5, 2011 1:44 PM
  • Hi!

    Is the SCVMM client machine a member of the domain?

    Tuesday, April 5, 2011 1:51 PM
  • Why not a simple file access rights issue?

    > Right click the VHD, check SECURITY TAB...

    > Read only???

    Yannick

     

    Tuesday, April 5, 2011 1:53 PM
  • and added to the question of Yannick: your VHD is not under the root of C:\ for example or any other secured folder?

    Tuesday, April 5, 2011 1:56 PM
  • D:\Virtual Machines\Temp\Temp_disk_1.vhd

     

    If you read first post.

    Tuesday, April 5, 2011 2:07 PM
  • Hi,

    Thanks for the suggestions.  I'm running the SCVMM console directly on the SCVMM server.

    I've check the permissions on the d:\virutal machines\Temp\ folder and all looks OK.  I tried adding everyone --> full control anyway but no luck.

    In the P2V conersion the VHD has been created and approx 5GB transferred from the Windows 2000 Server I was testing on. The P2V conversion fails at stage 1.4 and virutal machine XML file had also been created.

     

    Tuesday, April 5, 2011 2:14 PM
  • When you perform a p2v migration, do you alter any of the settings at that point?

    I've experienced that p2v migrations fail if you increase vhd size, RAM or anything other than what's suggested. It's better to leave everything and modify the VM settings after the migration has finished.

    Once again, is the SCVMM server a domain member?

    Tuesday, April 5, 2011 5:05 PM
  • Hi,

     

    According to the description, the issue seems to be related to SCVMM. As we mainly focus on the Hyper-V question about Windows Server system and here is not the best support resource for SCVMM, it is recommend you to get further support in the corresponding community so that you can get the most qualified pool of respondents. Thanks for your understanding.

     

    For your convenience, I have list the related link as followed.

     

    System Center Virtual Machine Manager

    http://social.technet.microsoft.com/Forums/en-US/category/virtualmachinemanager

     

     

    Best Regards,

    Vincent Hu

     

     

    • Marked as answer by Phil 999 Monday, April 11, 2011 2:50 PM
    • Unmarked as answer by Phil 999 Monday, April 11, 2011 2:50 PM
    Friday, April 8, 2011 8:19 AM
  • I finally fixed it.  The user account needed the privilege "SeManageVolumePrivilege" or "Perform Volume maintenance tasks".  Once this was assigned the VHD would mount and the stalled P2V would move to the next stage. It also fixed the same error on creating new VMs as well.

    Phil.

    • Marked as answer by Phil 999 Monday, April 11, 2011 2:54 PM
    Monday, April 11, 2011 2:54 PM
  • Phil,

    Where did you setup the "SeManageVolumePrivilege" or "Perform Volume maintenance tasks". 


    Harish

    Thursday, February 16, 2012 3:39 PM
  • Hi,

    Finally I found the solution to this problem.

    http://srvcore.wordpress.com/tag/system-center-virtual-machine-manager/page/2/

    "By default the local User Right “Create Symbolic links” is assigned to the Adminstrators group. Once you install Hyper-V a extension is installed on this machine that allows Service SIDs to be used and the Service SID “Virtual Machines” is allowed to “Create Symbolic links”

    So, you need to add your user or group in the configuration of GPO for allowed to create a symbolic link and mount the VHD file.

    Best regards

    Felipe Feitosa
    Coordinator of Infraestructure at SuperBank
    www.superbank.com.br
    www.supermeios.com.br

    Thursday, June 21, 2012 1:29 PM
  • I encountered this error last week too:
    Error Code: A required privilege is not held by the client.
    (A required privilege is not held by the client (0×80070522))

    spent 2 weeks to resolve this problem

    my situation isn’t related to GPO permission problem

    at last I found my “Hyper-V Global setting for each VM config file save location” set to an invalid path,

    which that drive already lost (after I enabled CSV, SAN disk drive D lost and changed to symbolic link C:\clusterStorage\volume 1)

    it caused the mentioned two operation cannot be executed:
    SeCreateSymbolicLinkPrivilege
    SeManageVolumePrivilege

    Microsoft didn't capture and tell you the real cause of my error >.<

    even through these permission are still disabled too

    i cannot enable it since after the Hyper-V host server joined the domain

    its disable due to the GPO inheritance by default

    Solution:
    reset the "Hyper-V Global setting for each VM config file save location" to a valid location (e.g. C:\Program File(x86)\Hyper-V\) on the Hyper-V Host server
    now adding, editing and running Hyper-V VM or performing Hyper-V failover Live Migration will not be a problem

    Microsoft didn’t capture their exception wisely and explain you clearly what caused the error >.<
    Microsoft didn’t capture their exception wisely and explain you clearly what caused the error >.<
    Microsoft didn’t capture their exception wisely and explain you clearly what caused the error >.<
    Tuesday, February 19, 2013 4:15 AM