When Embotics® vCommander™ is not able to retrieve Guest OS details from Windows VMs, one possible cause is Distributed Component Object Model (DCOM) is not enabled for the guest OS. This can be enabled easily by following either the manual or scripted procedures below.


Manual Configuration


When you choose to manually configure DCOM, you must perform the same steps on each virtual machine not providing guest OS details to Embotics vCommander. If you have many virtual machines exhibiting this kind of behavior, you should consider using the computer startup script described in the next section.

  1. Login to the affected VM and issue the command dcomcnfg.

  2. Expand Component Services, computers, and select My Computer.
  3. Right-click My Computer and choose Properties.

  4. Switch to the Default Properties tab.
  5. Check Enable Distributed COM on this computer.
  6. Set Default Authentication Level to Connect and Default Impersonation Level to Identify.
  7. Click OK.
 

Computer Startup Script


When you have many computers not reporting guest OS details to Embotics vCommander, it will be easier to configure a startup script that executes when the OS comes online. The script below can be used to configure DCOM in this manner. 

Set WSHShell = WScript.CreateObject("WScript.Shell")
'To Enable Remote DCOM in the computer
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Ole\EnableDCOM","Y","REG_SZ"
'To Set Authentication Level to Connect
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Ole\LegacyAuthenticationLevel",2,"REG_DWORD"
'To Set Impersonation level to Identify
WshShell.RegWrite "HKLM\SOFTWARE\Microsoft\Ole\LegacyImpersonationLevel",2,"REG_DWORD"

 

See Also


If you require assistance configuring a computer startup script for your Domain, refer to the Microsoft articles listed below.