Common causes for discover server details or add workload job failures

• If attempting to discover a Linux or VMware ESX Server v2.5.x or earlier, the root account or a sudo account is required.  For details on how to setup a sudo account please see TID 7920711 .
  
• Verify that the account being specified for the discovery contains the Administrator role (VMware Infrastructure 3 and higher).
  
• Ensure that the account used for the discovery has SSH access to the Linux Server.
  
• Ensure that the account used for the discovery has Shell access to the Linux Server.
  
• Ensure that the SSHD daemon is enabled on the Linux Server.
  
• If the server is using a non standard SSH port, ensure that the port is specified when entering the hostname or IP  using the following format:  <hostname or IP>:<non standard port>  (i.e.   mylinuxserver:222 )

Checklist for discovering Windows based source and target servers:

• Ensure that Windows Management Instrumentation (WMI) is installed and is running on Source.
  
• Ensure that DCOM is enabled (on the Source machine and Platespin Server - see instructions below on how to check if DCOM is enabled).
  
• Ensure that the RPC service is running.
  
• Ensure that the Remote registry service is running (Please see TID 7920371 for more details).
  
• Ensure that File and Printer Sharing for Microsoft Networks is installed and enabled.
  
• Ensure that the administrative shares Admin$ and C$ on the source server are accessible from the Platespin server.
  
• Administrative credentials are required when discovering Windows servers in order to remotely gather the necessary server details. Try the discovery using a local admin account with the user name syntax: hostname\LocalAdmin or try the discovery with a domain admin account with the user name syntax: domain\DomainAdmin.
  
• If you are using the UPN (User Principal Name) format for the credentials, ensure that the Platespin Server is installed on a Windows 2003 Server ( see TID 7920293 for more information).
  
• If you are experiencing problems discovering a Windows NT 4.0 Server, ensure that the latest WMI core version is installed. (See the link below to download WMI Core V1.5 from Microsoft's web site).  For more details on troubleshooting Windows NT 4.0 Server discoveries, please see TID 7920035 .
  
• If you are experiencing problems discovering Windows XP Professional machines, please see TID 7920350 for more details.
  

If you are still experiencing problems discovering servers after verifying the above, Microsoft's Windows Management Instrumentation Tester (WBEMTest) can be used to troubleshoot WMI connections as follows:

1. On the machine where the Platespin Server is installed, click on the Windows Start button and then select Run
   Type "Wbemtest" (without the quotes) and press Enter.
2. In the Namespace enter in the name of the machine you are trying to discover with \root\cimv2 appended.  For example,  if your machine name is win2k you would enter: \\win2k\root\cimv2  as the namespace
3. Enter in the appropriate credentials using either the hostname\LocalAdmin or domain\DomainAdmin format
4. Click on the Connect button to test the WMI connection.  If an error message is returned after clicking on  "Connect", this indicates that a WMI connection cannot be established between the machine where PowerConvert is installed and the machine being discovered.  Please contact your Support Administrator for further assistance.

1. Click on the Windows Start button and select Run
2. Type "dcomcnfg" (without quotes) and press Enter
3. On a Windows NT/2000 server machine, the DCOM Configuration dialog window should appear.  Click on the Default Properties tab and ensure that "Enable Distributed COM on this computer" is checked.
4. For Windows 2003, the Component Services window will appear instead.  In the Computers folder of the console tree of the Component Services administrative tool, right-click on the computer for which you want to check if DCOM is enabled and then click on Properties.  Click on the Default Properties tab and ensure that "Enable Distributed COM on this computer" is checked."
5. If DCOM was not enabled, please enable it and restart the Windows Management Instrumentation Service (if rebooting the server is not possible) and try the discovery again