Hi,

I am getting a new server intended to replace my existing Windows 2000 server

I need to verfiy the process aof adding this new server 2003 and what needs
tobe done to get my active directory onto this new server


appreciate any help

Re: Getting a new Domain Controller by Danny

Danny
Tue Jun 17 12:57:09 PDT 2008

Run adprep/forest prep to prepare your Win 2k domain for Win 2k3. If you
have the Win 2k3 R2 version you will have to run adprep a second time but
from the second CD of the R2 set. Add the server to the domain as a member
server then riun dcpromo to make it a DC.

I would suggest keeping the Win 2k DC on line for redundancy. You could
upgrade it to Win 2k3 if you want.


hth
DDS

"Dan DeCoursey" <DanDeCoursey@discussions.microsoft.com> wrote in message
news:1E360C43-8370-48A4-A6A7-9A8BCCB6A60B@microsoft.com...
> Hi,
>
> I am getting a new server intended to replace my existing Windows 2000
> server
>
> I need to verfiy the process aof adding this new server 2003 and what
> needs
> tobe done to get my active directory onto this new server
>
>
> appreciate any help



Re: Getting a new Domain Controller by Meinolf

Meinolf
Tue Jun 17 13:37:55 PDT 2008

Hello Dan,

!!!NEVER START BEFORE HAVING CREATED A BACKUP OF YOU DATA/MACHINE!!!

One question first:
Is the old server also Exchange server and will it be taken out of the domain

forever, when the new server is running?

- On the old server open DNS management console and check that you are running
Active directory integrated zone (easier for replication, if you have more
then one DNS server)

- run replmon, dcdiag and netdiag on the old machine to check for errors,
if you have some post the complete output from the command here or solve
them first

- run adprep /forestprep and adprep /domainprep from the 2003 installation
disk against the 2000 server, with an account that is member of the Schema
admins, to upgrade the schema to the new version 30 and secondly from the
second disk if it is R2 to version 31.

- Install the new machine as a member server in your existing domain

- configure a fixed ip and set the preferred DNS server to the old DNS server
only

- run dcpromo and follow the wizard to add the 2003 server to an existing
domain

- if you are prompted for DNS configuration choose Yes (also possible that
no DNS preparation occur), then install DNS after the reboot

- for DNS give the server time for replication, at least 15 minutes. Because
you use Active directory integrated zones it will automatically replicate
the zones to the new server. Open DNS management console to check that they
appear

- if the new machine is domain controller and DNS server run again replmon,
dcdiag and netdiag on both domain controllers

- if you have no errors, make the new server GLobal catalog server, open
Active directory Sites and Services and then double-click sitename, double-click
Servers, click your domain controller, right-click NTDS Settings, and then
click Properties, on the General tab, click to select the Global catalog
check box (http://support.microsoft.com/?id=313994)

- Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801)

- you can see in the event viewer (Directrory service) that the roles are
transferred, also give it some time

- reconfigure the DNS configuration on your NIC of the 2003 server, preferred
DNS itself, secondary the old one

- if you use DHCP do not forget to reconfigure the scope settings to point
to the new installed DNS server

- export and import of DHCP database (if needed) http://support.microsoft.com/kb/325473


Demoting if needed (But you should always have 2 DC's for redundancy and
failover reason)

- reconfigure your clients/servers that they not longer point to the old
DC/DNS server on the NIC

- to be sure that everything runs fine, disconnect the old DC from the network
and check with clients and servers the connectivity, logon and also with
one client a restart to see that everything is ok

- then run dcpromo to demote the old DC, if it works fine the machine will
move from the DC's OU to the computers container, where you can delete it
by hand. Can be that you got an error during demoting at the beginning, then
uncheck the Global catalog on that DC and try again

- check the DNS management console, that all entries from the machine are
disappeared or delete them by hand if the machine is off the network for ever



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.blakjak.demon.co.uk/mul_crss.htm

> Hi,
>
> I am getting a new server intended to replace my existing Windows 2000
> server
>
> I need to verfiy the process aof adding this new server 2003 and what
> needs tobe done to get my active directory onto this new server
>
> appreciate any help
>



Re: Getting a new Domain Controller by Paul

Paul
Wed Jun 18 05:55:12 PDT 2008

I have an article that should help you out on this:

http://www.pbbergs.com/windows/articles.htm
Select Decommission a DC

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"Dan DeCoursey" <DanDeCoursey@discussions.microsoft.com> wrote in message
news:1E360C43-8370-48A4-A6A7-9A8BCCB6A60B@microsoft.com...
> Hi,
>
> I am getting a new server intended to replace my existing Windows 2000
> server
>
> I need to verfiy the process aof adding this new server 2003 and what
> needs
> tobe done to get my active directory onto this new server
>
>
> appreciate any help



Re: Getting a new Domain Controller by DanDeCoursey

DanDeCoursey
Wed Jun 18 05:55:01 PDT 2008

Hello Meinhoff,


The old serve is our current DC and the new once is intended to be the new
DC it is not an exchange server I might leave this old server online
just to replicate to since we only ever had the one server i never ahd any
replication going on

"Meinolf Weber" wrote:

> Hello Dan,
>
> !!!NEVER START BEFORE HAVING CREATED A BACKUP OF YOU DATA/MACHINE!!!
>
> One question first:
> Is the old server also Exchange server and will it be taken out of the domain
>
> forever, when the new server is running?
>
> - On the old server open DNS management console and check that you are running
> Active directory integrated zone (easier for replication, if you have more
> then one DNS server)
>
> - run replmon, dcdiag and netdiag on the old machine to check for errors,
> if you have some post the complete output from the command here or solve
> them first
>
> - run adprep /forestprep and adprep /domainprep from the 2003 installation
> disk against the 2000 server, with an account that is member of the Schema
> admins, to upgrade the schema to the new version 30 and secondly from the
> second disk if it is R2 to version 31.
>
> - Install the new machine as a member server in your existing domain
>
> - configure a fixed ip and set the preferred DNS server to the old DNS server
> only
>
> - run dcpromo and follow the wizard to add the 2003 server to an existing
> domain
>
> - if you are prompted for DNS configuration choose Yes (also possible that
> no DNS preparation occur), then install DNS after the reboot
>
> - for DNS give the server time for replication, at least 15 minutes. Because
> you use Active directory integrated zones it will automatically replicate
> the zones to the new server. Open DNS management console to check that they
> appear
>
> - if the new machine is domain controller and DNS server run again replmon,
> dcdiag and netdiag on both domain controllers
>
> - if you have no errors, make the new server GLobal catalog server, open
> Active directory Sites and Services and then double-click sitename, double-click
> Servers, click your domain controller, right-click NTDS Settings, and then
> click Properties, on the General tab, click to select the Global catalog
> check box (http://support.microsoft.com/?id=313994)
>
> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801)
>
> - you can see in the event viewer (Directrory service) that the roles are
> transferred, also give it some time
>
> - reconfigure the DNS configuration on your NIC of the 2003 server, preferred
> DNS itself, secondary the old one
>
> - if you use DHCP do not forget to reconfigure the scope settings to point
> to the new installed DNS server
>
> - export and import of DHCP database (if needed) http://support.microsoft.com/kb/325473
>
>
> Demoting if needed (But you should always have 2 DC's for redundancy and
> failover reason)
>
> - reconfigure your clients/servers that they not longer point to the old
> DC/DNS server on the NIC
>
> - to be sure that everything runs fine, disconnect the old DC from the network
> and check with clients and servers the connectivity, logon and also with
> one client a restart to see that everything is ok
>
> - then run dcpromo to demote the old DC, if it works fine the machine will
> move from the DC's OU to the computers container, where you can delete it
> by hand. Can be that you got an error during demoting at the beginning, then
> uncheck the Global catalog on that DC and try again
>
> - check the DNS management console, that all entries from the machine are
> disappeared or delete them by hand if the machine is off the network for ever
>
>
>
> 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.blakjak.demon.co.uk/mul_crss.htm
>
> > Hi,
> >
> > I am getting a new server intended to replace my existing Windows 2000
> > server
> >
> > I need to verfiy the process aof adding this new server 2003 and what
> > needs tobe done to get my active directory onto this new server
> >
> > appreciate any help
> >
>
>
>