Today I had to virtualize several Windows 2008 R2 Terminal server. After a successful conversion I ran into a problem when installing the VMware Tools.

Error 1606. Could not access network location [servername]\[sharename]\desktop\programs\startup\.

This error is caused by a Group Policies that was redirecting the start menu to another server (also for the domain administrator and local administrator). Because I started the VM in an isolated environment it was unable to check the free disc space of the network share and gave me this error. This error is discussed in VMware KB1017886.

In my case there were two directories redirected to a server that was not reachable for this server. I also checked the Current User settings, but there was nothing directing to the unreachable server.

To solve the error change both register keys to their original settings. 

• The “Common Startup” key should be “%ProgramData%\Microsoft\Windows\Start Menu\Programs\Startup”
  
• The “Common Programs” key should be “%ProgramData%\Microsoft\Windows\Start Menu\Programs”
  

The original setting of all the keys. 

Restart the VMware Tools installation and now everything should work without any problems.

More information:

• Microsoft KB886549.
  

After en APD (All Path Down) in our hosting environment I had the following error when I tried to do something with the ESXi datastores.

The VMware environment was working correctly.
I started searching the VMware Knowledge base and found KB2064174. This KB describes exactly my problem.

Symptoms 

• Selecting/browsing a datastore, the VMware vCenter Server 5.1.x displays the error message:

com.vmware.sps.fault.qsconnectionException

• Selecting the Storage Views of any datastore displays the error message:

cannot initiate storage service

• vMotion or an offline migration of a virtual machines fails with the below error message:

pbm.fault.PBMFault.summary

Resolution

To resolve this issue, ensure the VMware inventory service and the VMware profile Driven Storage Service are running.

1. Log in as an administrator to the server that is running the vCenter Server.
   
2. Click Start > Run.
   
3. Type services.msc
   
4. From the list of services, check the status of the VMware inventory service and the VMware profile Driven Storage Service.
   
5. If any of these services are not running, right-click on the service and select Start. (A restart of the services may be applicable as well).
   

Note: If both of the services are not running, start the Inventory service first and the Profile Driven storage service second.

For VMware vCenter Appliance 5.x

Restart virtual center server through the web interface.

1. Log in to the vCenter Server Appliance’s VAMI (Virtual Appliance Management Interface) at http://<IP/hostname of VC>:5480
   
2. Select the Summary tab under vCenter Server.
   
3. Click Stop beside vCenter Server to stop the process.
   
4. Click Start beside vCenter Server to start the process
   

In my case all the services where running, so I restarted the VMware vCenter Inventory services. After this restart the error message disappeared when browsing the datastores.