AD Win 2K3 server replacement

Discussion in 'Server Migration' started by Jeff P, Jan 18, 2006.

  1. Jeff P

    Jeff P Guest

    I have a Windows Server 2003 AD server which needs to be replaced. I have
    been researching the best way to do this. Ideally I would like to Ghost the
    server and restore the image onto the new server. But the old server is and
    IDE and the new server is a dual SCSI with a mirror. Is that way feasible?
    Or should I add the new server to the domain, move the roles to the new
    server, remove the old server and then rename the new server and IP to the
    old server?

    I really want to keep the same name and IP address.

    Any help would be greatly appreciated.

    Jeff
     
    Jeff P, Jan 18, 2006
    #1
    1. Advertisements

  2. Hi, Jeff...

    I'd go with the last option. Keep in mind though, that you cannot reuse the
    old computername if you make the new server a domain controller; this will
    create problems in your Active Directory. I dont know your environment, hence
    I dont know your reasons for wanting to retain the computername name (mayby
    login script, drive mappings and such); consider changing these depencies
    instead and dont rename the new server once it is a domain controller. If
    possible you could later consider using DNS aliases or WINS records to keep
    the old "server" name alive for a short period of time.

    Regards,
    Soren Granfeldt
     
    Soren Granfeldt, Jan 18, 2006
    #2
    1. Advertisements

  3. Jeff P

    lk Guest

    Hi Jeff,
    I've done exactly this with Trueimage server 8 version, but as
    always, ymmv..

    1. Backup current server with Ghost/Truimage/Ultrabac, whatever you have
    on hand to assure you can restore the old server as it was

    2. Get an old PC, and use this as a test client. Add the computer
    account to the domain, and test logging in to the domain on it.
    Now, unplug that from the network.
    Be sure to note what user profile is created in \documents and settings

    3. Install win2000 server on the new dual scsi mirrored server, install
    SP4. Create an ASR floppy (automated system recovery disk)

    4. Remove the IDE drive from the old server, put in an external USB
    case, and plug in to the new server.

    5. Install Truimage server 8, reboot. Login and clone the external
    drive to the internal Dual scsi. Alternatively you can create a
    bootable CD with Truimage to do the imaging.

    6. When the server comes up, it may blue screen due to chipset/hardware
    issues. YOu can then do an ASR repair install using the floppy.

    good luck
     
    lk, Jan 19, 2006
    #3
  4. Jeff P

    lk Guest

    Forgot to add, that once your "cloned" new server is back up,
    put it on an isolated LAN, and connect your temp PC client machine.
    See if you can login. If so, and if the profile you used originally
    is recognized, you should be all set

    LK
     
    lk, Jan 19, 2006
    #4
  5. Jeff P

    lk Guest

    Forgot to add this: once your "cloned" new server is back up,
    put it on an isolated LAN, and connect your temp PC client machine.
    See if you can login. If so, and if the profile you used originally
    is recognized, you should be all set

    LK
     
    lk, Jan 19, 2006
    #5
  6. Jeff P

    Jeff P Guest

    My concern about this method is having the new DC with a new name. The DC is
    a DHCP, and DNS server. Doesn't that mess stuff up if the server is named
    differently?
     
    Jeff P, Jan 19, 2006
    #6
    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.