transfer host name different machine in AD2003

Posted on 2009-02-12
Last Modified: 2012-05-06
2003/XP domain in effect.

I want to replace a computer, but keep using the current machine name.  Should I join the new computer to the domain, with hostname of NewComputer, rename the old computer from KeepName to OldComputer, then rename the new computer KeepName?  Will AD be OK with this?  Gotchas?

Please cite URL references or provide explaination, to receive points.  TIA.
Question by:pcrequest
    LVL 9

    Expert Comment

    The steps would be
    1) disjoin old machine from domain (Check AD to make sure it has been deleted and delete manually if not)
    2) rename old machine to  newname
    3) rejoin old machine with newname
    4) join new machine with oldname

    The first will remove the name from the AD, then you readd the machine with a new name that will not conflict, then the new machine can be added with the existing name, since it is no longer in the AD
    LVL 57

    Expert Comment

    by:Mike Kline
    You shouldn't need to disjoin a machine to rename it.   That just add an extra step.
    LVL 30

    Accepted Solution

    If both machines are going to be domain-joined at the same time, then obviously they need to have different names, so call the new one "COMPUTER-NEW" or whatever. Once you have decommissioned the old computer, just rename the new one to the old name.

    If you are not using dynamic name resolution such as WINS or dynamic DNS (I can't imagine you wouldn't be, but just in case), be sure to update any relevant DNS/WINS records if the IP address of the new machine.
    LVL 1

    Author Comment

    laura, in your scenerio I fear the old computer account in AD would interfere with renaming the new computer with the old name.  The old computer will remain on the network for a while FYI.  Yes, using WS2003 dynamic DNS updates for name services.
    mkline, are you agreeing with my plan in the original post?
    LVL 57

    Assisted Solution

    by:Mike Kline
    I think with Laura's plan when she says decommison that would mean the old machine would not exist anymore.
    Since you need them both up then yes your plan is fine.
    When you make the change to the oldcomputer name give it time to replicate.

    Featured Post

    How to run any project with ease

    Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
    - Combine task lists, docs, spreadsheets, and chat in one
    - View and edit from mobile/offline
    - Cut down on emails

    Join & Write a Comment

    Suggested Solutions

    One of the major disadvantages of still running XP in production is its lack of Internet Explorer Favourites directory redirection. If your users frequently roam between computers, the usual workaround is to enable Roaming Profiles to have the favou…
    As network administrators; we know how hard it is to track user’s login/logout using security event log (BTW it is harder now in windows 2008 because user name is always “N/A” in the grid), and most of us either get 3rd party tools, or just make our…
    This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
    This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

    734 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    23 Experts available now in Live!

    Get 1:1 Help Now