Migrating from VMware to Hyper-V; Problems with Hyper-V

Maximilian Schäfer 21 Reputation points


I am Running the 64-Bit Version of Windows 8.1 Pro and i am now Virtualizing a Windows Server 2008 R2. It in itself is not Causing an Issue.
(I know 2008 R2 and 2008 are EOL)
I am Running 8.1 in a Windows Server 2003 Domain, since i do not need it to be higher. I have 1 Running Windows Server 2012 R2 and 2 Windows Server 2008 R2.
I had VMware Workstation Pro and then just exported these Machines as VHD. I created new Hyper-V Machines. Then i got this:


Basically it is a "Cannot Change Machine State" Error with the Error Code 3080 and 3040.
i checked the Permissions and get more Issues Later Down the Road. The Issue is that it cannot Verify a Connection to the Domain, so it just does not wanna work with
Powershell or CMD.

Can anyone Please Help me, we have no Email otherwise!

Thank you,

Windows 8
Windows 8
A Microsoft operating system.
171 questions
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
8,765 questions
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
1,929 questions
No comments
{count} votes

Accepted answer
  1. Limitless Technology 37,501 Reputation points

    Hello MaximilianSchfer

    Usually this is caused by a lack of NTFS permissions on the Virtual Machine folder. For this you can compare the permissions with a machine that is working correctly

    PS C:\>$acl = Get-Acl -Path "D:\VirtualMachines\<Good machine folder>"
    PS C:\>$acl.access > C:\goodVM.txt
    PS C:\>$acl = Get-Acl -Path "D:\VirtualMachines\<problematic machine here>"
    PS C:\>$acl.access > C:\ProblemVM.txt
    PS C:\>Compare-object -referenceobject $(get-content C:\goodVM.txt) -differenceobject $(get-content C:\ProblemVM.txt)

    The result will tell you the difference in permissions and you will just need to set the missing ones in the NTFS permission of the folder.

    --If the reply is helpful, please Upvote and Accept as answer--

2 additional answers

Sort by: Most helpful
  1. Dave Patrick 340.3K Reputation points MVP

    We don't know what the dialog says. Might try some other method of conversion.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

  2. Maximilian Schäfer 21 Reputation points

    i know, didn't respond but, this seems to have done it. It also was the Issue that the Config File was in a Different Location then the VM! But this is a Hyper-V 2012 R2 issue only i think. Maybe a last Hotfix will come out or something.. Thanks!