1

Remotely managing Hyper-V VMs from Windows 8 Client

view story
linux-howto

http://serverfault.com – Currently, I have a core Hyper-V Server hosting VMs for a domain controller and several domain-joined VDI infrastructure servers. The VMs are connected in that domain environment, but the remote management of the physical Hyper-V Server is set up using the same WORKGROUP (as the Windows 8 client I'm managing from) This makes it cumbersome to manage the VMs hosted on the physical server from my remote management Windows 8 client because I can only connect to the physical Hyper-V server and not the individual VMs hosted inside. Can I make my set up more flexible by hosting a second domain cont (HowTos)

dayu's picture
Submitted by dayu on 11/05/2012

Stories similar to Remotely managing Hyper-V VMs from Windows 8 Client

I have a core Hyper-V Server 2012 that I am remotely managing from a Windows 8 client. I can connect in Hyper-V Manager, Server Manager, and MMC.

I run a Hyper-V server running several Hyper-V VMs. I was wondering if there is any way for me to manage

the Hyper-V server itself (just Hyper-V role, not the rest of the server box) and the Hyper-V VMs (like connecting into them)

via Mac OS?

I'm on Mac OS 10.8 on my main laptop. From what I've been seeing the Hyper-V management tools are all Windows based.

I'm trying to connect my Hyper-V Server to a Windows 8 client for remote management.

I'm trying to connect remotely from my Windows 8 client to manage my Hyper-V Server 2012.

I've configured my Windows Server 2008 to allow the remote management (using sconfig). I am connecting (with IP addres) using Windows Server 2008 (full version, where I've configured RSAT) and Server Manager (. I am using administrator account with the password on both systems.

We currently run a Hyper-V server on a non-domain W2008 server, and are looking to build a failover solution. Because all the (6-10) VM guests are linuxes, and our datacenter space is 90% non windows, we have never felt the need for AD domains etc.

My initial plan is a second server (either W2008R2 or W2012 standard), running Hyper-V server.

There is no shared storage / SAN in place.

I have a Windows Server 2008 inside Hyper-V.

My host OS is a Domain Controller.

I can ping my network from the guest OS, but I can't join the domain. It gives a DNS error:

The operation returned because the timeout period expired.

Could anyone help ?

I have a server running Windows Server 2012 and it only has the Hyper-V role. I have a VM also running Windows Server 2012 and it has the Active Directory: Directory Services and DNS ([example.com]) roles. It has been promoted to a domain controller for [example.com].

In the virtualization host I have joined the domain successfully.

I am currently having an issue with our Domain Controller network environment which is on Hyper V. Basically the machine that was hosting the Hyper V has crashed. The problem is not with hard drive but with the corrupted hyper v file.

We have all the vhds and xml configuration files in separate partition. Plan is to make a fresh install of hyper v and reattach all virtual machine.