|
I would definitely consider getting your hands on the Exchange Server Best Practices Analyzer (ExBPA) tool version 2.7 or later, which includes an Exchange 2007 readiness check for your organization. During the planning phase, I would identify if you utilize features in Exchange 2000 that are no longer supported in Exchange 2007. Those features include:
Microsoft Mobile Information Server
Exchange 2000 Instant Messaging Service
Exchange 2000 Chat Service
Exchange 2000 Conferencing Server
Key Management Service
cc:Mail Connector
Microsoft Mail (MS Mail) Connector
In Exchange 2003, the following features will require you to maintain an instance of Exchange 2003 in the organization:
GroupWise Connector
X.400 Connector
Connector for Lotus Notes
The process of moving or transitioning from Exchange 2000 to 2007 does not support an in-place upgrade. If you consider that Exchange 2000 was not 64-bit, the notion of an in-place upgrade not being an option becomes more obvious. That being said, there is a useful Microsoft TechNet article, Best practices for transitioning an Exchange organization, that goes through some best practices for transitioning to Exchange 2007. You will most likely use the Move-Mailbox cmdlet or the Move Mailbox Wizard.
(Click on image for enlarged view.)
Do you have comments on this Ask the Expert Q&A? Let us know.
Related information from SearchExchange.com:
Expert Advice: Migrate Exchange 2000 to 2003 in the correct sequence
Expert Advice: Performing an Exchange 2000 to 2003 in-place upgrade
Tip: Drawbacks of running a mixed mode Exchange environment
Tip: Mixed mode vs. native mode – what's the difference?
Reference Center: Exchange deployment and migration advice
Reference Center: Exchange Server 2007 tips and resources
|
