RE: NT4.0 to 2003
- From: "mikes1p" <mikes1p@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 20 Dec 2005 12:18:02 -0800
I'm a week or two ahead of you so I feel your pain, the figuring out how to
ACTUALLY do the AD migration is not clearly spelled out, lot's of half cooked
sources of info
Are you doing an "Inplace" upgrade or "migrating" to a new AD domain?
My suggestions below are for the "inplace" approach, which is what I'm
working right now for our old NT domain
> 1) I want the new computer (2003) to eventually have the same ip address and
> name once i take the old computer offline. Is this possible and at what
> point do i/can i rename the computer,domain,ipaddress?
Yes then new box can have the same IP and name. How you get there is a bit
convoluted. I'd give up on the idea of installing NT on the new server unless
you find NT drivers for the new hardware.
You need an temporary NT box, installed fresh as a BDC, using a different IP
and name. Sync the netlogon shares if you use them. Promote it to the PDC
then turn off/unplug your original NT PDC, it will be your fall back server
if things go wrong.
Upgrade the temp PDC to Server 2003 and have it be the first AD Domain
controller. Run AD in mixed mode, the temp DC looks like an NT PDC to the NT
clients.
You can probably change the new machines name and IP after you install 2003
but I haven't done that so I cannot vouch for that. This should work: remove
the old NT PDC's account from the AD Domain, install Server 2003 fresh on
your new box using the name and IP of your old, add it as the second DC. Once
you are golden remove the the temp AD server
If things go sour, just turn off the 2003 AD servers, and plug in your old PDC
> Also, if I have to use a new domain name can i use FNBNEWTOWN.COM and
> what effect does this have on workstations where the domain is set to
> FNBNEWTOWN.
The AD wizard asks you what you want the NetBios name to be for the domain,
just use FNBNEWTON. If you do an "inplace upgrade" of the FNBNEWTOWN domain
the NT clients still see the same old domain name, in fact the domain looks
just like the existing NT domain.
> 2) NT 4.0 has a limit on the o/s partition size how do i increase the size
> of the partition after or before the upgrade?
Assuming you go the round about way I'm suggesting you won't be installing
NTon the new hardware, you'll be installing Server 2003 on the new hardware.
Server 2003 allows larger boot partitions. If you gotta go NT first, many
disk cloning apps let you resize NT partitions when restoring so they can be
larger than the NT installer will allow
> 3) How do i go about the upgrade if i can not get nt 4.0 drivers for the new
> hardware specific to the sata raid controller?
See my reply to #1
You need a lab system, simple as that. I found mine to be the best thing
I've done to understand upgrading to AD. I know it's a pain but all I can say
is you don't want to fly blind into an upgrade of a production domain, to
many questions and things you need to figure out as you go, you cannot find
the answers online fast enough. Go find some old PIII's at salvage place if
you have to, you want to get the same hardware as your NT PDC or at least the
same disk controller, then clone your PDC and restore it to your lab. Failing
that install NT fresh and mimic your production domain as best you can
Good luck
Mike
"Chip pellegrino" wrote:
> I know these nt to 2003 posts are repetitive but i still don't know what
> i am doing.
> We currently have 1 PDC called scomputer2 the domain is FNBNEWTOWN and it is
> running nt 4.0. I would like to upgrade it to 2003, but on a new
> box/hardware. I have read the posts about installing nt 4.0 on it and making
> it a bdc, syncing it, promoting it to a pdc and then upgrading it. I have
> the following questions about this:
>
> 1) I want the new computer (2003) to eventually have the same ip address and
> name once i take the old computer offline. Is this possible and at what
> point do i/can i rename the computer,domain,ipaddress? Also, if I have to
> use a new domain name can i use FNBNEWTOWN.COM and what effect does this have
> on workstations where the domain is set to FNBNEWTOWN. Would i have to go
> around to all the workstations and change it?
>
> 2) NT 4.0 has a limit on the o/s partition size how do i increase the size
> of the partition after or before the upgrade?
>
> 3) How do i go about the upgrade if i can not get nt 4.0 drivers for the new
> hardware specific to the sata raid controller?
>
>
.
- Prev by Date: Upgrade Server 2003 to Server 2003 R2
- Next by Date: Problems migrating from NT4 to 2003
- Previous by thread: Upgrade Server 2003 to Server 2003 R2
- Next by thread: Problems migrating from NT4 to 2003
- Index(es):
Relevant Pages
|
