HVS08 R2 RC disk and device management from remote GUI
- I've installed Hyper-V Server 2008 (HVS08) R2 RC and added it to the domain. When I use Manage Computer from W7, I can see events, manage users, services etc., but these two things fail (from W7 RC client):
Disk Management - thinks about it for a few seconds and then:
on W7: "The RPC server is unavailable"
on HVS08, event ID 1 from source "VDS Basic Provider" with explanation "Unexpected failure. Error code: 490@01010004".
Device Manager - responds almost instantly with:
"Make sure the this computer is on the network [check], has remote administration enabled [check], and is running the 'plug and play' [check] and 'remote registry' [check] services."
Obviously since the MMC is working, I've enabled that and all other remote managment features from the HVS08 R2 menu.
This is a brand new install of HVS08 R2, my download and install DVD are confirmed good. Haven't even tried to create a VM yet.
Answers
- Answer to the Device Manager problem: Enable remote access to PNP using group policy, as explained here:
http://technet.microsoft.com/en-us/library/cc753802.aspx
Disk Management problem is still outstanding. In case there's any doubt, the firewall has been turned off and that made no difference, as expected.- Proposed As Answer byBrian Borg Friday, July 03, 2009 8:33 PM
- Marked As Answer byCarl Houseman Thursday, November 19, 2009 2:32 AM
Did you enable the group policy setting for remote PNP and make sure the policy is applied on the HVS side?
What did you do to make the Disk Management GUI work? It's still not working here and I've been applying all MS-supplied updates.
The advice in this thread worked for me to allow remote Disk Management from Win7. I have not done any group policy updates.
http://serverfault.com/questions/59735/hyper-v-server-r2-disk-management-mmc-returns-rpc-server-is-unavailable
Quote:
You need to change the Firewall rules on both machines (NOT only the Hyper-V Server) Run this command on both machines: netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes
Mark Berry
MCB Systems
- Marked As Answer byCarl Houseman Thursday, November 19, 2009 2:28 AM
All Replies
- Did you enable the remote administration functionality and open the appropriate ports in the firewall?
This posting is provided "AS IS" with no warranties, and confers no rights. Please note that this is the R2 release candidate of Hyper-V 2008 server that I'm talking about.
With that in mind, those questions were either explicitly or implicitly answered in my post. Now, if using the menu to enable remote management is not enough to open ports in the firewall, I'd say that's a design deficiency and an RC2 is needed. But I'm pretty sure the firewall ports are opened by enabling remote management.
Not to mention, if a firewall was blocking something, doubtful it would cause an "Unexpected failure" event to be logged by the "VDS Basic Provider" on the HVS08 server. I post here partly in hopes that someone at MS will become aware of the problems and hopefully fix them before RTM.- If that is your aim, it wasn't very clever to be so short with Mike. If it is a problem that needs to be fixed, Mike is the guy who will be looking at it!
Bill - And I'm the guy working for no pay to help MSFT put out a better RTM product. When I've taken the time to make a detailed report, it would be nice if the response acknowledged that detail in some way.
But if my report is shelved for the reason you suggest, I have better things I can be doing, and there are other virtualization products I could be using/recommending. - Answer to the Device Manager problem: Enable remote access to PNP using group policy, as explained here:
http://technet.microsoft.com/en-us/library/cc753802.aspx
Disk Management problem is still outstanding. In case there's any doubt, the firewall has been turned off and that made no difference, as expected.- Proposed As Answer byBrian Borg Friday, July 03, 2009 8:33 PM
- Marked As Answer byCarl Houseman Thursday, November 19, 2009 2:32 AM
Disk Management problem is still outstanding. In case there's any doubt, the firewall has been turned off and that made no difference, as expected.
Hello everybody!
I'm currently experiencing a similar problem under Build Version 7600 (that is RTM, right?) of Hyper-V Server 2008 R2.
Firewall is off, HV-Server and Win7-Client are members of the same domain.
When trying to connect to Disk Management applet of Remote Server Manager, client recieves "RPC Server unavailable".
On the server, the VDS service stops without an error message. Event ID 4 is logged as informational.
Any ideas how to get remote VDS-Management working?- Hello today i was able to connect to Disk Management
but Device manager i still get the famous error of rpc and remote registry (that are up and runing)
Build Version 7600 Hyper-V Server 2008 R2 - Did you enable the group policy setting for remote PNP and make sure the policy is applied on the HVS side?
What did you do to make the Disk Management GUI work? It's still not working here and I've been applying all MS-supplied updates. Did you enable the group policy setting for remote PNP and make sure the policy is applied on the HVS side?
What did you do to make the Disk Management GUI work? It's still not working here and I've been applying all MS-supplied updates.
The advice in this thread worked for me to allow remote Disk Management from Win7. I have not done any group policy updates.
http://serverfault.com/questions/59735/hyper-v-server-r2-disk-management-mmc-returns-rpc-server-is-unavailable
Quote:
You need to change the Firewall rules on both machines (NOT only the Hyper-V Server) Run this command on both machines: netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes
Mark Berry
MCB Systems
- Marked As Answer byCarl Houseman Thursday, November 19, 2009 2:28 AM
on both machines:
Fantastic! Thank you. I think this topic can finally be closed.
netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yesYou should not have to change any group policy or enable rules on the Firewall. Server 2008 R2 use Server Manager to Enable Remote Management of the Server. If you are using RPC/HTTP then most likely the loadbalancing service for RPC/HTTP is not enabled. Once you enable this you will have disk management function. RPC unavailable is because the server cannot be located because the service to locate the server is not running by default even after you add RPC/HTTP proxy feature. Other services can be enable while you check. I might suggest enable themes service, enable SSDP discovery service. By default I think only the Built in Administrator Account from Windows will have access to the Server. This means unless you provide credentials as actual Administrator Remoting may seem like its broke. I use to be able to use the Admin Tools from other Admin accounts but not anymore. I think this is a security feature of R2. This is good because the default firewall rules have everything disabled but for some reason remote works if you use a built in account that is the same as a built in account on server. It is good practice to Use only built in account to manage server r2. Just enable the built in account on the machine you will remote from and make sure the password is identical to the password for the built in server R2. If you adjust the Firewall Rules or Group Policy I believe it compromises security somewhat on the server. Always work your way backwords when you have a solution. All the changes that are suggested may not be necessary leaving your server security compromised. Hope this helps out.
You should not have to change any group policy or enable rules on the Firewall. Server 2008 R2 use Server Manager to Enable Remote Management of the Server.
Assuming you are talking about Windows Server 2008, that may be true, but Windows Server 2008 was not the topic of discussion in this thread. Please read carefully. It is definitely necessary to make changes to both the firewall and to group policy to remotely manage by GUI these items on a Hyper-V Server 2008 R2 remotely.- Yeah I missed the hyper part. I don't know if UAC affect this in anyway but on R2 only a built in Admin from a Windows machine can manage Server R2 by default. If you change the policy of Win 7 or Vista to prompt for Crendentials for Admin privelage then enter built in credentials everything works but if you use a regular admin it does not. Ive fallen into the practice of Built in Admins having same password machine to machine and enabling the account if necessary. As for the policy change on both machines does not make sense to me. I would think the client default would just prompt for the rule change or allow it by default. I don't know about the Domain but it should be tried both joined and separted from the domain. Is the Domain controller Hyper V or another machine. How is it secure if you alter group policy on the Hyper V server along with the Firewall and it has been joined to a domain. I thought the policy trickeled down from the top. Are you saying change the policy on the Domain or the Hyper V server itself. My problem was the exact same I wanted to use MMC diskmanagement and was rejected. I to could both view remote logs and access registry as well as manage roles but not access disk service.
- If you are only concerned about remote disk management, no group policy changes are involved. See my November 18 post above.
For remote Device Management, you edit the local group policy of the Hyper-V server to Allow remote access to the PnP interface. I didn't try doing this from domain policy.
I blogged this here:
http://blogs.mcbsys.com/mark/post/Managing-Hyper-V-Server-2008-R2-from-Windows-7.aspx
BTW my Hyper-V server is domain-joined and I'm logged on to my Win7 machine as a domain admin when I do these things.
Mark Berry
MCB Systems
