Best way to replace a server and do clean install

[Guest Jack B. Pollack]

We will be replacing our old Win2K3 Server with a new one shortly. Not only

is the actual hardware antiquated, but the OS has been experiencing many

problems over the last year and I look forward to a clean install.

 

Since I am doing a clean install instead of some type of migration all of

the users will have to be manually re-added to the domain. There are only 14

users so this is not a terrible task.

 

My concern is that when I try to add the old user to the new domain it will

create a new user account for them on their local machines and that all of

their personal settings and desktop etc will be "lost".

 

Am I making this into a bigger project then it really is?

Will I just be able to go to each machine, log on with admin account and

join the "new" domain and the same user account on the Workstation side will

be used?

 

Any other advice?

 

Thanks.

[Guest Meinolf Weber]

Re: Best way to replace a server and do clean install

 

Hello Jack,

 

!!!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?

 

Add the new server after fresh install as additional DC, install DNS DHCP

and give it time for replication. Then make it Global catalog server and

move the 5 FSMO roles. After that copy your data, if needed. So the only

change for the users will be a new data server if this one is used for and

a new DNS server which will be provided with the DHCP scope options.

 

See here for step by step:

- 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 from the first DC:

 

- 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

> We will be replacing our old Win2K3 Server with a new one shortly. Not

> only is the actual hardware antiquated, but the OS has been

> experiencing many problems over the last year and I look forward to a

> clean install.

>

> Since I am doing a clean install instead of some type of migration all

> of the users will have to be manually re-added to the domain. There

> are only 14 users so this is not a terrible task.

>

> My concern is that when I try to add the old user to the new domain it

> will create a new user account for them on their local machines and

> that all of their personal settings and desktop etc will be "lost".

>

> Am I making this into a bigger project then it really is?

> Will I just be able to go to each machine, log on with admin account

> and

> join the "new" domain and the same user account on the Workstation

> side will

> be used?

> Any other advice?

>

> Thanks.

>

[Guest Jack B. Pollack]

Re: Best way to replace a server and do clean install

 

WOW!

 

Thanks for your post.

This is even more complicated then I first thought.

 

<Meinolf Weber> wrote in message

news:ff16fb66a256a8caa85858900d40@msnews.microsoft.com...

> Hello Jack,

>

> !!!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?

>

> Add the new server after fresh install as additional DC, install DNS DHCP

> and give it time for replication. Then make it Global catalog server and

> move the 5 FSMO roles. After that copy your data, if needed. So the only

> change for the users will be a new data server if this one is used for and

> a new DNS server which will be provided with the DHCP scope options.

>

> See here for step by step:

> - 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 from the first DC:

>

> - 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

>

> > We will be replacing our old Win2K3 Server with a new one shortly. Not

> > only is the actual hardware antiquated, but the OS has been

> > experiencing many problems over the last year and I look forward to a

> > clean install.

> >

> > Since I am doing a clean install instead of some type of migration all

> > of the users will have to be manually re-added to the domain. There

> > are only 14 users so this is not a terrible task.

> >

> > My concern is that when I try to add the old user to the new domain it

> > will create a new user account for them on their local machines and

> > that all of their personal settings and desktop etc will be "lost".

> >

> > Am I making this into a bigger project then it really is?

> > Will I just be able to go to each machine, log on with admin account

> > and

> > join the "new" domain and the same user account on the Workstation

> > side will

> > be used?

> > Any other advice?

> >

> > Thanks.

> >

>

>

[Guest Jack B. Pollack]

Re: Best way to replace a server and do clean install

 

BTW, no Exchange server on our network.

 

 

"Jack B. Pollack" <N@NE.nothing> wrote in message

news:#n0wZjj2IHA.528@TK2MSFTNGP02.phx.gbl...

> WOW!

>

> Thanks for your post.

> This is even more complicated then I first thought.

>

> <Meinolf Weber> wrote in message

> news:ff16fb66a256a8caa85858900d40@msnews.microsoft.com...

> > Hello Jack,

> >

> > !!!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?

> >

> > Add the new server after fresh install as additional DC, install DNS

DHCP

> > and give it time for replication. Then make it Global catalog server and

> > move the 5 FSMO roles. After that copy your data, if needed. So the only

> > change for the users will be a new data server if this one is used for

and

> > a new DNS server which will be provided with the DHCP scope options.

> >

> > See here for step by step:

> > - 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 from the first DC:

> >

> > - 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

> >

> > > We will be replacing our old Win2K3 Server with a new one shortly. Not

> > > only is the actual hardware antiquated, but the OS has been

> > > experiencing many problems over the last year and I look forward to a

> > > clean install.

> > >

> > > Since I am doing a clean install instead of some type of migration all

> > > of the users will have to be manually re-added to the domain. There

> > > are only 14 users so this is not a terrible task.

> > >

> > > My concern is that when I try to add the old user to the new domain it

> > > will create a new user account for them on their local machines and

> > > that all of their personal settings and desktop etc will be "lost".

> > >

> > > Am I making this into a bigger project then it really is?

> > > Will I just be able to go to each machine, log on with admin account

> > > and

> > > join the "new" domain and the same user account on the Workstation

> > > side will

> > > be used?

> > > Any other advice?

> > >

> > > Thanks.

> > >

> >

> >

>

>

[Guest Meinolf Weber]

Re: Best way to replace a server and do clean install

 

Hello Jack,

 

It isn't comlicated, just some more steps that you might saw before. But

everything is really easy to do. You will see.

 

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

> BTW, no Exchange server on our network.

>

> "Jack B. Pollack" <N@NE.nothing> wrote in message

> news:#n0wZjj2IHA.528@TK2MSFTNGP02.phx.gbl...

>> WOW!

>>

>> Thanks for your post.

>> This is even more complicated then I first thought.

>> <Meinolf Weber> wrote in message

>> news:ff16fb66a256a8caa85858900d40@msnews.microsoft.com...

>>> Hello Jack,

>>>

>>> !!!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?

>>>

>>> Add the new server after fresh install as additional DC, install DNS

>>>

> DHCP

>

>>> and give it time for replication. Then make it Global catalog server

>>> and move the 5 FSMO roles. After that copy your data, if needed. So

>>> the only change for the users will be a new data server if this one

>>> is used for

>>>

> and

>

>>> a new DNS server which will be provided with the DHCP scope options.

>>>

>>> See here for step by step:

>>> - 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 from the first DC:

>>>

>>> - 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

>>>> We will be replacing our old Win2K3 Server with a new one shortly.

>>>> Not only is the actual hardware antiquated, but the OS has been

>>>> experiencing many problems over the last year and I look forward to

>>>> a clean install.

>>>>

>>>> Since I am doing a clean install instead of some type of migration

>>>> all of the users will have to be manually re-added to the domain.

>>>> There are only 14 users so this is not a terrible task.

>>>>

>>>> My concern is that when I try to add the old user to the new domain

>>>> it will create a new user account for them on their local machines

>>>> and that all of their personal settings and desktop etc will be

>>>> "lost".

>>>>

>>>> Am I making this into a bigger project then it really is?

>>>> Will I just be able to go to each machine, log on with admin

>>>> account

>>>> and

>>>> join the "new" domain and the same user account on the Workstation

>>>> side will

>>>> be used?

>>>> Any other advice?

>>>> Thanks.

>>>>

[Guest Hank Arnold (MVP)]

Re: Best way to replace a server and do clean install

 

It's actually a lot less complicated than rebuilding the domain. Do a

search on the MS Knowledge base (and Google) and you'll find some very

good step by step processes for this.

 

If the DC in question is the only one, I would suggest you:

 

1) build the new DC and migrate to it as Meinolf described.

2) Take the old DC off line for several days

3) If everything works, power up the old DC.

4) Use DCPROMO to make the old DC a member server

5) Remove it from the domain. Clean up AD to remove any leftover entries

(DNS also)

6) Rebuild the server (clean install) and DCPROMO it as a second DC.

 

It's vital that you have more than one DC in a domain. Think about what

would happen if you were to lose the only DC.... Having a second DC

makes it possible to keep operating until the failed DC can be rebuilt

and/or replaced....

 

BTW, the process that Meinolf described assumes that the OS on the new

server is the same as on the old one. If you were to go with, say 2008,

you would have to upgrade AD first....

 

--

 

Regards,

Hank Arnold

Microsoft MVP

Windows Server - Directory Services

 

Jack B. Pollack wrote:

> WOW!

>

> Thanks for your post.

> This is even more complicated then I first thought.

>

> <Meinolf Weber> wrote in message

> news:ff16fb66a256a8caa85858900d40@msnews.microsoft.com...

>> Hello Jack,

>>

>> !!!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?

>>

>> Add the new server after fresh install as additional DC, install DNS DHCP

>> and give it time for replication. Then make it Global catalog server and

>> move the 5 FSMO roles. After that copy your data, if needed. So the only

>> change for the users will be a new data server if this one is used for and

>> a new DNS server which will be provided with the DHCP scope options.

>>

>> See here for step by step:

>> - 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 from the first DC:

>>

>> - 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

>>

>>> We will be replacing our old Win2K3 Server with a new one shortly. Not

>>> only is the actual hardware antiquated, but the OS has been

>>> experiencing many problems over the last year and I look forward to a

>>> clean install.

>>>

>>> Since I am doing a clean install instead of some type of migration all

>>> of the users will have to be manually re-added to the domain. There

>>> are only 14 users so this is not a terrible task.

>>>

>>> My concern is that when I try to add the old user to the new domain it

>>> will create a new user account for them on their local machines and

>>> that all of their personal settings and desktop etc will be "lost".

>>>

>>> Am I making this into a bigger project then it really is?

>>> Will I just be able to go to each machine, log on with admin account

>>> and

>>> join the "new" domain and the same user account on the Workstation

>>> side will

>>> be used?

>>> Any other advice?

>>>

>>> Thanks.

>>>

>>

>

>

[Guest Meinolf Weber]

Re: Best way to replace a server and do clean install

 

Hello Hank,

 

Because he didn't mention server 2008 i skipped that part. :-)

 

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

> It's actually a lot less complicated than rebuilding the domain. Do a

> search on the MS Knowledge base (and Google) and you'll find some very

> good step by step processes for this.

>

> If the DC in question is the only one, I would suggest you:

>

> 1) build the new DC and migrate to it as Meinolf described.

> 2) Take the old DC off line for several days

> 3) If everything works, power up the old DC.

> 4) Use DCPROMO to make the old DC a member server

> 5) Remove it from the domain. Clean up AD to remove any leftover

> entries

> (DNS also)

> 6) Rebuild the server (clean install) and DCPROMO it as a second DC.

> It's vital that you have more than one DC in a domain. Think about

> what would happen if you were to lose the only DC.... Having a second

> DC makes it possible to keep operating until the failed DC can be

> rebuilt and/or replaced....

>

> BTW, the process that Meinolf described assumes that the OS on the new

> server is the same as on the old one. If you were to go with, say

> 2008, you would have to upgrade AD first....

>

> Jack B. Pollack wrote:

>

>> WOW!

>>

>> Thanks for your post.

>> This is even more complicated then I first thought.

>> <Meinolf Weber> wrote in message

>> news:ff16fb66a256a8caa85858900d40@msnews.microsoft.com...

>>> Hello Jack,

>>>

>>> !!!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?

>>>

>>> Add the new server after fresh install as additional DC, install DNS

>>> DHCP and give it time for replication. Then make it Global catalog

>>> server and move the 5 FSMO roles. After that copy your data, if

>>> needed. So the only change for the users will be a new data server

>>> if this one is used for and a new DNS server which will be provided

>>> with the DHCP scope options.

>>>

>>> See here for step by step:

>>> - 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 from the first DC:

>>>

>>> - 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

>>>> We will be replacing our old Win2K3 Server with a new one shortly.

>>>> Not only is the actual hardware antiquated, but the OS has been

>>>> experiencing many problems over the last year and I look forward to

>>>> a clean install.

>>>>

>>>> Since I am doing a clean install instead of some type of migration

>>>> all of the users will have to be manually re-added to the domain.

>>>> There are only 14 users so this is not a terrible task.

>>>>

>>>> My concern is that when I try to add the old user to the new domain

>>>> it will create a new user account for them on their local machines

>>>> and that all of their personal settings and desktop etc will be

>>>> "lost".

>>>>

>>>> Am I making this into a bigger project then it really is?

>>>> Will I just be able to go to each machine, log on with admin

>>>> account

>>>> and

>>>> join the "new" domain and the same user account on the Workstation

>>>> side will

>>>> be used?

>>>> Any other advice?

>>>> Thanks.

>>>>

[Guest Paul Bergson [MVP-DS]]

Re: Best way to replace a server and do clean install

 

I have an article on decommissioning a dc to help you with it step by step

 

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.

 

"Jack B. Pollack" <N@NE.nothing> wrote in message

news:utB43Di2IHA.1768@TK2MSFTNGP03.phx.gbl...

> We will be replacing our old Win2K3 Server with a new one shortly. Not

> only

> is the actual hardware antiquated, but the OS has been experiencing many

> problems over the last year and I look forward to a clean install.

>

> Since I am doing a clean install instead of some type of migration all of

> the users will have to be manually re-added to the domain. There are only

> 14

> users so this is not a terrible task.

>

> My concern is that when I try to add the old user to the new domain it

> will

> create a new user account for them on their local machines and that all of

> their personal settings and desktop etc will be "lost".

>

> Am I making this into a bigger project then it really is?

> Will I just be able to go to each machine, log on with admin account and

> join the "new" domain and the same user account on the Workstation side

> will

> be used?

>

> Any other advice?

>

> Thanks.

>

>

[Guest Jack B. Pollack]

Re: Best way to replace a server and do clean install

 

Thanks to all that responded. The new server is on order and it will

probably be a few weeks before I actually try all this. I'll post back if I

have problems.

 

Thanks again

 

 

"Paul Bergson [MVP-DS]" <pbergson@allete_nospam.com> wrote in message

news:e3DYl9q2IHA.552@TK2MSFTNGP06.phx.gbl...

> I have an article on decommissioning a dc to help you with it step by step

>

> 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.

>

> "Jack B. Pollack" <N@NE.nothing> wrote in message

> news:utB43Di2IHA.1768@TK2MSFTNGP03.phx.gbl...

> > We will be replacing our old Win2K3 Server with a new one shortly. Not

> > only

> > is the actual hardware antiquated, but the OS has been experiencing many

> > problems over the last year and I look forward to a clean install.

> >

> > Since I am doing a clean install instead of some type of migration all

of

> > the users will have to be manually re-added to the domain. There are

only

> > 14

> > users so this is not a terrible task.

> >

> > My concern is that when I try to add the old user to the new domain it

> > will

> > create a new user account for them on their local machines and that all

of

> > their personal settings and desktop etc will be "lost".

> >

> > Am I making this into a bigger project then it really is?

> > Will I just be able to go to each machine, log on with admin account and

> > join the "new" domain and the same user account on the Workstation side

> > will

> > be used?

> >

> > Any other advice?

> >

> > Thanks.

> >

> >

>

>