cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Veritas.com
Support

client-driven migration has not been selected for this pst file

rouute
Level 6

‎11-03-2009 04:05 AM

how come some pst files get migrated and some do not? for instance one user will have a pst get migrated and the same user will have one or two thats says "client-driven migration has not been selected for this pst file". Why would EV say that baout one pst and not another? Those pst files also say "Do Not Migrate" but changing them to "Ready to Copy" doesnt change anything.

How do you select the individual pst file to be a client driven pst file?

these pst are on the same local C drive.

do those have to go via server side?
0 Kudos
7 REPLIES 7

rouute
Level 6

‎11-03-2009 04:46 AM

I checked a pc and found the following:

After looking at log – the pstimport setting is set to 0, the setting should be a 1. The registry should also have the below entry but did not.
 
HKEY_CURRENT_USER\Software\KVS\Enterprise Vault\Client\PSTImportEnabled = 1



is ok to modify the client log so the pstimport setting is a 1?
0 Kudos

John_Mason
Level 3
Employee

‎11-03-2009 08:28 AM

The registry is not going to contains that setting. That is a setting that is contained in the Hidden messages of the mailbox or OST file(which may be the cause). I would try disabling that user for PST Migration in  the VAC and then do a SYNC. Once it has sync open Outlook and if in Cache mode then wait for the OST file to update and then close Outlook. Then re-enable the user for PST Migration and again SYNC. See if this changes that field automatically in the Hidde Messages. If not then you have a issue with the sync not happening or the OST file not taking the update.
0 Kudos

rouute
Level 6

‎11-04-2009 07:27 AM

SYNC?

0 Kudos

rouute
Level 6

‎11-04-2009 07:32 AM

I got it.
0 Kudos

rouute
Level 6

‎11-04-2009 07:43 AM

tried that approach, client drivend pst migration still not enabled.
0 Kudos

Kopfjager
Level 5
Employee Certified

‎11-04-2009 01:37 PM

It sounds like the PST may have been originally located by the Server side migrator task.  So the Client checks the database and finds that PST already listed.

If that is the case, then you can delete that PST job from the GUI and then retry the Client migration.   It should mention the migration type in the job listing.

0 Kudos

rouute
Level 6

‎11-06-2009 06:21 AM

i think you muissing the point, the clinet isnt even being enabled for client pst migration

the log should have pst enabled =1 in it.
0 Kudos