5.2

n
View Transfer Server Fails the Health Check on page 345
In View Administrator, View Transfer Server displays a status of Bad Health Check. The View
Administrator dashboard displays View Transfer Server with a red down arrow.
n
The Transfer Server Repository Is Not Configured on page 345
In View Administrator, View Transfer Server displays a status of No Transfer Server Repository
Configured.
n
View Transfer Server Instances Have Conflicting Transfer Server Repositories on page 346
In View Administrator, View Transfer Server instances display a status of Transfer Server Repository
Conflict.
n
The View Transfer Server Web Service Is Down on page 346
In View Administrator, View Transfer Server displays a status of Web Server Down.
n
Local Mode Operation Fails After the Datacenter Desktop Was Modified on page 346
During a local mode operation such as a check-out or check-in, the operation fails, and the following
message is displayed: This desktop has been modified at the datacenter. Please contact your
system administrator.
n
Recover Data from a Local Desktop on page 348
View secures the virtual machine of a local desktop by encrypting all of its virtual disks. If the virtual
machine's checkout identifier is deleted from the configuration, or the session or policy files become
corrupted, you might not be able to power on or check in the local desktop. You can decrypt the local
desktop's virtual machine so that you can recover data from it.
Check-Out Fails with "No Available Transfer Server" Error
When users try to check out desktops, the operations fail and an error message, No available Transfer
Server, is displayed.
Problem
The
check-out can fail when the operation is approximately 10% complete, before View Transfer Server begins
transferring data to the client computer. The check-out can also fail later in the process. For example, the base
image might be transferred to the client computer, but other virtual machine disks cannot be transferred.
This problem occurs with all check-out operations that are managed by a particular View Transfer Server
instance.
Cause
This problem can occur because View Transfer Server is running on an ESX host that does not have access to
the datastores where the desktops reside. During a check-out operation, View Transfer Server transfers desktop
data from the datastores to the client computer. The datastores must be accessible from the ESX host where
the View Transfer Server virtual machine is running.
Solution
n
Migrate the View Transfer Server virtual machine to an ESX host with access to the datastores.
a In View Administrator, place the View Transfer Server instance in maintenance mode.
b In vSphere Client, use the Migration wizard to migrate the View Transfer Server virtual machine to
the destination ESX host.
c In View Administrator, select the View Transfer Server instance and exit maintenance mode.
Chapter 14 Managing Local Desktops
VMware, Inc. 341