Tips for your Exchange Server 2003 migration and also Traps to avoid
Here are my 20+ tips based on my experience with Exchange 2003 migration.
Planning Tips – Before you install Exchange Server 2003
- Beg, steal or borrow machines for a Test Exchange 2003 network.
- Dedicate the Windows 2003 Server to Exchange 2003. Do not share the Exchange server with SQL or Domain Controller duties.
- Favour the Enterprise version of Exchange 2003 (avoid the Standard Edition if possible).
- Apply SP2 for Exchange 2003 and get the latest ADC connector for your migration.
- Try CSVDE or VBScript for bulk import of user accounts from a spreadsheet.
- Understand dependencies. Exchange 2003 looks to Windows 2003 for so many services, for example, SMTP needs IIS.
- Plead, threaten, exhort users to reduce Mailboxes size before migration.
- Allow the ExDeploy wizard to guide you through the setup.
- You cannot move server between Administrative Groups. So plan your Exchange 2003 Administration Groups before you install your server.
- Run setup /forestprep, then create a new name for the ‘First Administrative Group’. My point is that you cannot rename this Admin group later.
Here is a free tool to monitor your Exchange Server. Download and install the utility, then inspect your mail queues, monitor the Exchange server’s memory, confirm there is enough disk space and check the CPU utilization.
This is the real deal – there is no catch. SolarWinds provides this fully-functioning freebie, as part of their commitment to supporting the network management community.
Before you deploy Exchange Server 2003, check these Features
- Check out Exchange 2003s Junk Mail filter.
- Explore the new features of OWA in Exchange 2003.
- Investigate the OMA (Mobile access).
- To enable the Advanced Search in Outlook, set up Index Server to Catalog the Private store.
- Evaluate the new Active / Passive clustering technology.
- Always Read the Release Notes.
Once you have Exchange 2003 up and running- More tips
- Inspect the System Policies within Exchange 2003 e.g. to set Mailbox limits
- Set a date to switch Exchange 2003 from Mixed mode to Native mode
- Put your database files (Priv*.edb .stm) on a separate disk from the transaction logs
- Check out the GLOBAL SETTINGS with Exchange System Manager
- Decide on whether or not to archive all email to one very secure Active Directory account.
- Run Performance Monitor to create a baseline before the users start logging on.
- Apply SP1 and take advantage of cross-site mailbox migration.
- OWA needs Basic Authentication in IIS.
- If you need extra Virtual Servers, create them with the Exchange System Manager (not IIS).
- Decide on how to display names in the Address, surname firstname, or firstname surname. Do this BEFORE you create any users.
Import users from a spreadsheet, complete with their mailbox. Just provide a list of the users with the fields in the top row, and save as .csv file. Then launch this FREE utility, match your Exchange fields with AD’s attributes, click and import the users. Optionally, you can provide the name of the OU where the new mailboxes will be born.
- Bulk-import new users and mailboxes into Active Directory.
- Seek and zap unwanted user accounts.
- Find inactive computers.
Traps to avoid in Exchange 2003
- Always favour Exchange 2003 Enterprise Server (not the basic version with the 16 GB Store limit). The Enterprise version also supports multiple storage groups with up to 20 stores.
- Exchange 2003 will not function on a server with SharePoint Portal Server installed.
- Do Not Use Exchange 2000 System Manager to Manage Exchange 2003.
- If you install Exchange System Manager on the same machine as Outlook, then it may not display properly. (I have not noticed any problems myself, but Microsoft warn you not to do it.)
- If you have a multi domain forest, Run setup /domainprep in every domain. Guy says: just do it! Microsoft say do it because if you don’t, then you get 0800xxxx errors.
- Setup the Windows Server 2003 part of clustering before you start adding Exchange 2003 nodes. E.g. create virtual server, virtual IP and shared disk.
SolarWinds’ Network Performance Monitor will help you discover what’s happening on your network. This utility will also guide you through troubleshooting; the dashboard will indicate whether the root cause is a broken link, faulty equipment or resource overload.
What I like best is the way NPM suggests solutions to network problems. Its also has the ability to monitor the health of individual VMware virtual machines. If you are interested in troubleshooting, and creating network maps, then I recommend that you try NPM now.
Summary of Exchange tips for your migration
Think of planning like a general. Migrating to Exchange Server 2003 has all the complexities of a military campaign to test before you embark on the real migration journey. Take the time to read through my traps and thus avoid the minefields of a Microsoft Exchange migration. If you have an Exchange tip for migration, then I would love to add it to my list.
If you like this page then please share it with your friends
- ADMT Wizard
- ADC Agreements
- Install Exchange 2003
- Installing Exchange Server 2007
- Microsoft Exchange 2003 Clustering
- Migration Strategies
- Migration Benefits
- Microsoft Exchange Compatibility