Questions[hyper-v-server-2008-r2](server)

Is it possible to remotely manage Hyper-V running on Windows Server 2008 R2 with the Hyper-V Manager on Windows 10? I know that the Hyper-V Manager on Windows Server 2012 R2 is not backwards compatible with 2008 R2 (I don't know if Microsoft decided to add backwards compatibility for Hyper-V in Windows 10).

I have a Windows 10 vm with Hyper-V installed and when I try to connect to the host as a domain admin, I get a message that says:

An Error occurred while attempting to connect to server "Virtual1".
Check that the Virtual Machine Management service is running and that you are authorized to connect to the server. 

You do not have the required permission to complete this task. 
Contact the administrator of the authorization policy for the computer 'Virtual1'.

This error message doesn't tell me if I'm wasting my time or not and I have not found any websites stating that Windows 10 Hyper-V Manager is not backwards compatible with Windows Server 2008 R2. I've tried running winrm quickconfig on the host machine, as recommended on another ServerFault page for Windows 10 and Windows Server 2012 R2, but that doesn't seem to help. I'm able to remotely manage Hyper-V on my Windows 7 machine without any problems.

Any help will be greatly appreciated.

I've got a CentOS VM (release 6.2) running under HyperV. I have integration services installed (part of base now), and CentOS shows the current clocksource is hyperv_clocksource, however my time in the VM is about 10 minutes fast after a week of uptime. My understanding of the new IC and plugable clocksource is that this shouldn't happen any more. Is there any additional configuration necessary to get the plugable clocksource to "work?"

I know there are plenty of links about setting kernel options to PIT and various stuff like that, but those all seem to pre-date the integrated clocksource support, and as I understand it shouldn't be needed anylonger. Nor should ntpd nor adjtimex.

Edit: Was running 3.2 of IC (what ships w/Centos 6.2), upgraded to 3.3 today, machine has been up for 1 hour 22 minutes and clock is already 5 seconds fast. So I'm now running the latest IC and still have the same problem.

We have recently purchased a server which is running Hyper-V 2008 R2 bare metal. The server has two quad-core Intel Xeon processors with hyperthreading, so if I'm understanding correctly this gives us 16 cores. Within Hyper-V we have created a virtual machine running Windows Server 2008 R2 with 4 virtual processors. The processor settings screen is telling me that this represents 25% of the total system processing power. Does this mean that the remaining 75% can not be tapped into by the virtual OS? We will be running a few other virtual machines, but this one is for SQL Server and we'd like to throw as much horsepower at it as possible.

Using Hyper-V, what are the pros/cons of using the "Physical Hard Disk" option when adding a drive to a VM as opposed to just creating a fixed-size VHD that is as large as the disk?

The intention is for this disk to be allocated to a single VM so there isn't any requirement to have anything else using it.

I'm having an issue on my server when working with my VM guests, and I think its due to a recently installed update. What is the correct command to uninstall Windows Updates from either the command prompt, or Powershell?