We all know how simple it is to deploy a VMM agent to a server using the VMM console but what actually happens behind the scenes?  Hopefully this blog will try to explain that along with enough information to troubleshoot any issues you may be having.  In an controlled environment the following items were used to document this test:

  • Microsoft System Center 2012 Virtual Machine Manager SP1 Beta Management/Console Server.  This server is virtualized. 
  • Microsoft Windows 2012 Standard server.  This is a fresh install, joined to the domain, with no other software installed.  This server is virtualized and is the test server.
  • Process Monitor v 3.03 ( http://technet.microsoft.com/en-us/sysinternals/bb896645 )

Using Process Monitor I excluded all of the currently running processes on the test server.  I then pushed out the agent to the test server that I’ll be using as a library server.  Below are the command lines that I believe are all related to installing the VMM agent from the VMM server.  I’m not going to describe what each command line does.  If you’re at this page you have a pretty good clue what is going on.  If not search for keywords using Bing

C:\Windows\system32\msiexec.exe /V

C:\Windows\\msiInstaller.exe /install WSMANPORT=5985 BITSPORT=443 REBOOT=ReallySuppress 

C:\Windows\\VCRedist.exe /Q

c:\7cd7f6dd8aa5bd9040f92c5dd2\Setup.exe  /Q

C:\Windows\System32\MsiExec.exe -Embedding C1A486DC5357B1B729A4C586C4516646 M Global\MSI0000

C:\Windows\syswow64\MsiExec.exe -Embedding F5D4D7AAAD71DDDF4724511715851B03 M Global\MSI0000

"C:\Windows\SysWOW64\wbem\mofcomp.exe" "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup\VMMAgent.mof"

"C:\Windows\SysWOW64\wbem\mofcomp.exe" "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup\VMMVirtualization.mof"

"C:\Windows\SysWOW64\wbem\mofcomp.exe" "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup\lanSanDeployment.mof"

"C:\Windows\SysWOW64\wbem\wmic.exe" /NAMESPACE:\\root\wmi class MSFC_FibrePortNPIVMethods DELETE 

"C:\Windows\SysWOW64\wbem\wmic.exe" /NAMESPACE:\\root\wmi class MSFC_FibrePortNPIVAttributes DELETE
"C:\Windows\SysWOW64\wbem\wmic.exe" /NAMESPACE:\\root\wmi class MSFC_VirtualFibrePortAttributes DELETE

"C:\Windows\SysWOW64\wbem\wmic.exe" /NAMESPACE:\\root\wmi class MSFC_NPIVLUNMappingInformation DELETE 

"C:\Windows\SysWOW64\wbem\mofcomp.exe" "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup\NPIV.mof"

C:\Windows\system32\PkgMgr.exe /iu:LightweightServer /quiet /norestart

"C:\Windows\system32\dism.exe" /online /quiet /norestart /enable-feature /ignorecheck /featurename:"LightweightServer"

C:\Windows\TEMP\945178FE-ACA5-4159-AD31-33567C8E7A94\dismhost.exe {8C47F553-4E05-4A06-BAAC-22E0605B1535}


C:\Windows\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.2.9200.16384_none_622908ad510eb05b\TiWorker.exe -Embedding


C:\Windows\syswow64\lodctr.exe "/m:C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\scperfprovider.man"

"C:\Windows\SysWOW64\wbem\wmic.exe" /NAMESPACE:\\root\virtualization\\v2 class Msvm_EthernetSwitchPortSCVMMSettingData DELETE
"C:\Windows\SysWOW64\wbem\mofcomp.exe" "C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\setup\scvmmswitchportsettings.mof"

"C:\Windows\SysWOW64\netsh.exe" advfirewall firewall add rule name="HTTPS" action=allow dir=In protocol=TCP localport=443

"C:\Windows\SysWOW64\netsh.exe" advfirewall firewall add rule program="C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\vmmAgent.exe" name=VMMAgent dir=in action=allow

"C:\Windows\SysWOW64\netsh.exe" advfirewall firewall add rule name=HTTP action=allow dir=In protocol=TCP localport=5985

"C:\Program Files\Microsoft System Center 2012\Virtual Machine Manager\bin\vmmAgent.exe"

The command lines below MIGHT be used to clean up the server once the VMM agent has been pushed out by the VMM server but I’m not 100% sure. 
C:\Windows\System32\vdsldr.exe -Embedding