So after some 22,000 downloads (thank you) in the 8 months since first released, HVRemote has undergone a refresh to make it even easier to configure Hyper-V Remote Management and diagnose issues.
The major change in version 0.7 is the ability to perform some verification of the configuration and provide hints as to what to follow if it detects an error through the use of the new /target option. Below is an example of the new bit of output running hvremote /show /target:servername from a Windows 7 client where everything is working just fine (yes, it is fine for the ping to timeout, that just means it’s blocked by the firewall).
HVRemote 0.7 fully supports Windows Server 2008 R2, Microsoft Hyper-V 2008 R2 and Windows 7. In addition, the home page has undergone a refresh to cover the some of the most commonly asked questions, and the documentation has been brought up to date.
For a list of other changes, please see the documentation.
Thanks, John. Valuable additions to HVRemote, and much appreciated.
Essential with Hyper-V core R2 and Windows Server 2008 SP2 even with both computers in the same domain.
Thanks John; saved me a lot of 'aggro'
Any idea why I would be getting an undeterminated entity reference error?
C:\>cscript hvremote.wsf /add:david
Microsoft (R) Windows Script Host Version 5.7
Copyright (C) Microsoft Corporation. All rights reserved.
C:\hvremote.wsf(5872, 37) Windows Script Host: Unterminated entity reference - matching ';' not found
David - what version of HVRemote are you running, and where did you download it from? The reason I ask is that v0.7 (only!) has 5679 lines in the file, so I can only assume you have a corrupt download of some sort. Can you try downloading it again from code.msdn.microsoft.com/hvremote.
How do i install this on my server core?
its colo and I dont have access to it.
Just have Remote desktop client working.
Thanks in advance
Frank - you could use copy/paste through an RDP session. Without explorer on core, you could probably paste the text into a notepad session. However, I would strongly recommend that you do not deploy in this manner (assuming you mean you intend managing the Hyper-V machine directly over the internet) without something such as a TS gateway or similar deployed in front of it ensuring that the system is secure. Opening the WMI management interfaces directly to the Internet is a significant attack vector.
Why isn't it recommended to use HVRemote in a VMM managed environment? What are the technical difficulties that might occur? I'm planning a Hyper-V deployment with HVRemote and still have to decide if I integrate the hosts in VMM or not.
Thars - VMM manage their own authorization and delegation model and push policy from their servers to the Hyper-V machines. Hence any changes made by HVRemote would be lost. Similarly, changes that HVRemote have the possibility of making the server inaccessible by VMM.
hi John, I am not able to locate version 1.x, please advise url. regards, Malcolm