Now, another hurdle is that you can't just install the tools used to manage a Hyper-V server remotely. Installing Hyper-V Remote Management Tools in Windows 7 In my case, all I did was step #1 for the domain user and then logged in as the same domain user on my PC. Allow DCOM access on the client, if neededįrom here, you can double check your configuration on client and server -Ĭscript f /show /target:servercomputernameĬscript f /show /target:clientcomputernameĪll of these steps are covered in much greater detail in the documentation for HVRemote.
Add a firewall exceptions on the client, if needed.Add user rights on server for the clientĬscript f /add:domain\user (if machine is in a domain)Ĭscript f /add:user (if machine is in a workgroup).From your elevated command prompt, you need to do 4 things: To properly run it, you will use cscript, then the name of the script, followed by some options. If you try to run the script, just by itself, you'll see the error in Figure 5. Start up an administrator-level command prompt, as you see in Figure 4. Once downloaded, put it in a place easy to get to, like your Desktop. This script is downloaded and run on your Windows 2008 Hyper-V server and used to authorize remote Hyper-V administration.ĭownload it from the link above. Instead, there is a great script by Microsoft's John Howard called HVRemote. But trust me you don't want to have to go through many pages of instructions. These steps are listed in the Microsoft TechNet article Install and Configure Hyper-V Tools for Remote Administration. There is a ridiculously long list of steps that need to be performed in order to enable remote management with a Hyper-V server.
I will show you how to both enable Hyper-V remote management and install the Hyper-V remote management tools on your desktop PC.Įnabling Remote Management for Hyper-V on the server If you don't configure the Hyper-V server for remote administration and try to run the Hyper-V remote management tools from your desktop, you'll get the error message "you do not have the required permission to complete this task" when you attempt to connect to the Hyper-V Server using the remote management tools. First, you must enable remote management on the Hyper-V server.
However, with Hyper-V, you can't just install the tools on your PC and start using them. You install the vSphere client, and sha-bam, you are managing your ESX Server. With ESX Server, you download the vSphere client directly from the ESX server via your web browser. Having used VMware ESX / vSphere extensively, I thought that this process would be similar. Honestly, when I started looking at this, I didn't think it would be so complex. Thus, you need the Hyper-V tools for remote management up and running whenever you need them. So once you enable Hyper-V, how are you going to manage it from your desktop PC? You do not want to have to use Remote Desktop Protocol (RDP) to connect to the server and launch the Hyper-V manager, every time that you want to administer Hyper-V.
This way, you can get more use out of that one server by running multiple servers on it, and utilize unused CPU and RAM. AVMA is only supported on virtual machines running Windows Server 2012 R2 or later versions of operating systems.For any physical server running Windows 2008, you might as well enable Hyper-V. These Virtual Devices (VDev) are provided for Automatic Virtual Machine Activation (AVMA) to communicate with the host.
If you view the properties of these devices and check driver details, Hardware IDs or Compatible IDs, they will show the following: No guarantees how long MS will allow it will stay up here, though it’s freely distributed with Hyper-V Server.Īfter installing the IC on OSes older than Windows Server 2012R2, you will still see 2 unknown devices. Hyper-V 2008 here: !AnbqFQxI6C6pio4UYt3Jn_VLbrQs4w Hyper-V 2008 R2 here: !AnbqFQxI6C6pio4TpkS4Yi9Pl0_Ejg I’ve got a copy from Hyper-V 2012 R2 here: !AnbqFQxI6C6pibttEpT9LXnRf4jcYg Or, if you’ve got a Windows 8/8.1/2012/2012R2 VM/system available with Hyper-V installed you’ll find it in the C:\windows\system32\ folder. ( to extract, you’ll need to mount the ISO, open the x:\sources\install.wim file with something like 7zip, browse to Windows\system32, and extract the vmguest.iso or install Hyper-V Server in a VM to get the vmguest.iso) You can get the IC from Hyper-V 2012/2012R2 Server, a free download, here:
With Win10/Server2016 they no longer include this ISO as the current “supported” OSes all get their IC viaWindows Update. If you’re playing around with older OSes in the latest versions of Hyper-V, you’re missing one thing, the Integration Components (IC).