Guest OS Scan
In order to read details about Windows guests as part of the guest OS scan or connect to Windows to run workflow steps, vCommander® must be able to a...
Thu, 13 Jul, 2017 at 10:37 AM
Embotics® vCommander® uses Microsoft’s Windows Management Instrumentation (WMI) protocol to retrieve information about installed software and servi...
Mon, 29 May, 2017 at 1:38 PM
When Embotics® vCommander® is not able to retrieve Guest OS details from Windows VMs, one possible cause is Distributed Component Object Model (DCOM) i...
Mon, 29 May, 2017 at 1:38 PM
Embotics® vCommander® may be configured to scan your guests to retrieve information about their resources. For all guests, the following information is r...
Mon, 29 May, 2017 at 1:37 PM
Embotics® vCommander® uses WMI to retrieve information about the Windows guests in your environment. If one or more VMs are not displaying these details ...
Mon, 29 May, 2017 at 1:35 PM
In the event that you have one or more VMs that you do not want to be
included when the guest OS scan runs, you simply create a new guest OS
scan g...
Tue, 24 May, 2016 at 5:11 PM
Changes introduced in Windows 2008 R2 require Embotics® vCommander® to login to localhost and use it as a proxy to connect to your Windows 2008 R2 guests...
Mon, 29 May, 2017 at 1:35 PM
When a VM appears to be properly configured for guest OS scans, but consistently fails to provide guest details back to Embotics® vCommander®, you can co...
Mon, 29 May, 2017 at 1:33 PM
In order to scan guests and use guest workflow steps, Embotics® vCommander® logs into localhost and uses it as a proxy to connect and perform the scan. ...
Mon, 29 May, 2017 at 1:33 PM
Problem Guest OS Scans for one or more Windows VMs fail, when other similarly configured VMs are successful. You receive an error similar to: VM_NAM...
Mon, 1 Oct, 2018 at 4:09 PM