Migration of Exchange mailbox can be done with the ExProfre.exe tool. But at times, when the ExProfre.exe tool migrates the Exchange Server user profile, it results in numerous synchronization problems. Synchronization error messages appear in the event log. In such pathetic situations, you face problems while converting OST file into PST file. To overcome these situations a third-party OST to PST converter is needed. With the help of a converter, you are able to convert OST to PST with much ease.
Let's discuss what kind of synchronization problems occur when you use Exprofre.exe (Exchange Profile Update Tool) to migrate a user profile of Microsoft Exchange Server:
Numerous synchronization errors appear on screen. You can see these errors in synchronization log.
Synchronization of organizational forms does not occur. As a result, messages requiring organizational form get displayed without form data.
Synchronization of security settings of MS-Outlook doesn't occur So, if new public folder applies new security settings, then these settings remain unavailable.
Synchronization of favorite folders of Public Folder cannot be done. All the Items that are contained in that folder remain unsynchronized.
Synchronization log contains the below events in it:
Let's discuss what kind of synchronization problems occur when you use Exprofre.exe (Exchange Profile Update Tool) to migrate a user profile of Microsoft Exchange Server:
Numerous synchronization errors appear on screen. You can see these errors in synchronization log.
Synchronization of organizational forms does not occur. As a result, messages requiring organizational form get displayed without form data.
Synchronization of security settings of MS-Outlook doesn't occur So, if new public folder applies new security settings, then these settings remain unavailable.
Synchronization of favorite folders of Public Folder cannot be done. All the Items that are contained in that folder remain unsynchronized.
Synchronization log contains the below events in it:
Root of the issue:
Above problem occurs due to entryid values. Entyrid values are the values that MS-Outlook application uses to locate public folders. But the values get changed when you migrate mailbox. OST file do not get updated using ExProfre.exe tool. Thus, new entry id values are not found by the OST files. Which finally results in OST file inaccessibility. And in such situation you do not have any server backup of your mailbox data, you only have the .ost file that contains all your data, and it can not be imported to .pst file directly.
Resolution:
You can easily disregard this issue if the below conditions are true:
Organizational forms are not used by the clients.
There is no need for customized security settings of Outlook.
Favorites stored in public folder are not used by the clients.
Otherwise, create a new MS-Outlook profile and later connect it to the migrated MS-Exchange mailbox. For doing this, convert OST file manually and then connect it to MS-Outlook profile. It is possible to use a third party OST PST converter. With the aid of these tools, you can convert OST to PST data easily and quickly. Your unusable OST file gets converted into usable PST file. Once you get your OST file converted into PST file you can directly import that PST file in MS Outlook to access your data. To import a PST file in Outlook
- Open Outlook.
- Go to File menu, click Import And Export.
- Click Import from another program or file, then click Next.
- Click Personal Folder File (.pst), then click Next.
- Type the path and the name of the .pst file that you want to import, and then click Next.
- Select the folder that you want to import. To import everything in the .pst file, select the top of the hierarchy.
- Click Finish.
by: DrUltima on 2011-02-28 at 07:54:26ID: 24153
I am not sure I understand the value of this Article. If you have sync problems after migrating from one information store to another, why not just delete the profile and recreate it. I see no value in importing a converted PST, as that data would be stored in the Exchange server (else you would not have an OST). If you are having to do such an import, you are assuming a complete migration failure, and if that is the case, then you would need to address the problem at the server level first. You Article doesn't even mention server side troubleshooting for failed migrations.
It seems to me that it is basically an advertisement for software more than a "how to".
DrUltima