Solved

Upgrading from Exchange Enterprise 2000 to Exchange enterprise 2007, Windows 2000 domain

Posted on 2011-02-21
4
228 Views
Last Modified: 2012-05-11
I know this has been asked and answered here many times, but my research has me greatly concerned that I could screw this up big time.   Here is my scenario.

I have 2 Exchange 2000 Enterprise servers running on a Windows 2000 domain with 3 ADC's.  I also have several Windows 2003 member servers, any of which could be promoted to an Windows 2003 ADC.  I need a proven set up steps to get me to (as I understand it)
1. A Windows 2003 domain -via Domain prep and Forest prep
2. Then I think I need to do some sort of fix to prepare for Exchange 2007 (another domain and forest prep?)
3. Then I can promo an existing windows 2003 member server to an ADC and transfer all FMSO, PDC, etc.
4. Finally I can install Exchange Enterprise 2007 and start migrating users.

Of course the docs I read warn of dire consequences... Killing all the AD in the domain, etc.
I have imaged the Windows 2000 AD that I plan to install the domain and forest preps and I intend to remove it from the network during the domain and forest prep (good or bad idea?)

One of the Windows 2000 ADC is on another island, so screwing this up would be major.

Anyone with a good cook-book on this?

Marcus
0
Comment
Question by:msmaby
[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
4 Comments
 
LVL 21

Expert Comment

by:Hendrik Wiese
ID: 34942229
Good Guides to look at:

1. Common Mistakes When Upgrading Exchange 2000/2003 To a Exchange 2007

Very Good Guide or Cook-Book (if you like)
2. Upgrade to Microsoft Exchange 2007 from Exchange 2003 or 2000

Let me know if it helps?
0
 
LVL 2

Author Comment

by:msmaby
ID: 34945254
Thanks for the quick response.

The 1st document is the one I found that raised my hackles. As I see it, my first task is to move to a Windows 2003 based domain, but without killing my existing Exchange servers.  Here is where the major nerves come.  I do not have the luxury of having a lab to experiment in. I need to do this in a production environment.  Any cook books for this first step?

Thanks in Advance
Marcus
0
 
LVL 21

Expert Comment

by:Hendrik Wiese
ID: 35007383
Hi Marcus, Moving your domain to a 2003 function level would not break anything. And using the guides I provided above, if you follow everything step by step and ensure that everything is in place nothing will go wrong.

So my suggestion is have some faith and go for it.
0
 
LVL 21

Accepted Solution

by:
Hendrik Wiese earned 500 total points
ID: 35007400
The following guide will explain in detail how you should go about doing it.

Transitioning from Exchange 2000/2003 to Exchange Server 2007 (Part 1)
http://www.msexchange.org/tutorials/Transitioning-Exchange-2000-2003-Exchange-Server-2007-Part1.html
0

Featured Post

Best Practices: Disaster Recovery Testing

Besides backup, any IT division should have a disaster recovery plan. You will find a few tips below relating to the development of such a plan and to what issues one should pay special attention in the course of backup planning.

Question has a verified solution.

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

This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
This article explains the steps required to use the default Photos screensaver to display branding/corporate images
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

733 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