General discussion

Locked

copy/move exchange 5.5 to w2k and on

By Seadogs ·
We are preparing to move to w2k. Currently all of our servers except the pdc/bdcs and one member server are on windows 2000. The member server is nt 4 sp6a, running exchange 5.5 sp4. The plan is to move to a new w2k domain with new dc, importing the users, and then moving all the w2k member servers. What is the best way to do exchange? Should I create an nt4 server in the current domain, install 5.5, synch them up, then move the new exchange server to the new w2k domain? Then upgrade to w2k and then to exchange 2k? Or should I put a w2k member server in the current domain, put exchange 5.5 on it, then synch the servers and then move to the new domain and then upgrade to w2k? Or should I start the new nt4 or w2k server in the new domain, connect to the old one, then upgrade to exchange 2k? Which method would be best and how would it be done? Thanks for all help!

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

copy/move exchange 5.5 to w2k and on

by Joseph Moore In reply to copy/move exchange 5.5 to ...

Please read this Technet article Upgrading from Microsoft Exchange Server 5.5 to Microsoft Exchange 2000 Server: A Six-Step Case Scenario:
http://www.microsoft.com/technet/prodtechnol/exchange/exchange2000/deploy/depovg/sixsteps.asp
(please removeany spaces)

hope this helps

Collapse -

copy/move exchange 5.5 to w2k and on

by timwalsh In reply to copy/move exchange 5.5 to ...

A lot of questions.

There may be a far simpler way to go about the problem depending on what end state you want to arrive at.

First, a couple of rules you MUST follow when migrating to a Win2K AD domain:

1. A Win2K Domain Controller (DC)CANNOT exist in an NT4 Domain.
2. To migrate a domain from NT4 to Win2K, Win2K and Active Directory (AD) MUST be installed on the NT4 PDC (not a BDC).
3. Installing AD on a Win2K Server automatically turns the server into a DC.
4. NT4 BDCs andmember servers can exist in a Win2K domain with no problems.

A couple of questions I would like you to answer so I can tailor an answer instead of giving a lot a generalities that may or may not fit your situation:

1. Migration vs. new installation - domain names: When you create an AD domain during the migration process, you actually end up with 2 domain names - an AD domain name in the form of mydomain.com and a NetBIOS domain name that automatically defaults to your old NT domain name and can't be changed. The NetBIOS domain name is what shows up in the domain list at the Log-on screen. Would this be an issue (politically, or just from a stand point of user confusion)?

2. Is your PDC or any of your BDCs capable of running Win2K (meets all hardware requirements) or are you planning on retiring these servers? This may determine the process of migration that you follow.

3. Do you have any over-riding reasons for changing from Exchange 5.5 to Exchange 2000, or is Exchange working for you as is? The only reason to move Exchange to another machine is if you are having problems with the one Exchange is currently installed on or if it won't meet the hardware requirements for Win2K. You could leave Exchange on NT4 and it would be erfectly happy in a Win2K domain.
(continued)

Collapse -

copy/move exchange 5.5 to w2k and on

by timwalsh In reply to copy/move exchange 5.5 to ...

Or, you could install Win2K over the top of NT4 on the Exchange server and everything SHOULD still function properly (but this is still Microsoft, so who knows).

If you can succinctly explain your desired endstate, (i.e. All servers running Win2K, thinking of upgrading to Exchange2K but not absolutely necessary, Win2K DCs cannot be current servers due to hardware/software problems, want to migrate current user base (or, want to start over from scratch), because of internal political issues all traces of the former domain must be eradicated, etc.), we can usally give you a very direct answer to fit your situation.

Hope this helps.

Collapse -

copy/move exchange 5.5 to w2k and on

by Seadogs In reply to copy/move exchange 5.5 to ...

I am currently reading the article mentioned in answer #1. Have just started so I don't know if that is the way yet.

Here are my answers to answer #2's questions:
Our current situation is that we have 2 domains in two locations that have complete trust. The exchange server is on my local domain. We are planning to go to one domain and then have the two locations be organizational units. Only one of our current domain controllers would be capable of running w2k ads, and we want to change the domain name so we decided to build w2k dcs from scratch and import the directory of users. We've done this on the test network with no problems except for the exchange portion. The exchange server is capable of staying the exchange server. We'd like to set one up in our other location though. So as a test I installed a winnt server with exchange 5.5 on our local network and connected to our current server so that I've got all the accounts on it. Then somehow I'd like to get the server to the new domain, running windows 2000 and then upgrade to exchange 2000. We don't have to do exchange 2000 right away, but we'd like to switch fully to w2k for the servers. We are excited about some of the changes to exchange in 2000 and will move to it as soon as we can. Would you recommend settling w2k server domain down first? Thanks and let me know if I can clarify any of our needs!

Collapse -

copy/move exchange 5.5 to w2k and on

by Seadogs In reply to copy/move exchange 5.5 to ...

so my next immediate question is do I switch the test exchange server to the new domain and get that working as nt4/exchange 5.5, then upgrade to windows 2000 or upgrade to windows 2000, then switch the server to the new network and get working as windows 2000/exchange 5.5? Thanks!

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Operating Systems Forums