VMware P2V Permission to perform this operation was denied fix

VMware

Just the other day we had a Windows Server 2008 R2 Standard physical server that needed to be P2V’ed, and after trying to use VMware Converter Standalone 6.1.1 we ran into the error message “Permission to perform this operation was denied” after entering the source machine details.

vmware p2v permission denied

Even after trying to start VMware Converter as “Run as administrator” the error persisted. Below is the workaround we performed to quickly allow us to P2V the physical server.

Workaround for Permission to perform this operation was denied

  1. Log into the server you’re trying to convert to a virtual machine.
  2. Open Local Security Policy (open run dialog and type secpol.msc).
  3. Go to: Local Policies > Security Options.
  4. Change “User Access Control: Run all Administrators in Admin Approval Mode” from Enabled to Disabled.
    local security policy disabled p2v
  5. Restart the server to make the changes take effect.
  6. You should now be able perform the P2V without issue.

After making the above change we was able to successfully P2V the server without any further issues:
VMware P2V completed

Once you confirm the P2V is successful I would recommend changing User Access Control: Run all Administrators in Admin Approval Mode back to Enabled from Disabled.
local security policy enabled p2v

If you have another workaround please share in the comments!

Similar Posts

  • VMware vCenter Server 5.5b released

    VMware
    2 Comments

    vmware vcenter 5.5b released

    VMware hasn’t let the holidays get in their way and has released vCenter Server 5.5b (Build 1476387) along with vCenter Server Appliance 5.5.0b (Build 1476389). The update includes a number of fixes.

    Resolved Issues in 5.5.0b

    Upgrade and Installation

    • Upgrading the vSphere Web Client to vSphere 5.5 fails with an error
      Attempts to upgrade the vSphere Web Client to vSphere 5.5 fails when they are installed in a custom, non-default location. An error message similar to the following is displayed:

      Error 29107. The service or solution user already registered...

    Read More “VMware vCenter Server 5.5b released”

  • VMware Recertification Policy

    VMware
    1 Comment

    VMware certified

    Starting today, March 10 2014, new VCP certifications must be re-certified within two years of it’s earned date. Anyone who currently has their VCP certification prior to March 10 2013 has until March 10, 2015 to re-certify.

    The new policy gives you three options to re-certify:

    1. Take the current exam for your existing VCP certification solution track. For example, if you are a VCP3, you could take the current VCP5-Data Center Virtualization (VCP5-DCV) exam.
    2. Earn a new VCP certification in a different solution track. For example, if you are a VCP-Cloud, you could recertify by earning VCP5-Desktop (VCP5-DT) certification.
    3. Advance to the next level by earning a VMware Certified Advanced Professional (VCAP) certification. For example, if you are a VCP5-DCV you could earn VCAP5-DCA certification.

    I can understand why they are doing this but I don’t agree with the changes. As per the announcement if you let your certification expire, “Your certification will be revoked,and you will no longer be entitled to use the certification logo or represent yourself as VMware certified“. Really? You mean everything that was done prior and after taking the exam means nothing?

    Read More “VMware Recertification Policy”

  • How to fix VMware Converter error “FAILED: The VSS snapshots cannot be stored”

    VMware
    2 Comments

    While moving some VM’s from Hyper-V to VMware using VMware Converter a VM failed to convert with the error: FAILED: The VSS snapshots cannot be stored.

    FAILED: The VSS snapshots cannot be stored because there is not enough space on the source volumes or because the source machine does not have any NTFS volumes. Error code: 2147754783 (0x8004231F).

    Come to find out the System Reserved partition was full. Our soon to be retired Appassure backup application was nice enough to fill up the volume.

    Luckily Appassure is being replaced by Veeam and fixing the above VMware Converter error is an easy fix.

    Read More “How to fix VMware Converter error “FAILED: The VSS snapshots cannot be stored””

  • VMware vCenter Server 5.5.0a update released

    VMware
    0 Comments

    VMware has released an update to vCenter 5.5 Server. The new updated, numbered 5.5.0a doesn’t appear to add any new features but instead focus on squishing a number of bugs in the 5.5 version – mostly around vCenter Single-Sign-On and the vSphere web client.

    Issues resolved with this release are as follows:

    1. Attempts to upgrade vCenter Single Sign-On (SSO) 5.1 Update 1 to version 5.5 might fail with error code 1603
    2. Attempts to log in to the vCenter Server might be unsuccessful after you upgrade from vCenter Server 5.1 to 5.5
    3. Unable to change the vCenter SSO administrator password on Windows in the vSphere Web Client after you upgrade to vCenter Server 5.5 or VCSA 5.5
    4. VPXD service might fail due to MS SQL database deadlock for the issues with VPXD queries that run on VPX_EVENT and VPX_EVENT_ARG tables

    Read More “VMware vCenter Server 5.5.0a update released”

  • How-to fix VMware Converter error FAILED: Unable to find the system volume, reconfiguration is not possible.

    VMware
    3 Comments

    I was recently tasked with migrating a Hyper-V machine to our VMware environment. However, each time VMware Converter was ran, the task would fail at 97% with an error “FAILED: Unable to find the system volume, reconfiguration is not possible.“.

    FAILED: Unable to find the system volume, reconfiguration is not possible

    Looking further into the virtual machine there were a number of concerns I had on the VM. One such issue which I believe might be causing the above error, is that the system volume drive was on drive 0 while the “C:” drive was on drive 1. Whereas these are typically on the same drive in most Windows installs.

    Below are the steps I took to fix this VM and made the migration from Hyper-V to VMware a success.

    Read More “How-to fix VMware Converter error FAILED: Unable to find the system volume, reconfiguration is not possible.”

  • My VMware View Windows 7 Optimization Guide

    VMware
    10 Comments

    These are the few steps I do when creating a new "Golden" image. Luckily I don’t have to do these steps all the time as I’ll create the "Golden" image when there is a new upgrade such as when we went from View 4.6 to View 5.0.1. I like to have a new fresh machine using new virtual hardware from the start. You could certainly just upgrade the virtual hardware on the "Golden" image, I just prefer to start clean.

    At any rate, here’s my list. Hopefully someone might find it somewhat useful and maybe even others can improve upon it.

    Preparing a new virtual machine

    1. Create New Virtual Machine – FILE > NEW > VIRTUAL MACHINE (CTRL+N)
    2. Under Configuration select CUSTOM.
    3. Select a Name, Folder, Host, Cluster, and Storage.
    4. Under Guest Operating System select Windows and then Windows 7 32bit under the Version drop down.
    5. Select which Network (VLAN) and under Adapter select VMXNET 3.
    6. Configure disk size to 30GB THIN provisioned.

    Read More “My VMware View Windows 7 Optimization Guide”

Leave a Reply to nathan jones Cancel reply

Your email address will not be published. Required fields are marked *

12 Comments

  7. Quick thanks and to let folks finding this article know this tip still works (as of 25 Feb 2021) … at least it worked for me …

    – Windows 10 Pro / SP1 (1803) (host to be P2V’d)
    – VMware Workstation 16 Pro (running on host to be P2V’d)
    – VMware vCenter Converter Standalone Client 6.2

    Reply