New Server Old Name, keep old server?

Discussion in 'Active Directory' started by Scott Townsend, Mar 26, 2007.

  1. We would like to add an AD DC to the domain and make it the Primary DNS,
    Print, Virus, etc Server. We have a few Existing DCs that support some of

    We'd like to keep some of the DCs as backups, Though we'd like to use the
    Server name of one of the old DCs for the new DC and still keep the Old DC

    Is there a how to On Renaming a DC?

    I was thinking if Renaming a DC isn't that big of a deal, then I was going
    to install the new DC with a new name, get all of the SW dialed in and
    functional (as far as a replacement DC to the one that I'm stealing the name
    from) and then rename the old to something else then rename the new to the
    old name.

    Make since?

    Thank you for any input....

    Scott Townsend, Mar 26, 2007
    1. Advertisements

  2. Paul Bergson [MVP-DS], Mar 26, 2007
    1. Advertisements

  3. Scott Townsend

    Herb Martin Guest

    There are NO "PDCs" in AD -- just DCs. You can give a DC most of the
    work and call it your main DC but they are largely equal.

    Generally you should be using AD Integrated DNS anyway so there won't
    even be a single master for DNS either.

    And in a single domain every DC should be a GC too.

    Yes, try to have at least two DCs all of the time.
    DCPromo to non-DC and rename then the new DC can be created with the old
    Yes, but it is tedious. You must put the domain in Win2003 Server Native
    first -- which means NO Win2000 DCs.

    BTW: Why are you retiring the DC? Seldom do DCs need to be the
    most powerful machines.
    Do it the other way around -- easier than renaming a DC.
    And if you have more than one Subnet you almost certainly need WINS
    Server(s) too.
    Herb Martin, Mar 26, 2007
  4. The Server has to be 2003 or the AD Domain has to be Native Win2003? I do
    have one Win2000 DC. I cannot demote it yet as I have a Certificate Server
    Running on it and I need to move it too.

    Thank you,
    Scott Townsend, Mar 27, 2007
  5. THank you for your reply! I appreciate it. Looks like the link the other
    poster replies with is simpler, though not sure if they meant that the
    server I'm renaming has to be Win2003 or all DCs in the Domain have to be
    Win2003. I do have one Win2000 and it has a Certificate Server on it that we
    are still using and I need to move it first before I can demote it.
    Right, though when I meant master in DHCP, you need to specify a Pri//Sec
    DNS and WINS Server for the Clients. I wanted to make the new box the
    Primary for this purpose. Yeah they are all GCs too.
    Its Sad, but I'm not really retiring it. DC1 is Win2000, It has Cert Server,
    Virus Management Console, DNS, WINS, License Server, Data I/O Server and a
    few other Rolls. I want to replace that unit. DC2 is a 'okay' machine and
    its currently the DNS, WINS, DHCP, Print server. DC2 had the name that my
    managers want to use to replace DC1. So DC2 will just be a backup DNS, WINS,
    Print server. The new DC will be DNS, WINS, DHCP, Print, Virus Management
    Console, License Server, Data /IO Server, Cert Server.

    Its all in a Name... To bad I don't get Paid overtime... )-:
    Just though it would be nice to have the time to get the new Server Dialed
    in, so when I make the name change all the clients would then be pointing to
    the new server and not see any issues. Bringing up the new server with the
    Old name would mean I have to get it all up and running and everything top
    notch before people get back to the office. Rather not pull an all nighter
    to get it all right the first time.

    Thank you again for your assistance!

    Scott Townsend, Mar 27, 2007
  6. Scott Townsend

    Herb Martin Guest

    The latter sinced this is required to advance the domain mode.

    Every DC. This is so that every DC will understand that one of their
    partners changed names and Win2000 DCs don't know about this
    And those are VERY hard to rename -- you essentially have to remove
    and rebuild the CA.
    Actually it isn't Pri/Sec but PREFERRED and ALTERNATE(s).
    In most cases each Client should have the "closest" DNS or WINS server,
    or you should split them half and half when there are two choices.

    It's ok to put one of the first every time in SOME cases, but you first
    should be to do it efficiently.
    Maybe just get some of that stuff on another machine.
    Names don't really matter except for a few cases like FILE/print SERVERS
    (and Cert Servers.)

    That whole idea of their being a "Primary Server" is really a misconception
    on your manager's part which you may be enabling.
    Herb Martin, Mar 27, 2007
  7. Thanks Paul and Herb! they are right.

    Mike Luo

    Microsoft Online Partner Support
    Get Secure! -

    When responding to posts, please "Reply to Group" via your newsreader so
    that others may learn and benefit from your issue.
    This posting is provided "AS IS" with no warranties, and confers no rights.
    Mike Luo [MSFT], Mar 27, 2007
  8. Sorry, 2003 Native Mode.

    Paul Bergson [MVP-DS], Mar 27, 2007
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.