Client Driven Migration PST's remain in a Migrated state when using Citrix/Terminal Services
Article ID: 100022720
Updated On:
Cause
In a Citrix/Terminal Services environment the registry may change per log on. If a client driven migration is started when logged into one session the registry key is created, when logging in the next time, the session may be controlled by a different server and the registry key may not be present. Without the FileID registry key the client is unaware of the migration so will not continue with the remaining chunks. Also the client will not start to migrate the PST again as the PST already has an entry in the PstFile table.
Resolution
Registry Settings:
HKEY_CURRENT_USER\SOFTWARE\KVS\Enterprise Vault
HKEY_CURRENT_USER\SOFTWARE\KVS\Enterprise Vault\Client
"FixedPreviewPane" = dword:0000000a
"OLBarState" = dword:00000000
"LastPSTSearch" = "20091130"
"LoggingLevel" = dword:00000003
HKEY_CURRENT_USER\SOFTWARE\KVS\Enterprise Vault\Client\
HKEY_CURRENT_USER\SOFTWARE\KVS\Enterprise Vault\Client\
HKEY_CURRENT_USER\SOFTWARE\KVS\Enterprise Vault\Client\
"LastItemNum" = dword:0000012c
"LastCopiedChunk" = dword:00000001
"FailedItems" = dword:00000000
HKEY_CURRENT_USER\SOFTWARE\KVS\Enterprise Vault\Client\PSTsMarked
"ce1e4bf56040bb45a629a66220cba26f" = "Personal Folders"
To find the FileID of the pst being migrated
1. Open the Vault Admin Console (VAC)
2. Expand Personal Store Management
3. Click on Files
4. In the right hand window right click on the entry for the PST file and select properties
5. Under the general tab, make a note of the name in the Holding File box
6. If the name is PST1234_20.pst, the PST FileID is 1234 and chunk number is 20
Workaround
To disable client driven migration while the user is logged into a Citrix/Terminal Services session, but enable client driven migration for the same user when not in a Citrix/Terminal Services session, and only using one policy.
Add the DWORD below to the registry when in a Citrix/Terminal Services session with a value of 0 which will override the policy setting and disable client driven migration, this could be done via a logon script.
DWORD : PSTImportEnabled
Location:
HKEY_CURRENT_USER\SOFTWARE\KVS\Enterprise Vault\Client
DWORD Values
0 - Disables client-driven PST migration.
1 - Enables client-driven PST migration.
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.
Applies To
All supported versions of Enterprise Vault
Issue/Introduction
For client driven migration to work, a PST is given a FileID, a registry key with the FileID as the name is created, Under the registry key there are three DWords which contain information on the progress of the migration, an example is shown below
HKEY_CURRENT_USER\SOFTWARE\KVS\Enterprise Vault\Client\<SiteEntryID>\PSTImport\<PST FileID>
DWords
LastCopiedChunk - the id of the last chunk to be successfully uploaded to the server
LastItemNum - the index number of the last item to be copied into the last PST chunk to be successfully uploaded
FailedItems - a running total of the number of items that could not be copied from the source PST file into the PST chunks
