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 ESXi 6.0 CBT bug fix released

    VMware
    0 Comments

    VMware

    You may remember ESXi 4.x-5.x had a CBT bug, as mentioned here, that could potentially cause your backups to be pretty useless. Well it seems ESXi 6.0 isn’t without it’s own CBT bug which could cause the following to possibly occur:

    • Backing up a VM with CBT enabled fails.
    • Powering on virtual machines fails.
    • Expanding the size of a virtual disk fails.
    • Taking VM quiesced snapshots fails.

    Prior to the fix, the workaround was to disable CBT. Thankfully VMware has released a fix for the ESXi 6.0 CBT bug and it’s recommended that anyone who uses CBT apply this patch regardless if it was a clean install of VMware ESXi 6.0 or an upgrade to ESXi 6.0.

    Read More “VMware ESXi 6.0 CBT bug fix released”

  • Easy ESXi 5.5 upgrade via command line

    VMware
    17 Comments

    ESXi 5.5 was just released general availability (GA) on Sunday (9/22) and I’m itching to upgrade the home lab to run the latest version with all it’s goodies. I wanted to try upgrading my hosts without having to go through the same process that I followed setting up ESXi on the NUC in the first place, injecting custom NIC drivers, etc.

    Enter the command line…

    1. Move all VM’s from the host and then put the host into Maintenance Mode.
    2. Go to the Configuration tab > Security Profile and Enable SSH under Services.
      ssh enabled
    3. Under Firewall, enable httpClient (outbound http).
      httpClient enable
    4. Open PuTTY (or other SSH client) and SSH into your host.

      5. Read More “Easy ESXi 5.5 upgrade via command line”

  • 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”

  • Another CBT bug found in VMware ESXi 6.0

    VMware
    0 Comments

    VMware

    VMware just published KB 2136854 regarding a new bug found in ESXi 6.0 that causes virtual machine backups, which use Changed Block Tracking (CBT), to be inconsistent. VMware says the cause of the issue is this:

    This issue occurs due to an issue with CBT in the disklib area, this causes the change tracking information of I/Os that occur during snapshot consolidation to be lost. The main backup payload data is never lost and it is always written to the backend device. However, the corresponding change tracking information entries which occur during the consolidation task are missed. Subsequent QueryDiskChangedAreas() calls do not include these missed blocks, hence a backup based on this CBT data is inconsistent.

    Read More “Another CBT bug found in VMware ESXi 6.0”

  • 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”

  • 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”

Leave a Reply to KobiMobi 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