• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 628
  • Last Modified:

Exchange 2000 to 2007 migration ??

Hi,

We plan to migrate our mail server to Exchange 2007. But our domain still Windows 2000.

I am listing our configuration and the steps we plan to do. We are worry about the results, I mean the Forest and AD impact regarding our setup. May you comment or recommend ideas about this migration.

** Current configuration **
SERVER1: Windows 2000, DC, AD, DNS, WINS, DHCP, Exchange 2000
SERVER2: Windows 2000, DC (backup)
SERVER3 to 5: Windows 2000 Members
SERVER6: Windows 2003 Member, SQL 2003

** Planned configuration ** (Phase#1)
SERVER1: Windows 2000, DC, AD, DNS, WINS, DHCP
SERVER2: Windows 2000, DC (backup)
SERVER3 to 5: Windows 2000 Members
SERVER6: Windows 2003 Member, SQL 2003
SERVER7: Windows 2003 R2 Member, Exchange 2007

step1: Install SERVER7 a new server Windows 2003 as member and Exchange 2007 (with Client Access, hub, Mailbox and Unified Roles)
step2: Install Anti-Virus
step3: Test the server with some dummy mailboxes
step4: Migrate the mailboxes from Exchange 2000 to 2007 with the build-in tool in Exchange 2007 Management Console
step5: Tests some mailboxes (connect with Outlook 2000, 2003 and 2007)
step6: Redirect all smtp traffic to SERVER7
step7: Uninstall Exchange 2000 from Add/Remove Programs on Server1

** Planned configuration ** (Phase#2, within 6 months)
SERVER1: Windows 2003, DC, AD, DNS, WINS, DHCP
SERVER2: Windows 2003, DC (backup)
SERVER3 to 5: Windows 2000 Members
SERVER6: Windows 2003 Member, SQL 2003
SERVER7: Windows 2003 R2 Member, Exchange 2007

step1: DCPromo on SERVER2 to depromote this server
step2: Remove SERVER2 from the domain
step3: In place upgrade of SERVER1 from Windows 2000 to Windows 2003
step4: Format and Reinstall SERVER2 as SERVER8 with Windows 2003
step5: Insert SERVER8 as DC in this domain

Best Regards,

ANormand
0
anormand
Asked:
anormand
3 Solutions
 
billwittenCommented:
Exchange 2007 requires that the schema master FSMO role be hosted on a Windows 2003 SP1 or later DC and also requires one Windows 2003 SP1 or later GC in every AD Site that you plan to have Exchange 2007 installed in (http://technet.microsoft.com/en-us/library/aa996719.aspx).

It should also be noted that MS doesn't support Outlook 2000 against an Exchange 2007 server.

In addition to the above, you should ensure that all of the system folders, such as the free/busy PF are migrated to Exchange 2007 prior to attempting to uninstall the Exchange 2000 server.

Also note that it might be a good idea to take server 2 offline when you do the upgrade to 2003 as opposed to demoting it.  At the very least, install a Virtual Server-based DC so that you have two.  That way if you need to roll back after a failed upgrade you will be able to without an authoritative restore.
0
 
consultkhanCommented:
if you are having enough public folders you should keep atleast one exchange system manager running to manage those public folders.Since exchange 2007 has no tool to administer public folders.

thanks.
0
 
anormandAuthor Commented:
Hi,

Want do you think about this plan instead, migrate to Exchange 2003 and when the domain will be update to Windows 2003 migrating to Exchange 2007?
This way I do not touch the domain and resolve our main concern regarding limited size with Exchange 2000.

Regards,
0
Problems using Powershell and Active Directory?

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

 
SembeeCommented:
If you don't want to touch the domain then migrating to Exchange 2003 is your only option. Although even then to get the full feature set you need Windows 2003 GC/DCs.

Simon.
0
 
anormandAuthor Commented:
OK,

With all your input and documents I read. Here my revised plan.....

** Current configuration **
SERVER1: Windows 2000, DC, AD, DNS, WINS, DHCP, Exchange 2000
SERVER2: Windows 2000, DC (backup)
SERVER3 to 5: Windows 2000 Members
SERVER6: Windows 2003 Member, SQL 2003

** Planned configuration ** (Phase#1)
SERVER1: Windows 2000, DC, AD, DNS, WINS, DHCP
SERVER2: Windows 2000, DC (backup)
SERVER3 to 5: Windows 2000 Members
SERVER6: Windows 2003 Member, SQL 2003
SERVER7: Windows 2003 R2 Member, Exchange 2003

step1: Install SERVER7 a new server Windows 2003 as member and Exchange 2003
step2: Install Anti-Virus
step3: Test the server with some dummy mailboxes
step4: Migrate the mailboxes from Exchange 2000 to 2003 (over automatic roll-up, on this part I will need informations on this procedure)
step5: Tests some mailboxes (connect with Outlook 2000, 2003 and 2007)
step6: Redirect all smtp traffic to SERVER7
step7: Uninstall Exchange 2000 from Add/Remove Programs on Server1 (is it recommanded ???)

Regards,

ANormand
0
 
SembeeCommented:
There is a process for the migration of Exchange.
I have a guide here: http://www.amset.info/exchange/migration.asp
It is important that you do it in the right order, otherwise you will have problems later on.

Simon.
0
 
anormandAuthor Commented:
Sembee:

I read your guide, if I understand well your document is based on replacing/migrating an Exchange Box for another keeping the same name on a member server.

Our setup wasn't install as the best rules for Exchange.
Our Exchange2000 is installed on Windows2000 DC,AD.
We want to keep this server1 as Windows2000 DC, AD and having server7 (member) as Exchange2003. And uninstall Exchange2000 from this server1.

Is there any special concerns regarding our plan.

Regards
0
 
SembeeCommented:
My guide is written for various scenarios. You simply have to adjust the steps.
Everything is in the guide. You will install Exchange on to the new machine with a new name, move all the data across as outlined. Once the migration is complete and all of the Outlook users have connected just once you can then remove the original Exchange server.

Simon.
0
 
anormandAuthor Commented:
When you have a Windows 2000 DC with Exchange 2000 and Windows 2003 (Member) with Exchange 2003. Do we have to do forestprep and other DC Schema update for Exchange 2003?

Regards
0
 
SembeeCommented:
If you already have an Exchange 2003 server then you do not have to prep the domain or forest again. If you do not have Exchange 2003 already then prep is required.

Simon.

--
If your question has been answered, pleased remember to accept the answer and close the question.
0
 
anormandAuthor Commented:
Thanks you all for your input... a special thanks to Sembee for his input and his online documentation. Will keep you posted of the migration... regards
0

Featured Post

Technology Partners: We Want Your Opinion!

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!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now