Developer Forum

I have a windows 2003 Domain controller that is just about ready for
retirement. This was the first 2003 Domain controller installed into our
domain and at the moment houses all of the FSMO roles. We have 4 locations
each running 2 2003 domain controllers and we are also running exchange 2007
on windows 2003 as a member server.
My plan is to run adprep/ forestprep and adprep/ domainprep from the windows
2008 server CD on my 2003 domain controller that houses the all of the FSMO
roles, and then introduce a new windows 2008 server to the domain. Afterwards
move the FMSO roles to the new windows 2008 server. After I confirm that
everything is working properly I would run DC Promo on the old windows 2003
server and take it off line.

If the procedure is correct, then here are my questions.
Are there any other steps I should be taking since the old 2003 server was
the first 2003 server introduced to the domain?

Should I move all of the roles to the new windows 2008 server? or split them
between another windows 2003 domain controller and the new 2008 domain
controller, or should I move all of the rolls to the other windows 2003
server?

Am I missing any steps?

TIA
--
erock

Hello erock,

You plan sounds ok.

Before starting i would run replmon from the run line or repadmin /showrepl,
dcdiag /v and netdiag /v from the command prompt on the existing DC's to
check for errors, if you have some post the complete output from the command
here or solve them first. For this tools you have to install the support\tools\suptools.msi
from the 2003 installation disk.

The FSMO roles should be held by the newest OS DC, so new AD group for example
will be created. ( http://www.yqcomputer.com/
2008)

Switch to AD integrated DNS zones if not done.

Also run adprep /rodcprep to prepare for read-only domain controllers.

Make all DC's GC in a single forest domain.

During promotion configure a fixed ip and set the preferred DNS server to
one older DC/DNS server only, after everything is replicated set itself as
preferred and another domain DNS as secondary.

Do not forget to reconfigure client DNS settings for the new DC/DNS.

After promotion run again the diagnostic tools, on the 2008 copy the netdiag
from a 2003 DC, rest is included.

To check for problems just disconnect the old DC for some days from the network,
if none exist reconnect and then demote it.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.yqcomputer.com/

You should also consider what role, if any, this DC has in a certificate
authority before de-comishing.



--
/kj