Replace single DC question

We are upgrading to a new single DC. This DC will eventually replace old DC
which will be used just for testing.
I have read that the best way to do this is to first install new server as a
member and then promote it to a DC.
If I do this and demote OLD DC will the clients find the DNS that now lives
on the new DC?
When I demote old DC will it be recognized as member server?
When I promote new DC replication will occur. Does that mean AD etc.... now
lives on the OLD and New DC?
Can someone clarify the sequence of steps to make this happen?

Will Sellers <(E-Mail Removed)> wrote:
> We are upgrading to a new single DC. This DC will eventually replace
> old DC which will be used just for testing.
> I have read that the best way to do this is to first install new
> server as a member and then promote it to a DC.

Yes....and install DNS, and make it a global catalog server, and transfer
all the FSMO roles (if the old DC is/was the first/only DC on your network).

> If I do this and demote OLD DC will the clients find the DNS that now
> lives on the new DC?

If you use DHCP, change the scope to point all clients at the new server for
DNS (and for WINS, if you use that).

> When I demote old DC will it be recognized as member server?

Yes.

> When I promote new DC replication will occur. Does that mean AD
> etc.... now lives on the OLD and New DC?

Yes.


> Can someone clarify the sequence of steps to make this happen?

Hope the above helps.

You need to transfer the ad roles. This how to may help,

How to trasnfer AD rolesThis article describes how to transfer Flexible Single Master Operations (FSMO) roles (also known as operations master roles) by using the Active Directory ...
http://www.howtonetworking.com/artic...feradroles.htm


Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
"Will Sellers" <(E-Mail Removed)> wrote in message news:SJ8fi.275$w2.63@trnddc01...
We are upgrading to a new single DC. This DC will eventually replace old DC
which will be used just for testing.
I have read that the best way to do this is to first install new server as a
member and then promote it to a DC.
If I do this and demote OLD DC will the clients find the DNS that now lives
on the new DC?
When I demote old DC will it be recognized as member server?
When I promote new DC replication will occur. Does that mean AD etc.... now
lives on the OLD and New DC?
Can someone clarify the sequence of steps to make this happen?

Thanks for the response. I understand everything except where you state
Change the scope to point clients at the new server.
We do use DHCP
Are you saying that I need to change settings in the dhcp that now lives on
the new server?

"Lanwench [MVP - Exchange]"
<(E-Mail Removed) hoo.com> wrote in message
news:eqXV$(E-Mail Removed)...
> Will Sellers <(E-Mail Removed)> wrote:
>> We are upgrading to a new single DC. This DC will eventually replace
>> old DC which will be used just for testing.
>> I have read that the best way to do this is to first install new
>> server as a member and then promote it to a DC.
>
> Yes....and install DNS, and make it a global catalog server, and transfer
> all the FSMO roles (if the old DC is/was the first/only DC on your
> network).
>
>> If I do this and demote OLD DC will the clients find the DNS that now
>> lives on the new DC?
>
> If you use DHCP, change the scope to point all clients at the new server
> for DNS (and for WINS, if you use that).
>
>> When I demote old DC will it be recognized as member server?
>
> Yes.
>
>> When I promote new DC replication will occur. Does that mean AD
>> etc.... now lives on the OLD and New DC?
>
> Yes.
>
>
>> Can someone clarify the sequence of steps to make this happen?
>
> Hope the above helps.
>
>
>

Will Sellers <(E-Mail Removed)> wrote:
> Thanks for the response. I understand everything except where you
> state Change the scope to point clients at the new server.
> We do use DHCP
> Are you saying that I need to change settings in the dhcp that now
> lives on the new server?

Your DHCP scope needs to specify the correct DNS and WINS server IPs.....so
if you're changing them, you need to change your DHCP scope too (and change
the same settings in any static IP configss as well).
>
> "Lanwench [MVP - Exchange]"
> <(E-Mail Removed) hoo.com> wrote in
> message news:eqXV$(E-Mail Removed)...
>> Will Sellers <(E-Mail Removed)> wrote:
>>> We are upgrading to a new single DC. This DC will eventually replace
>>> old DC which will be used just for testing.
>>> I have read that the best way to do this is to first install new
>>> server as a member and then promote it to a DC.
>>
>> Yes....and install DNS, and make it a global catalog server, and
>> transfer all the FSMO roles (if the old DC is/was the first/only DC
>> on your network).
>>
>>> If I do this and demote OLD DC will the clients find the DNS that
>>> now lives on the new DC?
>>
>> If you use DHCP, change the scope to point all clients at the new
>> server for DNS (and for WINS, if you use that).
>>
>>> When I demote old DC will it be recognized as member server?
>>
>> Yes.
>>
>>> When I promote new DC replication will occur. Does that mean AD
>>> etc.... now lives on the OLD and New DC?
>>
>> Yes.
>>
>>
>>> Can someone clarify the sequence of steps to make this happen?
>>
>> Hope the above helps.

Why is it, when asked about a single server upgrade, nobody ever says leave
the old one in place for AD fault tolerance as recommended by Microsoft?

You should leave the old DC in place.

Joshua Bolton <(E-Mail Removed)> wrote:
> Why is it, when asked about a single server upgrade, nobody ever says
> leave the old one in place for AD fault tolerance as recommended by
> Microsoft?
>
> You should leave the old DC in place.

Sure. But if he has other needs for the old server, then this may not be
possible. Yes, it's good to have more than one DC, but how many small
offices can actually apply all the 'best practice' config recommendations?
Precious few. ;-)