A couple things to watch out for:
- Windows 2003 will try to change your AD setup from "Compatible" to
"Native". This means that any legacy software of hardware that
communicates directly with your domain may break. Watch our for old
printers, NT 4 boxes, or old SANs. If this is not a concern, then the
upgrade should go smoothly.
- Windows 2003 will try to remove any unsigned plug-ins to your tree.
I've seen this take out all the configuration from a 3rd party mail
server. Again, this usually isn't a concern, but you need to watch out
for it.
- Windows 2003 by default does not have many services turned on. This
shouldn't affect much (other than security), but if you have some 3rd
party applications expect certain services to just 'be there', you may
need to install/turn them on.
Otherwise, good luck. 2000 -> 2003 has been pretty painless in my
experience.
-Nick Kwiatkowski
MSU Telecom Systems
-----Original Message-----
From: MSU Network Administrators Group [mailto:[log in to unmask]] On
Behalf Of Oscar Castaneda
Sent: Thursday, September 06, 2007 9:33 AM
To: [log in to unmask]
Subject: [MSUNAG] upgrading domain controller
List,
I am running a windows domain with a domain controller on Windows 2000.
I have a new server with Windows 2003 and I want to make it the domain
controller.
The 2003 server is brand new, I haven't even turn it on.
I had been reading what I found available in the internet about a 2003
taking over a domain from a 2000 but I would like to listen stories or
experiences of people who went through this transition before. I am sure
that many of you already did it.
According with what I had seen, it seems to be an straight forward
procedure, but you never know and I would not like to make my network go
down.
--
Oscar Castaneda
Michigan State University
|
