Another variation on PST migration ?
Ladies and Gentlemen,
I suspect I'm not the first to try this, nor do I expect to be the last !!
My environment: Exchange 2007, EV 2007 (7.5 sp3).
The 'other, legacy' environment had Exchange 2003, Outlook 2003 and a vast number of PST files stored on their users laptop or desktop machines,
The company I work for has recently absorbed another company,
We're migrating the other companys' users into our Exchange 2007 environment, giving them new user-ids, Exchange mailfiles Outlook 2007 clients and so on. All was going well, until they asked that their old PST files from their Exchange/Outlook 2003 environment were migrated into their new EV mail archives.
I've created a Provisioning Group, a PST Policy document, a PST migration task that is scheduled and running..
Problem is that its not picking up the merged users' (Exchange /Outlook 2003) PST files from their laptops/desktops.
I'm using the client driven process, which I hoped would 'mark' their PST files and proceed to migrating the content into the users new EV mail archives.
I suspect that because the PST files were associated with the users' old company's profile, they can't be "seen" via the new profiles the users are now using for our company's Exchange 2007 environment.
All of the users with PST files are remotely based or on customer sites.
Appreciate any guidance you can offer?
Thanks
Comments
Some random thoughts
Some random thoughts ...
These PSTs are they on the users workstations?
Does your policy scan the whole machine or just the Documents and Settings folder (and the PSTs are stored outside that)?
Did you synch the mailbox after doing the policy work?
On the Desktop Policy in the VAC, under advanced -> outlook, there is a setting called PST Search Interval. The default is 7, meaning that the scan only takes place once every 7 days. You can decrease that interval, or remove the registry key (called LastPSTSearch) on a test client machine.
Finally, do you have a client log with max logging enabled .. that will explain (hopefully) what happened.
Some additional thoughts
Does the Vault Service account have access to the target location of pst files?
Are the computers being located by the Location task? If no, did you try doing a netbio based search?
-Craig Champagne
www.bluesource.net
Check out our services for the US and the UK
EV_Notice, For clarity, the
EV_Notice,
For clarity, the client side migration does not mark the pst this is done via the EV Client Add-on and based on the desktop policy setting (Mark PSTs) which is on by default.
I've found client-side migrations frustrating for most admins since it is not very clear what is happening when. Here's some general tips that might help.
1. Enable minimum tracing logging (press CTRL+Shit and click on any ev toolbar icon. The log file will give you alot of information as to when & what the pst search finds. The EV client is doing the pst search and will be able to find (based on policy setting as Rob noted above) any pst the end-user could find on the local hard disks.
2. During troubleshooting get use to deleting the LastPSTSearch key as Rob suggests. Restart Outlook and look for the results. Also available is the "restart search" box from the CTRL+SHIFT click (step 1) menu which I think does the same thing and deleting the lastpstsearch key
3.Basic step that I'm sure you have already done: Enable users for pst migration: in the admin console, rt-click the "personal store management" and select users.
Regards
Joe
Would you like to reply?
Login or Register to post your comment.