FIX: Pools or virtual machines remain listed in VirtualCenter after being deleted in View Manager

Symptoms

• A pool is deleted from disk in View Manager from View Administrator > Desktops and Pools
• Some virtual machines from the deleted pool remain in VirtualCenter
• In View Administrator > Desktop Sources, the virtual machine show a status of Deleting, however the objects never get deleted

Resolution

The virtual machine may not be deleted when View Manager is unable to process the shut down command.

To workaround the issue:

1. Manually shutdown the virtual machine and wait a few minutes. VirtualCenter automatically continues with the cleanup process and deletes the virtual machine.
2. If the virtual machine is deleted from VirtualCenter or you have manually deleted the virtual machine but it still appears up in Desktop Sources, the virtual machine entry must be removed from ADAM.
   
   Warning: Editing or deleting items within ADAM may destroy existing pools in View Manager. Backup the configuration data before making any changes. For backup instructions, see http://www.vmware.com/pdf/vdm_config_data_export_import.pdf.
   
   
   1. Open the ADAM editor, click Start > Programs > ADAM > ADAM ADSI Edit.
   2. Right-click ADAM ADSI Edit and select Connect to.
   3. Choose Distinguished name (DN) or naming context and type:
      
      dc=vdi,dc=vmware,dc=int
      
      
   4. Under OU=Servers, double-click each entry and search in Attribute > pae-DisplayName for the corresponding virtual machine name.
   5. Delete the appropriate entry that contains the virtual machine name.
   6. Refresh the Desktop Sources view. The virtual machine is no longer listed.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007510

The Home Folder may be mapping incorrectly when logging on to a Windows XP-based computer

Symptom:
When you log on to a user account on a Windows XP- based computer with drives that are mapped to a Home Folder on a network, the Home Folder may be mapped to the base share instead of the complete path.

Example scenario:

• 
  The Home Holder is set to: \\fileServer\share\UserName
• 
  The actual mapping that the user receives is \\fileServer\share

Note: Manually mapping the path completes successfully and all files are accessible, but the scenario may repeat when the user logs in again.

Cause:

This issue may occur if due to one of the following reasons:

• 
  Under Group Policy, in User Configuration -> Administrative Templates -> System -> User Profiles -> Connect home directory to root of the share is set to Enabled.
  
• 
  Network delays cause the workstation to try to map to the home folder before it completes initializing the network connection during logon.

Resolution:

To resolve this issue, do the following:

• Make sure you do not have the policy configured in User Configuration -> Administrative Templates -> System -> User Profiles -> Connect home directory to root of the share

• Set the Group Policy setting under Computer Configuration -> Administrative Templates -> System -> Logon -> Always wait for the network at computer startup and logon to Enabled.

http://support.microsoft.com/default.aspx?scid=kb;EN-US;969006