Upgrade exchange 2000 to exchange 2007 (Full Version)

All Forums >> [Microsoft Exchange 2007] >> Migration



Message

skrs22 -> Upgrade exchange 2000 to exchange 2007 (22.Mar.2007 7:56:03 PM)

Hi guys,
i have a small network that has 14 servers with 2 domain controller replicating each other.

first one has Windows 2000 server  with DNS, WINS, DHCP and Exchange 2000.

second one is Windows 2000 Active Directory with DNS and WINS replicated to the first one.

Now i want to upgrade my Exchange to 2007 with third server that has windows 2003 R2. Kindly please guide me to do this transition.

thank you
Chris



vhato -> RE: Upgrade exchange 2000 to exchange 2007 (24.Mar.2007 2:26:24 PM)

Well, here is the bad news.

Your Windows 2000 DC's must become 2003 DC's somehow.  You can either buy upgrade copies of Windows Server 2003 and upgrade the 2000 DC's or you must add a 2003 DC to the 2000 Domain...but you are not out of the woods.  To install Exchange 2007, NO Server 2000 DC's can exist.....at all.  They can be members of the domain, but under no circumstances can they be DC's.

If you plan to add a 2003 DC to you 2000 Domain, first upgrade all 2000 DC's to Service Pack 4.  One you have done that, place the Windows Server 2003 CD inthe Windows Server 2000 DC's drive and goto the command prompt.  Goto the drive letter of the cd drive and enter the i386 folder.  Type in adprep /forestprep.  This will upgrade the Active Directory on your 2000 DC's to include features for 2003.  If all goes well, this can be done in about 20 minutes.  You will probably run into problems requirng ADSIEdit to be run, just let us know the errors and we will help fix them.  Don't be afraid, this won't screw up anything even if it does fail.

Once this task has been completed goto the Windows Server 2003 server, you run dcpromo from the command prompt or just add the Windows Server 2003 to the domain using the startup wizard that pops up when you boot 2003.

Now the FSMO roles and Global Catalog must be moved from the 2000 DC's to the 2003 DC's.  Again, don't be afraid, this is real painless.  Our goal is to completely remove the 2000 DC's as DC's and make them merely members.

Reply here and I will post how to transfer the FSMO Roles and Global Catalog. After that is done, we can being installing Exchange 2007 and and migrating mailboxes.

I just completed this exact project.  I have 35 server, 230 users, and several Blackberry users.  I was terrified to touch my 2000 DC's much less decomission my Exchange 2000 server.  Remember, Microsoft offers FREE telephone support to you if you tell them "you network is down".  Sure it comes from India, but these guys are good at this.  I used the free support 7 times in 2 weeks on separate issues.  Just didn't want you to feel alone.



alanchan -> RE: Upgrade exchange 2000 to exchange 2007 (29.Mar.2007 2:19:12 PM)

Hey Vhato,

My name is Alan, I am in the same shoes as Skrs22.

I have a small server farm here with only one 2003 DC and a 2000 DC in the same domain.
the existing Exchange 2000 server is not a DC.
I am about to buy new hardware for Exchange 2007

like you said, I have to remove the 2000DC first,
I did all the adprep /forestprep, ADSIEdit etc...

but unsure how to move the FSMO roles and Global Catalog to the 2003DC
Can you help???

thank you



BeTaCam -> RE: Upgrade exchange 2000 to exchange 2007 (2.Apr.2007 8:21:51 AM)

NTDSUTIL
-connections
.
.
.Roles
- transfer FSMO Roles source to target

let me know if you need more assistance in this exercise



edx200 -> RE: Upgrade exchange 2000 to exchange 2007 (6.Apr.2007 4:08:35 PM)

quote:

ORIGINAL: vhato
To install Exchange 2007, NO Server 2000 DC's can exist.....at all.  They can be members of the domain, but under no circumstances can they be DC's.

You're correct in telling him that he needs a Windows 2003 DC that, in addition to your provided info, must also control the Schema Master FSMO role. However, you are completely incorrect when you stated the quoted. There is no reason at all that you cannot install Exchange 2007 in an AD forest which has Win2K DCs. The only major clincher is that you, as I explained above, have to have a Win2K3 DC in the forest acting as both a GC and the Schema Master FSMO.

To the OP, what I did to get around the issues is (and I KNOW this is something everyone here will wince at) make the new Exchange 2K7 server a DC as well as Schema Master & GC. You want to make it a GC anyway, and it really doesn't HURT to have E2K7 on a DC, it just isn't Best Practice. I worked with MS's Exchange Support Team in planning this whole thing out perfectly and, aside from them disliking the Exchange Server/DC combo, everything went smooth as butter.

What I would suggest though is that you look into the new SBS when it comes out and forego the upgrade to a full Exchange 2007 server. You just don't need that sort of horsepower in your organization and it costs a hefty chunk of money for the licenses and CALs.



t0ta11ed -> RE: Upgrade exchange 2000 to exchange 2007 (12.Apr.2007 4:32:43 PM)

This is why I didn't even bother carrying over anything Win 2000 related when migrating to Win 2k3 and Exchange 2k7. Too much work LOL



Page: [1]