Difference between revisions of "Zimbra Outlook PST Import Wizard Tips"

(First Commit of PST Import Tips)
 
(updated really outdated 'ram requirement' memory tuning info to point to the perf tuning guide instead)
 
(15 intermediate revisions by 6 users not shown)
Line 1: Line 1:
 +
{{BC|Community Sandbox}}
 +
__FORCETOC__
 +
<div class="col-md-12 ibox-content">
 
=Zimbra Outlook PST Import Wizard Tips=
 
=Zimbra Outlook PST Import Wizard Tips=
 +
{{KB|{{Unsupported}}|{{ZCS 5.0}}||}}
 +
 +
{{Archive}}{{WIP}}
 +
 +
 
Sometimes you may have difficulty importing your PST with the Zimbra PST Import Wizard.  This may be due to the version of your PST file (i.e. Outlook 2000), the condition of your PST file, or emails with unusually large attachments.  Here are a few tips that might help solve some sticky PST import problems.
 
Sometimes you may have difficulty importing your PST with the Zimbra PST Import Wizard.  This may be due to the version of your PST file (i.e. Outlook 2000), the condition of your PST file, or emails with unusually large attachments.  Here are a few tips that might help solve some sticky PST import problems.
  
 
==Outlook Version==
 
==Outlook Version==
* You must have Outlook XP or 2003 installed on the machine you are running the Import Wizard on (ideally Outlook 2003).  <b>Outlook 2000 and earlier is not supported</b>.  If you can't locate a machine with Outlook XP/2003, then you can install Microsoft's trial version of Office 2003.  The import wizard does not actually load Outlook during the conversion, but does access some of its libraries therefore it must be installed.
+
* You must have Outlook 2003 installed on the machine on which you are running the Import Wizard.  <b>Outlook XP and earlier is not supported</b>.  If you can't locate a machine with Outlook 2003, then you can install Microsoft's trial version of Office 2003.  The Import Wizard does not actually load Outlook during the conversion, but does access some of its libraries therefore it must be installed.
  
==Backups==
+
==PST Preparation==
* <b>Make a backup of your PST file!</b>  If you are going to use your old Outlook 97-2002 PST to do the import, loading your old PST with Outlook 2003 may make it not work again with older Outlook versions.
+
* <b>Make a backup of your PST file!</b>  If you are going to use your old Outlook 97-2002 PST to do the import, it may not work with the older Outlook versions after loading it with Outlook 2003.
  
==Re-exporting your PST==
 
 
* You may need to re-export your old PST to a new Outlook 2003 PST.  This will clean up any inconsistencies and make the import wizard's job much easier.  This may be particularly the case if your PST came from Outlook 2000 and earlier.
 
* You may need to re-export your old PST to a new Outlook 2003 PST.  This will clean up any inconsistencies and make the import wizard's job much easier.  This may be particularly the case if your PST came from Outlook 2000 and earlier.
 +
 +
* Use <b>SCANPST.EXE</b> to repair your PST beforehand to clean up any problems with your PST before you import.  You can find <b>SCANPST.EXE</b> by searching for it in Windows (<b>(START => Search => For files or folders)</b>). For an en-US Outlook 2003 installation it should be located under c:\program files\common files\system\msmapi\1033\.
  
 
==Message size limitations==
 
==Message size limitations==
* By default, the importer (as of version 3.0.1) has a 10MB limit on <b>encoded</b> message size and is controlled by the importer itself, not the Zimbra server. <b>Do not confuse this with Outlook's reported attachment size</b>.  A file with a 8MB attachment will encode to an email over 10MB in size and will therefore not be imported.
+
* By default, the migration tools have a local 10MB limit on the <b>encoded</b> size of uploaded messages. <b>Do not confuse this encoded size with Outlook's reported attachment size</b>.  A file with an 8MB attachment will encode to an email over 10MB, and will therefore not be imported. A 12MB attachment = 16MB encoded, a 14MB attachment = 19MB encoded.
(e.g. a 12MB message = 16MB encoded, a 14MB message = 19MB encoded)
 
  
* The 10MB message limit can be adjusted by adding a registry key to the Windows machine running the Import Wizard.  The key/value is:
+
* The 10MB limit can be adjusted by adding a registry key to the Windows machine running the Import Wizard.  The key/value is:
  HKEY_CURRENT_USER\Software\ZCSMigWiz\MaxAttachSizeMB
+
  HKEY_CURRENT_USER\Software\ZCSMigWiz\MaxAttachSizeMB   (Zimbra versions < 4.5.6)
* In <b>REGEDIT</b>, Add a key called:
+
  <b>or</b>
  HKEY_CURRENT_USER\Software\ZCSMigWiz
+
  HKEY_CURRENT_USER\Software\Zimbra\MaxAttachSizeMB   (Zimbra versions >= 4.5.6)
* Add a DWORD Value called <b>MaxAttachSizeMB</b> and assign it a value in MB.
 
(e.g 15 = 15MB).  The next time the Import Wizard runs, it will use this value.
 
  
==Repairing your PST==
+
You can adjust this using <b>RegEdit</b> (Start -> Run -> regedit). Add a key called '''HKEY_CURRENT_USER\Software\ZCSMigWiz''' in Zimbra versions earlier than 4.5.6, and '''HKEY_CURRENT_USER\Software\Zimbra''' in Zimbra versions equal to or later than 4.5.6. Then add a DWORD Value called <b>MaxAttachSizeMB</b> and assign it a value (in MB obviously; e.g 15 = 15MB)The next time the Import Wizard runs, it will use this value.
* Use <b>SCANPST.EXE</b> on your PST before hand to clean up any problems with your PST before you import. You can find <b>SCANPST.EXE</b> by searching for it in Windows.   
+
 
<b>(START => Search => For files or folders)</b>
+
Note: The default [[Configuring_maxmessagesize|mta settings]] on the Zimbra server also limit attachments (and complete mime-encoded messages) to 10mb.
  
 
==RAM Requirement==
 
==RAM Requirement==
* Importing PSTs with large attachments requires a lot of physical RAM in the Zimbra server.  It is best that you have the minimum required RAM according to the Zimbra specs (1GB)However you may be able to import most or all of your messages with less.  An email with a 14MB attachment will not import to a machine with 768MB of RAM and standard heap settings.  If you really must live with less physical RAM, a temporary workaround for migration purposes is to increase the Tomcat/Java heap size on the server. The heap size defaults to 30% of all available physical RAM.  You can increase that percentage by using the following commands on the Zimbra server (logged on as the zimbra user):
+
* Generally speaking, tuning the server shouldn't be necessary specifically for migrating mailbox dataHowever, in the rare exception, see [[Performance Tuning Guidelines for Large Deployments#Memory Allocation]] for hints on tuning the mailboxd JVMAnd if the changes you make end up being migration specific, remember to revert the setting to the previous value after you are done.
$ tomcat stop
+
 
$ zmlocalconfig -e tomcat_java_heap_memory_percent=40
+
{{Article Footer|unknown|3/15/2006}}
$ tomcat start
+
 
<b>WARNING:</b> Remember to set the heap size back to <b>30</b> after you are done!
+
[[Category:Migration]]
 +
[[Category:ZCS 4.5]]

Latest revision as of 21:21, 9 February 2016

Zimbra Outlook PST Import Wizard Tips

   KB 1367        Last updated on 2016-02-9  




0.00
(0 votes)


Sometimes you may have difficulty importing your PST with the Zimbra PST Import Wizard. This may be due to the version of your PST file (i.e. Outlook 2000), the condition of your PST file, or emails with unusually large attachments. Here are a few tips that might help solve some sticky PST import problems.

Outlook Version

  • You must have Outlook 2003 installed on the machine on which you are running the Import Wizard. Outlook XP and earlier is not supported. If you can't locate a machine with Outlook 2003, then you can install Microsoft's trial version of Office 2003. The Import Wizard does not actually load Outlook during the conversion, but does access some of its libraries therefore it must be installed.

PST Preparation

  • Make a backup of your PST file! If you are going to use your old Outlook 97-2002 PST to do the import, it may not work with the older Outlook versions after loading it with Outlook 2003.
  • You may need to re-export your old PST to a new Outlook 2003 PST. This will clean up any inconsistencies and make the import wizard's job much easier. This may be particularly the case if your PST came from Outlook 2000 and earlier.
  • Use SCANPST.EXE to repair your PST beforehand to clean up any problems with your PST before you import. You can find SCANPST.EXE by searching for it in Windows ((START => Search => For files or folders)). For an en-US Outlook 2003 installation it should be located under c:\program files\common files\system\msmapi\1033\.

Message size limitations

  • By default, the migration tools have a local 10MB limit on the encoded size of uploaded messages. Do not confuse this encoded size with Outlook's reported attachment size. A file with an 8MB attachment will encode to an email over 10MB, and will therefore not be imported. A 12MB attachment = 16MB encoded, a 14MB attachment = 19MB encoded.
  • The 10MB limit can be adjusted by adding a registry key to the Windows machine running the Import Wizard. The key/value is:
HKEY_CURRENT_USER\Software\ZCSMigWiz\MaxAttachSizeMB   (Zimbra versions < 4.5.6)
 or
HKEY_CURRENT_USER\Software\Zimbra\MaxAttachSizeMB   (Zimbra versions >= 4.5.6)

You can adjust this using RegEdit (Start -> Run -> regedit). Add a key called HKEY_CURRENT_USER\Software\ZCSMigWiz in Zimbra versions earlier than 4.5.6, and HKEY_CURRENT_USER\Software\Zimbra in Zimbra versions equal to or later than 4.5.6. Then add a DWORD Value called MaxAttachSizeMB and assign it a value (in MB obviously; e.g 15 = 15MB). The next time the Import Wizard runs, it will use this value.

Note: The default mta settings on the Zimbra server also limit attachments (and complete mime-encoded messages) to 10mb.

RAM Requirement

  • Generally speaking, tuning the server shouldn't be necessary specifically for migrating mailbox data. However, in the rare exception, see Performance Tuning Guidelines for Large Deployments#Memory Allocation for hints on tuning the mailboxd JVM. And if the changes you make end up being migration specific, remember to revert the setting to the previous value after you are done.
Verified Against: unknown Date Created: 3/15/2006
Article ID: https://wiki.zimbra.com/index.php?title=Zimbra_Outlook_PST_Import_Wizard_Tips Date Modified: 2016-02-09



Try Zimbra

Try Zimbra Collaboration with a 60-day free trial.
Get it now »

Want to get involved?

You can contribute in the Community, Wiki, Code, or development of Zimlets.
Find out more. »

Looking for a Video?

Visit our YouTube channel to get the latest webinars, technology news, product overviews, and so much more.
Go to the YouTube channel »

Jump to: navigation, search