5.2

Table Of Contents
Change the Encryption Key Cipher for an Existing Local Desktop
To change the encryption key cipher for an existing local desktop, you edit the pae-VM record for the local
desktop in View LDAP on your View Connection Server host.
You
use the ADSI Edit utility to modify View LDAP. The ADSI Edit utility is installed with View Connection
Server. When you change View LDAP on a View Connection Server instance, the change is propagated to all
replicated View Connection Server instances.
Prerequisites
n
Change the encryption key cipher for local desktops. See “Change the Local Desktop Encryption Key
Cipher for New Key Generation,” on page 325.
n
See the Microsoft TechNet Web site for information on how to use the ADSI Edit utility on your Windows
operating system version.
Procedure
1 If the local desktop is checked out, check it in and remove any existing local files.
2 Start the ADSI Edit utility on your View Connection Server host.
3 In the Connection Settings dialog box, select or connect to DC=vdi, DC=vmware, DC=int.
4 In the Computer pane, select or type localhost:389 or the fully qualified domain name (FQDN) of the
View Connection Server host followed by port 389.
For example: localhost:389 or mycomputer.mydomain.com:389
5 In the pae-VM record for the local desktop, clear the values for the pae-mVDIOfflineAuthKey,
pae-mVDIOfflineDataKey, and pae-mVDIOfflineObfuscationKey attributes.
6 Check out the local desktop.
View Connection Server generates new keys for the local desktop. The new keys have the new encryption key
cipher value.
Determining the Effects of Deduplication and Compression on Data Transfers
You can determine the extent to which deduplication and compression reduce the amount of data that is sent
over the network during transfer operations. You can obtain data transfer sizes by reading the View Client
with Local Mode logs on the client computer.
During a check in or replication, the local desktop displays the amount of data that would be transferred to
the remote desktop in the datacenter if no optimization took place. This amount does not reflect the actual data
that is sent over the network. The same number appears whether or not deduplication and compression are
enabled.
When both features are enabled, View Client starts by using deduplication to remove redundant data blocks
from the data that will be transferred. Next, View Client either compresses the remaining data or determines
that the data cannot be compressed.
Reading the View Client with Local Mode Logs
To generate log entries that show deduplication and compression statistics, you must set the logs to Debug
mode.
Table 14-5 shows the location of the View Client with Local Mode logs on the client computer.
VMware Horizon View Administration
326 VMware, Inc.