can't connect to VDS on server core installation
-
Thursday, July 28, 2011 7:07 PM
I have 2 servers i am configuring for hyper-v running server 2008R2 enterprise x64. I have done the following steps
on server core box
netsh advfirewall firewall set rule group="Remote Administration" new enable=yes
sc config vds start= demand
net start vds
netsh advfirewall firewall set rule group="Remote Volume Management" new enable=yes
Set Allow remote access to the PnP interface. in GPO
netsh advfirewall firewall set rule group="Windows Firewall Remote Management" new enable=yesalso verified GPO settings for RPC are not set and verified permissions for DCOM Objects
when connecting to disk management snap-in on remote system running windows 7 sp1 with RSAT installed I get "you do not have access rights to logical disk manager on %computername%"
the two servers are in the same domain as the windows 7 workstation used for management. user accounts used to administer servers are added to DCOM Group of local servers.
anyone have any ideas ?
All Replies
-
Friday, July 29, 2011 5:42 AM You must also enable the "Remote Volume Management" rule group and start the VDS service on the Windows 7 machine (it makes no sense, but it MUST be done). Failure to do so will usually result in RPC errors, but I'm wondering if it's not still responsible for your error. Try it if you haven't already.
- Proposed As Answer by Borodin Andrey Wednesday, January 04, 2012 6:30 AM
-
Friday, July 29, 2011 6:06 AMModerator
Hi,
You must first start the Virtual Disk Service (VDS) on the computer running a Server Core installation. You must also configure the Disk Management rules appropriately on the computer that is running the MMC snap-in.
For more information, you can refer to page 48 to page 50 in the following guide.
http://www.microsoft.com/download/en/details.aspx?id=16065
Vincent Hu
-
Friday, July 29, 2011 11:59 AM
You must also enable the "Remote Volume Management" rule group and start the VDS service on the Windows 7 machine (it makes no sense, but it MUST be done). Failure to do so will usually result in RPC errors, but I'm wondering if it's not still responsible for your error. Try it if you haven't already.
Forgot to add that in to my initial post but I have done this as well. thanks for the help though
-
Friday, July 29, 2011 12:05 PM
Hi,
You must first start the Virtual Disk Service (VDS) on the computer running a Server Core installation. You must also configure the Disk Management rules appropriately on the computer that is running the MMC snap-in.
For more information, you can refer to page 48 to page 50 in the following guide.
http://www.microsoft.com/download/en/details.aspx?id=16065
Vincent Hu
Thank you for the help but as mentioned in my initial post this has already been done.
I used the SC command to set the Virtual disk services to run on demand and followed that with the net start to start the VDS service. i verified through MMC services snap-in that the service was started prior to trying to connect to the VDS through disk management. -
Friday, August 05, 2011 4:17 PManyone else have any ideas ?
-
Wednesday, December 07, 2011 7:35 PM
I finally got a fix for this after taking a step back from the project for a few days. I did a capture of the network traffic that showed I was running into an issue with DCOM permissions in the domain
My 2 server core installations were receiving group policy settings that were restricting my dcom permissions and causing this error
I moved my servers into a now OU in active directory and disabled policy inheritance created a new policy specifically to my server core installs and this resolved the issue
- Marked As Answer by James Kulikowski Wednesday, December 07, 2011 7:36 PM
.png)
