Deployment Type: Refresh OS Change: XP --> 7 Office Change: 2007 --> 2010 When the user logs in and launches Outlook 2010 post deployment, an error appears for all network based .pst files. Outlook appears to change the mapping from NetworkShareDriverLetter:\Archive.pst (ex. M:\Archive.pst) to C:\Archive.pst which is wrong. However if I go into the data tab of the account to manage the data files the mapping appears correct (M:\Archive.pst). To resolve the issue the mappings have to first be removed then re-added. I was curious if anyone else has experienced this before? As a note the drive mapping is the "home folder" that is set in the User's Active Directory object. Found the issue in the loadstate.log: 2010-10-28 18:24:45, Info [0x080000] Partition mapping (forced): Relocating item(s) from 'M:\Outlook' to 'C:\Outlook' As a note, it doesn't actually relocate the .pst. The .pst still resides on the network share and this behavior is preferred.

I know that the M: drive isn't available when the loadstate.exe process executes. I theorize that because of this loadstate.exe uses some internal processing rules to perform the partition mapping: relocating items action. My question is now how do I stop this from happening?

Total side note: using non-local PSTs is not supported.Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys

Total side note: using non-local PSTs is not supported. Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys I know, I've read the KB article for that. If it were up to me I'd delete all of the .psts in the organization. Unfortunately this is the real world, and in the real world these types of situations exist :)