0x80070569 Error When Creating Second Virtual server in Hyper-v 2012

Question

_{Wednesday, October 10, 2012 9:18 PM}

I get this error when I try to create a second VM from Hyper-v Manager on windows 8 / server 2012 / server 2008 R2.

Hyper-v is running on a new install of server 2012 core.

I was able to create the first VM (server 2012 with a GUI) and is running fine.

I have tried adding the local administrator account to the logon as a batch job and doing a gpupdate /force with not luck.

Both the server 2012 core and the server 2012 VM are joined to the same domain.  I am logged into server 2012 and server 2008 R2 as the domain administrator.

Any ideas would help!

All replies (6)

_{Thursday, October 11, 2012 8:24 AM ✅Answered}

Hi,

Error Message: The user has not been granted the requested logon type at this computer, this problem typically occurs when the user does not have the permissions to log on locally on the computer.

By default, members of the Users group have the ability to log on locally, but an administrator can deny the right to specific user or group accounts. An explicitly denied right always overrides an allowed right.

This can be caused by either of the following:

• Neither the user account nor any of the groups it belongs to has been granted the Allow log on locally user right.
• The user account or one or more of the groups it is a member of has been listed in the Deny log on locally user right.

Ensure that the user, or a group the user belongs to has the right to log on locally. Ensure that the user, and all groups that the user belongs to, are not denied the right to log on locally.

Also, have you tied to restart to restart the Hyper-V host server? Restart it and check the result.

You may also try to create VM using PowerShell command:

Sample Scripts for Managing Virtual Machines
http://technet.microsoft.com/en-us/library/bb963748.aspx

For more information please refer to following MS articles:

Error Message: The user has not been granted the requested logon type at this computer
http://technet.microsoft.com/en-us/library/cc732593(v=WS.10).aspx
Windows 8 Hyper-V Virtual Machine Management Service
http://social.technet.microsoft.com/Forums/lv/winserverhyperv/thread/4b3e7582-dc20-4dcb-8e71-fef9fecce19c

Lawrence

TechNet Community Support

_{Monday, October 15, 2012 8:53 AM ✅Answered}

Hi,

I found some posting which discussed similar issue, and finally the issue disappears after several hours or after 1 day. I don’t find the issue reason.

As you mentioned, may be communication issue. And I think maybe is authentication issue, sometimes domain account display as GUID, not the common display name; at this time, you may encounter this issue. However, after restart, issue disappears.

For more information please refer to following thread:

Enable replication failed
http://social.technet.microsoft.com/Forums/en-US/winserverhyperv/thread/a195ac9c-d5fd-4e78-a57a-f66b8231bc50

Lawrence

TechNet Community Support

_{Friday, October 12, 2012 5:32 PM}

I checked all of these AD location and the administrators group is there.  I checked the Deny and it is empty.

I came in the next day and tried it again and I was able to add a second VM.  After that I had problems adding hard drives to VM's, it would error out.  But it will still create the VHDX, so I would then browse out and select the VHDX.  Everything was up and running yesterday just fine.

Today after stopping one of the virtual servers, I couldn't start it back up.  I would get the same error I got trying to create a second VM.  After reading through the last link, I went in and restarted the Hyper-V Virtual Machine Management Service.  I was then able to start up the VM.

I have tried restarting the hyper-v server in the past when I would get these errors and it hadn't fixed this issue.  I have found that when I have problems that refreshing the hyper-v manager will fix some issues.  This happens from my windows 8 PC and the server 2012 VM.  Either hyper-v 2012 is just flaky like that or maybe I am having a communication issue.  Maybe a switch or cable problem?

Thanks,

Nathan

_{Tuesday, July 22, 2014 7:34 AM | 5 votes}

Maybe that will help,

in my case the domain was joined after Hyper-V Role installed. The local group Hyper-V Adminstrator was empty. Just added my domain admin, restart the hyper-V service and recreate the VM. It's working.

_{Wednesday, July 25, 2018 7:03 AM}

Hi,

After restart this service Hyper-V Virtual Machine Management, I did not have a problem.

_{Thursday, May 23, 2019 8:38 PM}

Boa noite,

Funcionou pra mim, obrigado.