We value your feedback.
Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!
Solved
Transition Single Exchange 2003 server to Exchange 2010
Posted on 2012-12-30
Hello, we currently have an exchange 2003 server that needs to be replaced. It is a DC, although we have other DCs in the domain. We also have an existing exchange 2010 server that someone tried to transition to in the past and gave up. First, how do I transition to a single server 2010 setup? What do I need to do at the firewall level? What about Active Directory? And what do I need to do at our spam filtering solution? (MXLogic) Also, the 2003 server provides DNS and DHCP, how can I transition those roles away from the 2003 server? Finally, how do I remove the remnants of the old 2010 and 2003 servers? Thanks!
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
3
2
2- +1
8 Comments
Here is a great step by step outline of the migration path you mentioned above. The link to the full document is below the outline.
The sequence for a migration from Exchange 2003 to Exchange 2010 is as follows:
1. Bring the Exchange organization to Exchange Native Mode.
2. Upgrade all Exchange 2003 Servers to Exchange Server 2003 Service Pack 2.
3. Bring the AD forest and domains to Windows Server 2003 Functional (or higher) levels.
4. Upgrade at least one Global Catalog domain controller in each AD Site that will house
Exchange Server to Windows Server 2003 SP2 or greater.
5. Prepare a Windows Server 2008 (RTM or R2) x64 edition server for the first Exchange 2010 server.
6. Install the AD LDIFDE tools on the new Exchange 2010 server (to upgrade the schema).
7. Install any necessary prerequisites (WWW for CAS server role).
8. Run setup on the Exchange 2010 server, upgrade the schema, and prepare the forest and domains. (Setup runs all in one step or separate at the command line.)
9. Install CAS server role servers and configure per 2010 design. Validate functionality.
10. Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers.
11. Install Hub Transport role and configure per 2010 design.
12. Transfer inbound and outbound mail traffic to the HT servers.
13. Install Mailbox servers and configure Databases (DAG if needed).
14. Create public folder replicas on Exchange 2010 servers using pfmigrate.wsf script,
AddReplicatoPFRecursive.ps
15. Move mailboxes to Exchange Server 2010 using Move Mailbox Wizard or Powershell.
16. Rehome the Offline Address Book (OAB) generation server to Exchange Server 2010.
17. Rehome Public Folder Hierarchy on new Exchange Server 2010 Admin Group.
18. Transfer all Public Folder Replicas to Exchange Server 2010 Public folder store(s).
19. Delete Public and Private Information Stores from Exchange 2003 server(s).
20. Delete Routing Group Connectors to Exchange Server 2003.
21. Delete Recipient Update Service agreements using ADSIEdit.
22. Uninstall all Exchange 2003 servers.
http://www.networkworld.com/community/node/47632
Hope this helps!
The sequence for a migration from Exchange 2003 to Exchange 2010 is as follows:
1. Bring the Exchange organization to Exchange Native Mode.
2. Upgrade all Exchange 2003 Servers to Exchange Server 2003 Service Pack 2.
3. Bring the AD forest and domains to Windows Server 2003 Functional (or higher) levels.
4. Upgrade at least one Global Catalog domain controller in each AD Site that will house
Exchange Server to Windows Server 2003 SP2 or greater.
5. Prepare a Windows Server 2008 (RTM or R2) x64 edition server for the first Exchange 2010 server.
6. Install the AD LDIFDE tools on the new Exchange 2010 server (to upgrade the schema).
7. Install any necessary prerequisites (WWW for CAS server role).
8. Run setup on the Exchange 2010 server, upgrade the schema, and prepare the forest and domains. (Setup runs all in one step or separate at the command line.)
9. Install CAS server role servers and configure per 2010 design. Validate functionality.
10. Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers.
11. Install Hub Transport role and configure per 2010 design.
12. Transfer inbound and outbound mail traffic to the HT servers.
13. Install Mailbox servers and configure Databases (DAG if needed).
14. Create public folder replicas on Exchange 2010 servers using pfmigrate.wsf script,
AddReplicatoPFRecursive.ps
15. Move mailboxes to Exchange Server 2010 using Move Mailbox Wizard or Powershell.
16. Rehome the Offline Address Book (OAB) generation server to Exchange Server 2010.
17. Rehome Public Folder Hierarchy on new Exchange Server 2010 Admin Group.
18. Transfer all Public Folder Replicas to Exchange Server 2010 Public folder store(s).
19. Delete Public and Private Information Stores from Exchange 2003 server(s).
20. Delete Routing Group Connectors to Exchange Server 2003.
21. Delete Recipient Update Service agreements using ADSIEdit.
22. Uninstall all Exchange 2003 servers.
http://www.networkworld.com/community/node/47632
Hope this helps!
Active 1 day ago
Just follow the Microsoft Exchange Deployment Tool
http://technet.microsoft.com/en-us/exdeploy2010/default.aspx
http://technet.microsoft.com/en-us/exdeploy2010/default.aspx
Hello indigo6,
please follow http://social.technet.microsoft.com/Forums/en/exchange2010/thread/d24d733d-6006-4d07-aa6b-f4ac380fb874, http://allcomputers.us/windows_server/understanding-how-to-transition-to-exchange-server-2010.aspx and http://araihan.wordpress.com/2009/10/29/transitioning-from-exchange-server-2003-to-exchange-server-2010-step-by-step/ to sort out single transition.
Thanks
Kernel Recovery Tools
please follow http://social.technet.microsoft.com/Forums/en/exchange2010/thread/d24d733d-6006-4d07-aa6b-f4ac380fb874, http://allcomputers.us/windows_server/understanding-how-to-transition-to-exchange-server-2010.aspx and http://araihan.wordpress.com/2009/10/29/transitioning-from-exchange-server-2003-to-exchange-server-2010-step-by-step/ to sort out single transition.
Thanks
Kernel Recovery Tools
Thank you. So, what about removing the failed exchange 2010 server? Also, transitioning DNS and DHCP? Thanks again!
Active 1 day ago
You can use adsiedit to remove the old Exchange server. However be careful while using this tool, as changes are irreversible.
OK, I think my exchange question is answered. It seems easier than I thought... I guess we will see. What about mxlogic and then transitioning DNS and DHCP? This server is also a DC, how can I safely decommission it?
Featured Post
Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Wouldn't it be nice if objects in Active Directory automatically moved into the correct Organizational Units?
This is what AutoAD aims to do and as a plus, it automatically creates Sites, Subnets, and Organizational Units.
The main intent of this article is to make you aware of ‘Exchange fail to mount’ error, its effects, causes, and solution.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment.
The video tutorial explains the basics of the Exchange server Database Availability grou…
There are cases when e.g. an IT administrator wants to have full access and view into selected mailboxes on Exchange server, directly from his own email account in Outlook or Outlook Web Access. This proves useful when for example administrator want…
Suggested Courses
Course of the Month13 days, 17 hours left to enroll
656 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.