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

Maximilian Schäfer 21 Reputation points
2022-08-30T11:17:18.853+00:00

Hello,

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:

236132-hyper-v.png

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 for business Windows Client for IT Pros Storage high availability Virtualization and Hyper-V
Windows for business Windows Server User experience Other
Windows for business Windows Client for IT Pros User experience Other
0 comments No comments
{count} votes

Accepted answer
  1. Limitless Technology 39,916 Reputation points
    2022-08-31T08:39:25.69+00:00

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

    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Anonymous
    2022-08-30T14:39:40.897+00:00

    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
    2023-01-20T20:25:39.6033333+00:00

    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!

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.