Assuming that View Transfer Server is functioning properly, you might find that check-out problems are due to View Connection Server no longer having the encryption key for files on the local machine.

After successfully checking out a local desktop and checking it in, you check the desktop out again, but you cannot connect to the local desktop. You might see an error message such as, Cannot access local desktop--desktop corrupted.

If you change the encryption key cipher for a local desktop, or if you delete the desktop from its pool and create a new one, View Connection Server uses a new authentication key to generate a new configuration file.

When end users attempt to check out the desktop again, only changed files are downloaded. The new files that get downloaded use a new encryption key, but the old files already on the local machine use the old encryption key, which View Connection Server no longer has.

End users must delete all local desktop files before checking the desktop out again.

The folder resides in the local desktop check-out directory. When you downloaded your first local desktop, if you did not click Options and change the directory where the local desktops are stored, they are stored in the default check-out directory.

Desktop Operating System

Default Check-Out Directory

Default directory on Windows 7 and Windows Vista

C:\Users\User Name\AppData\Local\VMware\VDM\Local Desktops\pool_display_name

Default directory on Windows XP

C:\Documents and Settings\User Name\Local Settings\Application Data\VMware\VDM\Local Desktops\pool_display_name