Adding Windows 2008 SP2 Server Core as a managed host in System Center 2012 Virtual Machine Manager fails

Symptoms

Adding Windows 2008 SP2 Server Core as a managed host in System Center 2012 Virtual Machine Manager (VMM) fails with one or more of the following errors:

Scenario 1:

Error (415)
Agent installation failed copying C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\agents\I386\3.0.6005.0\msiInstaller.exe to \\core2008.contoso.local\ADMIN$\msiInstaller.exe.
The network path was not found

Recommended Action
1. Ensure core2008.contoso.local is online and not blocked by a firewall. 
2. Ensure that file and printer sharing is enabled on core2008.contoso.local and it not blocked by a firewall. 
3. Ensure that there is sufficient free space on the system volume.
4. Verify that the ADMIN$ share on core2008.contoso.local exists. If the ADMIN$ share does not exist, reboot core2008.contoso.local and then try the operation again.

Warning (10444)
The VMM management server was unable to impersonate the supplied credentials.

Recommended Action
To add a host in a disjointed domain namespace, ensure that the credentials are valid and of a domain account. In addition, the SCVMMService must run as the local system account or a domain account with sufficient privileges to be able to impersonate other users.

Scenario 2:

Error (410)
Agent installation failed on core2008.contoso.local.
The RPC server is unavailable

Recommended Action
Try the operation again. If the problem persists, install the agent locally and then add the managed computer.

Cause

These errors are the result of a connectivity issues between the VMM server and the new host. In the case of a Windows 2008 SP2 Server Core host, the default Windows Firewall settings are blocking the operations. 

Resolution

To resolve this issue perform the following: 

If you are encountering the errors in Scenario 1, execute the following two commands at a command prompt:

netsh firewall set service fileandprint enable netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes  
If you are encountering the error in scenario 2 only, you only need to enable the rule for WMI:

netsh advfirewall firewall set rule group="windows management instrumentation (wmi)" new enable=yes  




Properties

Article ID: 2693650 - Last Review: Jul 9, 2012 - Revision: 1

Microsoft System Center 2012 Virtual Machine Manager

Feedback