Environment
This article outlines the troubleshooting procedures for Virtual Servers discovery issues. More specifically, if a Virtual Server was successfully discovered but the Virtual Server is not available under the Target Machine Column.
Situation
The occurrence of this behavior generally indicates that:
· VMware GSX Server VmCOM API was not installed on the POrtability Suite Server prior to the VMware Server discovery. For more information on how to install VMware Server VmCOM API please refer to Knowledge-Base article Q20114
· The Virtual service on the Virtual Server has not started – please make sure that the Virtual Server service on the Virtual Server is running (Under Services and Application), if the service is not running please run it and re-discover the server - (Applies for GSX and Microsoft Virtual Server 2005)
· If Domain Administrator credentials (Domain\Administrator) were used for the Virtual Server discovery and the server is not under Target Machine Column, you will need to use the server’s local administrator credentials to discover the Virtual Server (Computer\Administrator) - (Applies for VMware Server and Microsoft Virtual Server 2005)