replace 2000 DC with new 2003 DC ?

[scott]

Hi,

I have a 2000 AD domain with 1 DC and 3 member servers:

-DC 2000 server (hosts AD, dns, file services etc)
-member server 1 2000 server (Terminal services and pptp/rras)
-member server 2 2000 server (exchange 2000)
-member server 3 2003 server (SQL 2000)

Im planning to introduce a new rack machine to replace the DC 2000 server.
Ultimately my aim is to:

- replace the DC 2000 server machine with the new machine
- and upgrade AD to 2003.

Im not sure in what order all this should be done however. Can anyone offer
some suggestions ?

i.e whats the best way to complete this task under my set of circumstances ?

Many thanks for any help.
Scott

 

[Phillip Windell]

Im not sure in what order all this should be done however. Can anyone offer
some suggestions ?

That depends on the end goal. Will the old machine still exist of be gone
totally? Does the new DC need to be the same name and IP# as the old one?

--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/ISA2004_AccessRules.html

Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/techinfo/Guidance/2004.asp
http://www.microsoft.com/isaserver/techinfo/Guidance/2000.asp

Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
-----------------------------------------------------

 

[Richard G. Harper]

Phillip raises excellent questions, but let me assume and explain the
simplest case - the new server will, in the end, be the only server:

1. Set up the new Windows Server 2003 computer as a domain member on the IP
address you want it to reside at using fixed IP addressing, not DHCP.

2. Install DNS on the new server and create a forward lookup zone
integrated into Active Directory. Have the new server look to itself for
name resolution once the DNS is up and stable.

3. On the existing DHCP server, have all clients start using the new DNS
server as primary DNS and your existing DNS server as backup DNS.

4. Once all clients have renewed their leases (either manually or
automatically) move your DHCP data from the old server to the new one,
de-activating the range(s) when backing them up and re-activating your
range(s) when restoring them.

5. Again, wait until all clients have renewed their leases. Promote the
new server to an AD domain controller.

6. Create a Global Catalog on the new server.

7. Demote the old Windows 2000 DC to a member server.

References:

Move DHCP: http://support.microsoft.com/kb/325473/
DNS FAQ: http://support.microsoft.com/kb/291382
Global Catalog:
http://www.microsoft.com/technet/pr...Ref/24311c41-d2a1-4e72-a54f-150483fa885a.mspx


--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[scott]

many thanks for the replies and links....gives me a good starting point. not
really decided what to do with the old DC yet but your plan Richard looks
like a good way to go.

Point 6 and 7 mention creating a catalog and demoting the old DC to a
member. Can that we done easily enough between 2000 and 2003 AD ? i.e does
this process effectivly upgrate 2000 AD to 2003 ?

Thanks again.
Scott

 

[Richard G. Harper]

Yes, it does - but I did leave out one little step, you need to prep the
domain before you can bring up the first Windows Server 2003 domain
controller:

http://www.microsoft.com/technet/pr...Kit/3f4b9633-234e-465a-b9c4-0e08fe703d1c.mspx

--
Richard G. Harper [MVP Shell/User] (e-mail address removed)
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm

 

[scott]

excellent, thanks
scott