Solved

Transition Single Exchange 2003 server to Exchange 2010

Posted on 2012-12-30
8
485 Views
Last Modified: 2013-01-12
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!
0
Comment
Question by:indigo6
[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
 
LVL 25

Assisted Solution

by:Tony Giangreco
Tony Giangreco earned 167 total points
ID: 38731862
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.ps1,or Exchange 2010 Public Folder tool.

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!
0
 
LVL 43

Assisted Solution

by:Amit
Amit earned 166 total points
ID: 38732380
Just follow the Microsoft Exchange Deployment Tool

http://technet.microsoft.com/en-us/exdeploy2010/default.aspx
0
 
LVL 5

Accepted Solution

by:
Kernel_Recovery_Tools earned 167 total points
ID: 38736262
0
Are your AD admin tools letting you down?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

 

Author Comment

by:indigo6
ID: 38738192
Thank you. So, what about removing the failed exchange 2010 server? Also, transitioning DNS and DHCP? Thanks again!
0
 
LVL 43

Expert Comment

by:Amit
ID: 38739805
You can use adsiedit to remove the old Exchange server. However be careful while using this tool, as changes are irreversible.
0
 

Author Comment

by:indigo6
ID: 38748924
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?
0
 
LVL 25

Expert Comment

by:Tony Giangreco
ID: 38766706
Have you received the info you were looking for? Ready to close and award points?
0
 

Author Closing Comment

by:indigo6
ID: 38770689
I guess I will close this question and start a separate one for the other topics. Thanks!
0

Featured Post

Free NetCrunch network monitor licenses!

Only on Experts-Exchange: Sign-up for a free-trial and we'll send you your permanent license!

Here is what you get: 30 Nodes | Unlimited Sensors | No Time Restrictions | Absolutely FREE!

Act now. This offer ends July 14, 2017.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Here's a look at newsworthy articles and community happenings during the last month.
This article provides a convenient collection of links to Microsoft provided Security Patches for operating systems that have reached their End of Life support cycle. Included operating systems covered by this article are Windows XP,  Windows Server…
This video shows how to use Hyena, from SystemTools Software, to update 100 user accounts from an external text file. View in 1080p for best video quality.
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…

688 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question