Replace AD DC and use same UNC name

[Matt Bracken]

I am thinking I heard somewhere that you can not replace an avtive directory
domain controller with a completely new machine and use the same UNC name.
Is this true?
We are using too many batch files that reference the old DC by name instead
of using %LOGONSERVER%
Do I just transfer the FSMO roles and Global Catalog to a different DC and
remove the domain controller named JSTDC with dcpromo, then setup a new DC
named JSTDC and add it using dcpromo?

 

[Oli Restorick [MVP]]

That's exactly how I'd do it.

I would leave things to settle for a while after transferring the FSMOs and
making another server a GC and verify that the changes have happened
properly.

Oli

 

[ptwilliams]

This may help:
-- http://www.msresource.net/kb/replaceSingleDC.html


--

Paul Williams
_________________________________________
http://www.msresource.net


Join us in our new forums!
http://forums.msresource.net
_________________________________________


I am thinking I heard somewhere that you can not replace an avtive directory
domain controller with a completely new machine and use the same UNC name.
Is this true?
We are using too many batch files that reference the old DC by name instead
of using %LOGONSERVER%
Do I just transfer the FSMO roles and Global Catalog to a different DC and
remove the domain controller named JSTDC with dcpromo, then setup a new DC
named JSTDC and add it using dcpromo?

 

[Cary Shultz [A.D. MVP]]

Matt,

Just to clarify something: a computer account object does not have a UNC
name. The UNC name is the Universal Naming Convention, which is in the
format of \\servername\sharename. This is typically used when referring to
a shared resource ( such as a shared folder ) and you do not want to / can
not reference a mapped network drive ( so, you would use \\server01\share003
instead of f:\share003 ). I think what you meant is the DN: ( distinguished
name ) or the CN: (common name ). I would stick with the term 'computer
name', though.

HTH,

Cary