Re: Steps For Upgrading From NT4
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Wed, 28 May 2008 14:03:18 -0500
"Tom M" <TomM@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B0C25862-0F6D-430C-81CD-BE47CFFF414B@xxxxxxxxxxxxxxxx
I am trying to resolve a couple of questions about upgrading from a single
NT4 domain to an single 2003 AD domain. I currently have an small single
NT4
domain with a PDC and a BDC. Neither of these are easily upgradable to
2003.
The PDC is the ONLY computer which can upgrade an NT domain.
You have two basic choices for upgrade:
1) Move/upgrade the NT PDC to better hardware
2) Install an NT4 BDC on new(er) hardware that will support Windows
Server
Promote to PDC, then do the upgrade.
There are NO OTHER choices (except combos of this).
Also note, I have heard from people that their "NT4 cannot be upgraded"
when this was actually possible. Pentium, 128 MB, some harddrive space,
decent/updated BIOS, will usually do it -- and going to Win2000 first might
make it a TAD easier.
I have a 2003 member server that was deployed last year and a new 2003
server
sitting in a box yet to be deployed.
You must temporarily remove and install NT4 on one of them to use this
method.
My plan is to use a temporary NT4 server to upgrade to 2003 AD. I need to
setup a new DHCP server as my current BDC is fulfilling that role. I also
The BDC can live in the Win2003 domain so you don't have to consider
this part of the "same step".
Separate the UPGRADE from all other issues that you can.
obviously need a DNS server. Both of my new servers are going to be domain
controllers. So, this is my plan:
1. Deploy the server in the box as a member server, install DHCP and DNS.
I would not do that. The upgraded PDC can be the DNS (easier because it
will ASK you) and the current BDC can remain DHCP until you get the
domain under control.
2. Shut down my NT4 BDC and save it as a rollback server. This is
currently
my DHCP and WINS server.
We used to recommend this but it is (practically) never needed nor useful,
so if you have decent NT4 DC backups you can skipp it. If you don't have
good backups it is time to start making those backups.
3. Upgrade my temporary server from NT4 to 2003 and upgrade the domain to
interim 2003 AD.
That works. And it will offer to install DNS for you (correctly) as part of
that.
Let it.
4. Promote the new member server to a domain controller.
Ok.
5. Promote the older 2003 member server to a domain controller.
Ok.
6. Shut down the temporary server.
If it is a DC then it needs to first be DCPromo'd to non-DC.
Why do this? Use one of the DCs that will remain if you can
Is there information that would be on the temporary server that I would
need
to move to the new domain controller before shutting it down?
DCPromo needs to be run.
And if it is your DNS then you need to arrange for that.
You also need to arrange for the FSMO roles to move if you either
don't run DCPromo OR you want to be sure (which I prefer.)
What about WINS Server? Do you have more than one subnet?
You still need WINS Server if so. (And ALL machines are WINS
clients, especially DCs.)
Can I setup DNS on a 2003 member server and have that become the AD DNS
server when I do the upgrade?
Yes. Dynamic Zone corresponding to the AD Domain name.
Is there another way to do this that makes more sense?
There are ways that are more straight forward and easier but your
way works.
.
- Prev by Date: password complexity requirement
- Next by Date: Re: after NT to 2003, how to remove the NT domain
- Previous by thread: Re: Steps For Upgrading From NT4
- Next by thread: Re: Steps For Upgrading From NT4
- Index(es):
Relevant Pages
|
Loading
