Trapped Outlook Clients - post Exchange Migration

When Migrating Exchange, normally the Outlook client software needs to re-target itself to the new Exchange server. Outlook will check in with the old Exchange server and will learn that it needs to connect to a different Exchange. If the old Exchange server is turned off, the service are stopped, or it has been uninstalled, you will be left with a Outlook client that will not open.

Normally just turning on the old Exchange server, then starting the Outlook client will be sufficient to remedy this, however if the old Exchange server has been uninstalled then the Outlook client will be trapped. This is especially unnerving on a terminal server, where mlcfg.cpl will probably be restricted from executing.

A work around that I have found is to start outlook.exe with the command line switch, /profiles. This will launch a dialog window where you can create a new mail profile, configure it for the new Exchange server and set it to be the default profile.

Complete list of Entourage 2004 port requirements

Ports in Bold indicate SSL setup on the exchange server and on LDAP. Otherwise use ports un-bolded.

1.       80/443 to Exchange (mailbox synch, public folder access, free/busy info, shared folder access, quota management)

2.       53/389/636/3268/3269 to Global Catalog domain controller (Setup assistant, GAL, Password expiration notice)

3.       135 to Exchange (delegate management)

Manually uninstalling Intelligent Message Filter v1 prior to exchange 2003 service pack 2

When installing Exchange Server 2003 Service Pack 2 to an existing Service Pack 1 system, the service pack can fail if the update for the Intelligent Message Filter v1 is already installed.
To manually remove Intelligent Message Filter v1

1.     Stop all Exchange services (Information Store, System Attendant, SMTP, and Exchange-aware antivirus services).

2.     Rename the MSCFV1 folder in X:\Program Files\Exchsrvr\bin, where X is the drive letter where Exchange Server is installed.

3.     Rename the ContentFilter.dll file in X:\Program Files\Exchsrvr\bin\, where X is the drive letter where Exchange Server is installed.

4.     Open regedit and export the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange key.

5.     Delete the ContentFilterVersion sub key from the registry.

6.     Restart the server. You should now be able to install Exchange Server 2003 SP2 without errors.

Cached Exchange Mode with Extremely Large Mailboxes

Applies to: Cached Exchange mode with Mailboxes 18gb in size and over.

Outlook 2007 client hard codes max OST and PST size to 18gb warn and 20gb max for Unicode PSTs, and 1.8gb warn and 2.0gb max for ANSI PSTs. Once in warning mode, mail cannot be sent or received.

Solution:
On client machine where Outlook 2007 is installed.
Launch Regedit.
Navigate to the following key: HKCU\Software\Microsoft\Office\12.0\Outlook\PST (even for OSTs)
Create the key if necessary.
Create the following 4 DWords and populate them with the accompanying values:
• MaxFileSize=0x7bb04400
• WarnFileSize=0x74404400
• MaxLargeFileSize=0x0000c800
• WarnLargeFileSize=0x0000be00
Navigate to the following key: HKCU\Software\Policies\Microsoft\Office\12.0\Outlook\PST
Create the key if necessary.
Create the following 4 DWords and populate them with the accompanying values:
• MaxFileSize=0x7bb04400
• WarnFileSize=0x74404400
• MaxLargeFileSize=0x0000c800
• WarnLargeFileSize=0x0000be00

Restart outlook. Verify that mail can be sent and received.