Solved

Upgrade to Windows/Exchange 2003

Posted on 2006-11-29
8
218 Views
Last Modified: 2010-03-06
Hi all,
Current setup is this

A single Windows 2000 domain controller running in mixed mode. (i have just removed the last windows NT 4/exchange 5.5 server from the domain
and turned it off, all seems to be running ok) Not sure if i now need to switch to native mode for AD and the installed and running exchange 2000 (SP3)
server.

I have a new server with windows 2003 installed on the same network and i want to install exchange 2003 here. I recently read that
exchange 2003 will run happier on a member server? I do have 2 servers now and could leave the 2000 server to handle domain stuff.

My plan was to join the windows 2000 domain with the new windows 2003 server as a member. Install exchange 2003 on here and decomission
the exchange 2000 server. When i'm installing exchange 2003 do i choose new installation or join/upgrade?

My issues is moving the mailboxes/public folders from the old exchange 2000 server to the new exchange 2003 server. In the past i have
had to install exchange into the same site as the other in order to do this....or the ADC.  Is it possible for me to use the move mailbox method
or will it be psts....
Will i need the ACD installed for the replication of the public folders to the new exchange 2003 box?

I can see a lot of stuff about 5.5  to 2000/2003, but have done that bit....

Any advice would be appreciated

David
0
Comment
Question by:dlloyd37
  • 4
  • 4
8 Comments
 
LVL 104

Expert Comment

by:Sembee
ID: 18038551
What you want to do is a swing migration. Very easy and frequently discussed.
My article on the process is here: http://www.amset.info/exchange/migration.asp

Take your time, as public folder replication off Exchange 2000 is very slow.
Did you actually remove Exchange 5.5, or just shutdown the server?

Simon.
0
 

Author Comment

by:dlloyd37
ID: 18039332
I have followed the procedure from microsoft on how to remove the last exchange 5.5 server
from the site and its no longer there. What i mean is....its been succesfully removed from ESM
and have also removed the ADC. I have couple of errors in the event logs where some messages
can't be delivered to the old public store but other than that all seems ok. Maybe i need to run ds
consistancy checker to clear these up.

I have now turned off theold NT4/exch5.5 box and all has been running for a couple of days without an issue. I assume now
i can proceed as if i have just a windows 2000/exchange 2000 organisation.

One thought though?
Do i switch my domain controller windows 2000 (only 1) to native mode?
Do i switch my exchange 2000 (installed on same box) to native mode

before i proceed as my next step is to run the windows 2003 ADprep/forestprep against my windows 2000 DC
after following the artical about mangled attributes. I guess as i have exchange 2000 already installed i need to
run the fix script before running the prep programs from the windows 2003?

Once i have done that i will join the windows 2003 server to the windows 2000 domain as a member server and install
exchange 2003. I hope then i can move my public folders/mailboxes over to the new exchange. I then want to remove
my old exchange 2000 but retain the old server as the main DC only.

David
0
 
LVL 104

Expert Comment

by:Sembee
ID: 18040184
There is no reason to switch either the domain or Exchange org in to Native mode. It doesn't affect the upgrade in any way.

I don't think that you need to worry about mangled attributes as you going from Exchange 2000 to Exchange 2003. That doesn't cause problems. The mangled attributes comes when deploying Exchange 2000 in a Windows 2003 domain.

You don't need to Windows 2003 prep to introduce a Windows 2003 machine as a member server.

Therefore I would simply forest prep and domain prep for Exchange 2003.
If you are planning to deploy a Windows 2003 DC at some point, then I would look at doing all four preps (Exchange 2003 and Windows 2003) then moving on to the application deployment.

Once Exchange 2003 is installed, service pack it. Then configure replication of the public and system folders. Do not attempt to move any mailboxes until that is complete. It is slow, so you will need to wait at least a week before moving on to the mailbox move.

Simon.
0
Is Your AD Toolbox Looking More Like a Toybox?

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:dlloyd37
ID: 18041234
OK..sounds great if i understand you correctly,

So your saying:
Install Windows 2003 server on the new box
Join exisiting 2000 domain
run ADprep/forest prep against this installation then
install exchange 2003....and join the existing org?

I don't have to run anything else against my existing domain controller?

Thnx for your help on this

David
0
 
LVL 104

Expert Comment

by:Sembee
ID: 18041343
You can run prep on any machine - it doesn't have to be a Windows 2003 machine. Ditto for Exchange. I usually run everything on a domain controller as that is where the content is going to end up anyway.

When you come to install Exchange, you don't get an Org choice. The Exchange installation detects the existing server and just joins it automatically.

When running the prep, give it enough time to replicate before moving on to the next one. I usually leave 30 minutes between each one.

Simon.
0
 

Author Comment

by:dlloyd37
ID: 18042140
I'm a bit concerned in running the Adprep/forestprep command against
my windows 2000 DC, purely because i read this

Windows Server 2003 adprep/forestprep command causes mangled attributes in
windows 2000 forests that contain Exchange 2000 servers

Q314649

Is that because i won't be running this (Windows 2003 server Adprep)but the
one of the exchage 2003 cd?

David
0
 
LVL 104

Accepted Solution

by:
Sembee earned 250 total points
ID: 18043768
The easy way round that is to Exchange 2003 prep first, then Windows 2003 prep.

The actual order you do either in doesn't matter - it simply means that until you have run the relevant part you cannot introduce a Windows 2003 DC or an Exchange 2003 server.

Simon.
0
 

Author Comment

by:dlloyd37
ID: 18046510
Thank you and i will let u know how i get on....
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

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

This process describes the steps required to Import and Export data from and to .pst files using Exchange 2010. We can use these steps to export data from a user to a .pst file, import data back to the same or a different user, or even import data t…
Read this checklist to learn more about the 15 things you should never include in an email signature.
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…
This video discusses moving either the default database or any database to a new volume.

777 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