But when I use the drop down for virtual machines, I get "". Depending on the execution policy settings, PowerShell blocks unsigned scripts. On Windows 10 computers, you do this by starting the PowerShell session with administrative privileges from the context menu. I launch this and I can browse for computers in the other domain, authenticate myself, and do check name successfully. The first step in managing Exchange Online with PowerShell is to set the execution policy accordingly. I put in my credentials for the other domain (\) and I get returned "This version of the Hyper-V Management Tools cannot be used to manage servers running Windows Server 2012 or Windows Server 2012 R2 as another user".įrom the web, I learned that there is a back level version included located at C:\program files\Hyper-V\6.2\vmconnec t6.2.exe. And there is an option to connect as a different user. When I attempt to connect using Hyper-V Manager from Windows 10, I can verify the host on the different domain through Check Name. And I can connect to Hyper-V under Server Manager using that same domain account (using "Manage As"). Just listing it for completeness sake.įrom Windows 10, I can connect via Server Manager to the host, using a domain account on the Hyper-V host's domain (using "Manage As"). My available platforms are Windows 10 Enterprise on a different domain and Server 2008 that's on the same domain as the hyper-v host machine.įrom what I'm reading, this isn't possible at all from the 2008 machine. ![]() I have a Windows 2012 core server that I need to manage Hyper-V VMs on.
0 Comments
Leave a Reply. |