Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a hyper-v-server-2012-r2 Core server thats not joined to any domain.

What configuration must i do on the server and client to connect with MMC \ Device Manager?

I have managed to connect with the Computer Management to the server and i can access every thing in there but the device manager (and a few more that im not interested in)...

When i click the Device manager i get the following error: Error

I have checked and both services are running..

If possible i would like a step by step guide what to do on a freshly installed Hyper-v Core server to get every thing in Computer Management remotely accessible including Device Manager.

share|improve this question

3 Answers 3

I actually managed to access the device manager of a remote machine.

Make sure both the PnP service and the remote registry service are running on the remote machine.

Then there is actually a group policy setting that handles whether or not you are able to remotely access a machine's plug and play service (which is what device manager actually connects to) its under Computer Configuration\Policies\Administrative Templates\System\Device Installation and it's called "Allow remote access to the Plug and Play interface".

You can use gpedit.msc to manage the local group policy configuration since the machine is not in the domain.

Simply create a new mmc and add the device manager snap-in and you can specify the computer to connect to.

share|improve this answer
    
Cool, but one question the "Allow remote access to the Plug and Play interface" did you change that on the server or the client. (The server is a Core installation so im unsure if i can access MMC) –  Peter Mar 18 at 9:07

It seems using "Device Manager" on a remote machine does not really work, this TechNet thread discusses this.

They suggest using PowerShell Device Management Cmdlets. Personally I use devcon.exe which is a command line version of device manager. So far everything I needed to do was possible with it, and it is nice, because you can use it in your setup-script.

share|improve this answer
    
Thanks a lot for your answer it explains a lot, but why do they allow me to connect remotely with Device Manager if it doesn't work? –  Peter Oct 25 '13 at 14:31
    
@Petoj - I assume you are using Server Manager, right click a server and select 'Computer Management'. Now you get the standard computer management mmc. This is the exact same mmc, you would get locally, so it has all the nodes available locally. I agree they should disable device manager just like they do with local users. –  Peter Hahndorf Oct 25 '13 at 14:43
    
yes i am actually trying to use Server Manager but the only part i have been able to get to work is the Computer Management, if i just try to manage it with the Server Manager i get some cryptic Kerberos resolution error. –  Peter Oct 25 '13 at 14:53
up vote 0 down vote accepted

In my case running the following in powershell solved the problem. winrm quickconfig aand then winrm set winrm/config/client '@{TrustedHosts="RemoteComputerName"}'.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.