Exchange Server - Migration to Exchange Server 2000/2003 (December 7, 2005)
Please note: Portions of this transcript have been edited for clarity
MarkL (Moderator):
Hello everyone- welcome to today’s Migration to Exchange Server 2000/2003 chat. We are pleased to welcome our Experts. I will have them introduce themselves now…
Introductions:
Doug - Microsoft (Expert):
My name is Doug Blanchard. I have been with the Microsoft Exchange Support team for the past 4 yrs working in the XADM and XCON teams.
Ray Fong [MSFT] (Expert):
This is Ray Fong from Exchange Connector Team in Microsoft CSS.
Susan Hubbard [MSFT] (Expert):
Hi I am Susan and I work with the Exchange Connectors Team.
Linda-Microsoft (Expert):
Hi, my name is Linda Harrell. I'm a support engineer in the Exchange Admin group.
Beth - Microsoft (Expert):
My name is Beth Belluardo, I am on the Exchange Connectors support team. I've been with Microsoft for 8 years.
Start of chat::
Susan Hubbard [MSFT] (Expert):
Q: Is there step-by-step whitepaper/kb article for 5.5 to Exchange 2003 migration?
A: yes, there is. Here is the link:
The "Exchange Server 2003 Deployment Guide" guide for Microsoft Exchange Server 2003 is available http://support.microsoft.com/default.aspx?scid=kb;EN-US;842762
Sandy - Microsoft (Expert):
Q: with exchange 2003 running on 2003 server x64 as a member server, running in a win 2000 domain?
A: Hi Tim,
You can run Exchange 2003 on a x64 bit machine, but not on the 64 bit version of windows. See:
http://blogs.technet.com/exchange/archive/2005/11/18/414796.aspx and http://www.microsoft.com/exchange/evaluation/sysreqs/2003.mspx
Doug - Microsoft (Expert):
Q: I am currently testing the migration of two mail systems (Exch5.5 and a non-MSFT POP3 server) to Exch. 2003. The 5.5 migration seems straightforward, but the POP3 users are my questions. All POP3 users already have user accounts in AD, as well as..
A: Are the POP3 account's mailboxes also on Exchange 5.5 or another mail server product? POP3 accounts are the same as any other mailbox except that we access it using a different client (port 110 client).
Doug - Microsoft (Expert):
Q: Doug - The POP3 accounts are on a different commercial mail product, not Exchange. When I migrate the POP mailboxes, how will it identify the AD users?
A: Ok, this is 2 fold. 1 getting the accounts over into AD and the other is to migrate their mailbox data to the new Exchange 2003 server. You can accomplish both using the Exchange Migration Wizard.
Linda-Microsoft (Expert):
Q: Can I inplace upgrade from Exchange 5.5 to Exchange 2003?
A: Hi, you can not run an inplace upgrade from Exchange 5.5 to 2003.
Linda-Microsoft (Expert):
Q: What is a swing method? Is there a whitepaper for that?
A: Hi, here is an article that describes the swing method:How to upgrade to Exchange Server 2003 by using the swing upgrade method http://support.microsoft.com/default.aspx?scid=kb;EN-US;821896
Sandy - Microsoft (Expert):
Q: Great. I have an enterprise edition of exchange 5.5, have purchased exchange 2003 STD edition, am in process of purchasing a new server for 2003. one hp I spec'd comes with server 2003 x64 bit version, my current domain is win 2000. Will i have issues ...
A: Did that answer your question, Tim?
Doug - Microsoft (Expert):
Q: We import/export two other exchange 2003 GAL's into our exchange system using our parent companies ADC to our legacy exchange 5.5 server. Is there a better way to do this? IIFP? Will the Inter-Org replication tool work? We want to turn off our last 5.5 ser
A: This article might provide some good information: 839049 The supportability of Exchange 2000 organizations and of Exchange 2003 organizations across multiple forests - http://support.microsoft.com/default.aspx?scid=kb;EN-US;839049
Doug - Microsoft (Expert):
Q: Doug - The user accounts already exist in AD, the other mail product uses NTLM to authenticate. Using the Exchange Migration Wizard, will it create new user accounts for each POP3 Mailbox or will it "mail-enable" the existing AD Users?
A: Per KB 278017: the enhanced Migration Wizard matches the mailboxes with Active Directory accounts or creates new accounts that exist. The Migration Wizard will extract the data and allow you to mail-enable and merge that data into the existing account.
Beth - Microsoft (Expert):
Q: To migrate "cross site" from 5.5 to 2003, is there a recommended way to move the mailboxes and public folders? We want to remove our 5.5 sites and move to routing groups. We currently have 3 sites and would like to get rid of them.
A: The only way to move a 5.5 server from one site / routing group to another is to uninstall it from one site and them reinstall it to another. Once you finish upgrading to Exchange 2003 and no longer have Exchange 5.5 servers, you can drag the servers from one Routing Group to another and delete the empty routing groups.
Doug - Microsoft (Expert):
Q: Doug - Thank you, that answers my question :-)
A: You're Welcome!
Beth - Microsoft (Expert):
Q: To migrate "cross site" from 5.5 to 2003, is there a recommended way to move the mailboxes and public folders? We want to remove our 5.5 sites and move to routing groups. We currently have 3 sites and would like to get rid of them.
A: 843104Overview of the Site Consolidation feature in Exchange Server 2003 Service Pack 1 http://support.microsoft.com/default.aspx?scid=kb;EN-US;843104
Sandy - Microsoft (Expert):
Q: I am setting up a new Exchange 2003 with separate Org on a new server. What's the best way to migrate the public folder? The original server is running Exchange 5.5 SP4. I heard something like pfmigrate, will that help? Can I get more information?
A: Hi Bob, pfmigrate doesn't work across Exchange Orgs. You can use the interorg public folder replication tool or create .pst's in one org and populate the public folders with it in the other org. Here's a blurb about the interorg public folder tool:
The Inter-Organization Replication Tool supports the migration of your public folders and free and busy information across Exchange organizations. After you have used the Exchange Server Migration Wizard to move your mailbox contents and directory information to your new organization, you can use the Inter-Organization Replication Tool to migrate your public folder and free and busy information. For more information about the Inter-Organization Replication Tool, see Exchange Server 2003 Tools and Updates (http://go.microsoft.com/fwlink/?linkid=21236).
Susan Hubbard [MSFT] (Expert):
Q: OK, I know this is a loaded question, but here goes: I'm looking at putting around 2500 users on a single server (with a large SAN backend.) How many users are you typically seeing on single Exch 2003 servers, at what point would I want to start looking..
A: you will want to take a look at this guide: Exchange Server 2003 Performance and Scalability Guide
http://www.microsoft.com/technet/prodtechnol/exchange/2003/library/perfscalguide.mspx
Susan Hubbard [MSFT] (Expert):
Q: either at multiple servers, or an active/active cluster?
A: you won't want to go with an active/active 2 node cluster. If you go with a cluster solution go with active/passive. Here is some info on clustering from our blog:
http://blogs.technet.com/exchange/search.aspx?q=cluster&p=1
Linda-Microsoft (Expert):
Q: Will the Exchange Migration Wizard break the single instance storage? Can I copy the edb files from Exchange 5.5 and drop in to the Exchange 2003 and mount the database that way consider my new server is using the same org and site name?
A: Hi, yes, single instance storage will be broken:
328871 How to use the Exchange Migration Wizard to migrate mailboxes from an http://support.microsoft.com/?id=328871
Doug - Microsoft (Expert):
Q: I have Exchange 2000 on a Wind2000 DC and I am running low on system resource. I am planning to migrate Exchange 2000 and Win2000 to Win2003 with Exchange 2003. Can create some type of backup system, to fail back too if problem occur in during migration.
A: Take a System State Backup of the server before you do anything. Then take a backup of the Exchange Information store (or stop the Exchange services and copy all *.EDB and *.STM files). It is preferred to not have Exchange on a DC; however in some scenarios that is not possible to get around. If you have the hardware, I suggest installing a new Windows 2003 Server (new hardware) to join and upgrade the AD forest first (dcpromo). Then install Exchange 2003 on that server with the latest service pack (Sp2). Then you can move mailboxes to the new server. This is will allow your current environment to remain online and not be as impacted as a straight inplace upgrade.
Sandy - Microsoft (Expert):
Q: Are there two versions of Exchange Mig. Wiz? I seem to see you are referring to an enhance version. If yes, can you refer to a link/doco?
A: Hi Xman, there's only one version of the migration wizard but it is updated periodically when service packs are released etc. It's best to run the latest version.
Sandy - Microsoft (Expert):
Q: I C what you meant by enhanced EMW, Sandy....
A: This article discusses this: 278017 Introduction to the enhanced Migration Wizard http://support.microsoft.com/?id=278017
Doug - Microsoft (Expert):
Q: number of users will my proposed system can handle (except thru extrapolation, which isn't that great in my circumstance.)
A: Take a perfmon of your current environment to get an idea of what is doing now. Then look at additional services or functions you want to add (i.e. fax, phone, mobility) and factor that in. The great way to keep uptime for a server is to keep its performance well within the recommended values. Therefore, we suggest scale servers based on performance. Ex: If the performance is so bad that you have to reboot that node once a week, then the uptime is going to fall quickly. Going to a clustered environment is the best scalability. Consider a A/A/P (3-node cluster) with a dedicated SAN for Exchange only. This will allow you to maintain better performance and better scalability. Otherwise, testing before deployment for your specific environment and needs will be required.
Beth - Microsoft (Expert):
Q: Is it recommended to collapse 5.5 sites to one 2k3 site with routing groups? Even if these sites were created because of geographic location?
A: The Routing Groups for Exchange 2003 are equivalent to Sites in Exchange 5.5. You can have 1 Exchange Admin Group with multiple Routing Groups. Since you have multiple Geographical locations, you will want to keep them in their own Routing Group.
Doug - Microsoft (Expert):
Q: In a 2000 domain, would there be issues running exchange 2003 on a 2003 member sever?
A: There are no issues with running Exchange 2003 within a Windows 2000 domain however some features will not be available Query-Based Distribution List & Interorg Recipients.
Beth - Microsoft (Expert):
Q: Thanks Beth!
A: You're Welcome!
Linda-Microsoft (Expert):
Q: Once on 2k2, how do you recommend running eseutil and isinteg? Is it that different than 5.5? We run both about once a quarter on the 5.5 side
A: Hi, the Eseutil and Isinteg utilities are pretty much the same. Here are some article that may be helpful:
XADM: Exchange 2000 Server Eseutil Command Line Switches http://support.microsoft.com/?id=317014
How to Defragment Exchange Databases
http://support.microsoft.com/?id=328804
XADM: How to Run Eseutil on a Computer Without Exchange Server
http://support.microsoft.com/?id=244525
Description of the Isinteg utility
http://support.microsoft.com/?id=182081
Susan Hubbard [MSFT] (Expert):
Q: how can I enlarge a temp map, needed by an installation program?
A: Can you give us more information? We aren’t sure what you are referring to.
Susan Hubbard [MSFT] (Expert):
Q: I am installing a TOMTOM program. It says: cannot install, the temporary map has no space enough.
A: Do you mean TomTom the GPS for mobile phones? If so, you may want to contact them. www.tomtom.com/
Doug - Microsoft (Expert):
In response to Court - The upgrade process of Exchange 2000 to Exchange Server 2003 is very simple. The move mailbox process is similiar to that of Exchange 2000. If you are upgrading AD, consider 314649 Windows Server 2003 adprep /forestprep Command Causes Mangled Attributes in Windows 2000 Forests That Contain Exchange 2000 Servers - http://support.microsoft.com/default.aspx?scid=kb;EN-US;314649
Be sure to review:
842762 The "Exchange Server 2003 Deployment Guide" guide for Microsoft Exchange Server 2003 is available:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;842762
Exchange Server 2003 Deployment Tools overview:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;812593
Linda-Microsoft (Expert):
Q: Linda, the links you sent do not work (page can not be displayed)
A: Which one?
Susan Hubbard [MSFT] (Expert):
Q: Is there a rough metric for how long (per GB) the "Move Mailbox" wizard takes?
A: Sorry, we don’t, there are too many variables involved to be able to give an estimate.
Sandy - Microsoft (Expert):
Q: Will there ever be a utility to visio out nested distribution groups? Currently the only way I know how to do this is by hand. Very time consuming!!
A: There might be if there's enough demand, you might want to send an email requesting this to mswish@microsoft.com
Sandy - Microsoft (Expert):
Q: Thanks Sandy! being able to view nested distribution lists is VERY handy!! I'll make my wish request!!
A: you're welcome, that would be a great feature.
Linda-Microsoft (Expert):
Q: Would you recommend stripping down all the mailboxes to a small size before migrating to 2003?
A: Hi, if you are concerned about the time is takes to move the data over, it all depends on how large the data is being moved. You should be okay if this is over the local LAN.
Doug - Microsoft (Expert):
Q: Also what are your thoughts on auto archiving? Should we be looking for a file stripper like vault or use archiving and suffer the pst files?
A: Auto archiving at the client is not recommended. This will require more resources on a per client basis and if a message is deleted, how can it be recovered? However, if the data is left on Exchange, you can keep it all on 1 location, backup/restore at will, and centrally control the data flow as needed. Now, if you need archiving for other uses (like gov't regulations or save a copy of all messages on the system) there are plenty of options to review: http://www.microsoft.com/exchange/partners/default.mspx
Sandy - Microsoft (Expert):
Q: I use policytest to confirm both GC/DCs on both root/child domain return the correct right
A: Hi Joe, I would verify we have a domain recipient update service installed for the root domain and force active directory replication between the domains.
Sandy - Microsoft (Expert):
Q: Should we all be on Exchange 2003 SP2 or SP1? Didn't SP2 just come out in October 2005?
A: we'd recommend applying the latest service pack.
Sandy - Microsoft (Expert):
Q: Aside from bug fixes in SP2, were there any new features added that are worth mentioning?
A: There are quite a few new features. See
http://www.microsoft.com/exchange/evaluation/sp2/overview.mspx for details.
Susan Hubbard [MSFT] (Expert):
Q: And on that question has the mobile mail been implemented in sp2?
A: take a look at this:
SP2 mobile: http://www.microsoft.com/exchange/evaluation/sp2/overview.mspx#mobilesp2 Overview http://www.microsoft.com/exchange/evaluation/sp2/overview.mspx
Susan Hubbard [MSFT] (Expert):
Q: IN outlook 2k3 has the 2Gb pst limit been fixed?
A: we still have the 2gb limit.
MarkL (Moderator):
Well that wraps things up for our Migration to Exchange Server 2000/2003 chat this afternoon. I want to thank all of our guests for joining us, and of course, thanks to our experts for being here to answer questions. Have a great night everyone!