toolsignHi, Richard Mascarenhas here and I wanted to mention an issue you might run into when adding a Windows Server 2008 R2 SP1 Core computer to System Center Virtual 2012 Virtual Machine Manager (VMM). When adding a Core computer you may see the following error:

Error (441)
Agent communication is blocked. On server <HOST_NAME>, the version of virtualization software or the VMM agent is unsupported.

You may also see the following error when installing Microsoft Visual C++ and then the VMM agent manually on the Windows Server Core system:

"The subsystem needed to support the image type is not present"

Typically this will occur if the ServerCore-WOW64 feature is not enabled on the computer running Windows Server Core.

To enable the ServerCore-WOW64 feature, complete the following:

1.       Logon to the Server Core computer as an administrator.

2.       Run the following command exactly as shown:

DISM.EXE /online /enable-feature /featurename:ServerCore-WOW64

NOTE: The feature name 'ServerCore-WOW64' is case sensitive.

3.       Restart the computer when prompted.

Once restarted, try to add the Core server as a host to VMM again. This should fix the issue but if it still fails, install the correct version of Microsoft Visual C++ and then the correct VMM agent manually on the Windows Core server and then try adding the core server to VMM again. Both Microsoft Visual C++ and the VMM agent are found in the location C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\agents\amd64.

Richard Mascarenhas | Support Engineer | Microsoft CTS Management and Security Division

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up:
System Center – Configuration Manager Support Team blog:
System Center – Data Protection Manager Team blog:
System Center – Orchestrator Support Team blog:
System Center – Operations Manager Team blog:
System Center – Service Manager Team blog:
System Center – Virtual Machine Manager Team blog:

Windows Intune:
WSUS Support Team blog:
The AD RMS blog:

App-V Team blog:
MED-V Team blog:
Server App-V Team blog:

The Forefront Endpoint Protection blog :
The Forefront Identity Manager blog :
The Forefront TMG blog:
The Forefront UAG blog: