Windows Vista Forums

Moving from Server 2003 to Server 2008 R2 64 bit

  1. #1


    jdecker Guest

    Moving from Server 2003 to Server 2008 R2 64 bit


    We are in the process of retiring our 2003 Windows Server. It is
    currently running DNS, AD, Certificate Authority, DHCP, and Exchange
    2003.

    Our new server is a Virtual 2008 R2 64 bit. It is currently on the
    network but is only hosting NPS (IAS in 2003) Role.

    I found some Microsoft articles that lay out the process for migration,
    but it says to migrate the ip address and server name to the new server.
    However one of the problems I see is that we do not want to move the
    server name to the new machine. Unfortunately the network was setup by
    someone else and he used names of rock bands for the servers. We really
    want to get away from this and use names that better describe what the
    server is for. So what would you suggest about migrating without
    changing the destination servers name?

    Another question is will demoting the 2003 server while it is hosting
    Exchange 2003 cause a problem? We plan to move Exchange to a stand
    alone server in the future, and would like to upgrade to Exchange 2007
    or Exchange 2010. However I am not sure when the new server will be
    setup, so there could be a time period where the 2003 Server is still
    running after we move the DC responsibilities to the new server.

    If anyone has been through this process I would like to know how your
    process went and any tips you can provide.


    --
    jdecker
    ------------------------------------------------------------------------
    jdecker's Profile: http://forums.techarena.in/members/62076.htm
    View this thread: http://forums.techarena.in/windows-s...lp/1254556.htm

    http://forums.techarena.in


      My System SpecsSystem Spec

  2. #2


    Meinolf Weber [MVP-DS] Guest

    Re: Moving from Server 2003 to Server 2008 R2 64 bit

    Hello jdecker,

    No need to take over the names, the article is built from MS because lots
    of people like to keep servernames. For Exchange/CA see at the end. You can
    follow this way for AD itself.

    !!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOUR DATA/MACHINE!!!

    - On the old server open DNS management console and check that you are running
    Active directory integrated zone (easier for replication, if you have more
    then one DNS server)

    - run replmon from the run line or repadmin /showrepl(only if more then one
    DC exist), dcdiag and netdiag from the command prompt on the old machine
    to check for errors, if you have some post the complete output from the command
    here or solve them first. For this tools you have to install the support\tools\suptools.msi
    from the 2003 installation disk.

    - run adprep /forestprep and adprep /domainprep and adprep /rodcprep from
    the 2008 installation disk against the 2003 schema master(forestprep) / infrastructure
    master(domainprep/rodcprep), with an account that is member of the Schema/Enterprise/Domain
    admins, to upgrade the schema to the new version (44) or 2008 R2 (47)

    - you can check the schema version with "schupgr" or "dsquery * cn=schema,cn=configuration,dc=domainname,dc=local
    -scope base -attr objectVersion" without the quotes in a command prompt

    - Install the new machine as a member server in your existing domain

    - configure a fixed ip and set the preferred DNS server to the old DNS server
    only, think about disabling IPv6 if you are not using it, some known problems
    exist with it. Follow (http://blogs.dirteam.com/blogs/paulb...dows-2008.aspx)
    to disable it

    - run dcpromo and follow the wizard to add the 2008 server to an existing
    domain, make it also Global catalog and DNS server.

    - for DNS give the server time for replication, at least 15 minutes. Because
    you use Active directory integrated zones it will automatically replicate
    the zones to the new server. Open DNS management console to check that they
    appear

    - if the new machine is domain controller and DNS server run again replmon,
    dcdiag and netdiag (copy the netdiag from the 2003 to 2008, will work) on
    both domain controllers

    - Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801
    applies also for 2008), FSMO should always be on the newest OS DC

    - you can see in the event viewer (Directory service) that the roles are
    transferred, also give it some time

    - reconfigure the DNS configuration on your NIC of the 2008 server, preferred
    DNS itself, secondary the old one

    - if you use DHCP do not forget to reconfigure the scope settings to point
    to the new installed DNS server

    - if needed export and import of DHCP database for 2008 choose "netshell
    dhcp backup" and "netshell dhcp restore" command (http://technet.microsoft.com/en-us/l.../cc772372.aspx)



    Demoting the old DC

    - reconfigure your clients/servers that they not longer point to the old
    DC/DNS server on the NIC

    - to be sure that everything runs fine, disconnect the old DC from the network
    and check with clients and servers the connectivity, logon and also with
    one client a restart to see that everything is ok

    - then run dcpromo to demote the old DC, if it works fine the machine will
    move from the DC's OU to the computers container, where you can delete it
    by hand. Can be that you got an error during demoting at the beginning, then
    uncheck the Global catalog on that DC and try again

    - check the DNS management console, that all entries from the machine are
    disappeared or delete them by hand if the machine is off the network for ever

    - also you have to start AD sites and services and delete the old servername
    under the site, this will not be done during demotion


    Exchange:
    To demote a server with exchange installed, you have to first uninstall exchange
    to get it removed correct. It should be possible to demote it with exchange
    installed but not recommended.

    CA:
    http://www.microsoft.com/downloads/d...displaylang=en

    http://technet.microsoft.com/en-us/l...66(WS.10).aspx

    http://technet.microsoft.com/en-us/l...88(WS.10).aspx


    Best regards

    Meinolf Weber
    Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    no rights.
    ** Please do NOT email, only reply to Newsgroups
    ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


    > We are in the process of retiring our 2003 Windows Server. It is
    > currently running DNS, AD, Certificate Authority, DHCP, and Exchange
    > 2003.
    >
    > Our new server is a Virtual 2008 R2 64 bit. It is currently on the
    > network but is only hosting NPS (IAS in 2003) Role.
    >
    > I found some Microsoft articles that lay out the process for
    > migration, but it says to migrate the ip address and server name to
    > the new server. However one of the problems I see is that we do not
    > want to move the server name to the new machine. Unfortunately the
    > network was setup by someone else and he used names of rock bands for
    > the servers. We really want to get away from this and use names that
    > better describe what the server is for. So what would you suggest
    > about migrating without changing the destination servers name?
    >
    > Another question is will demoting the 2003 server while it is hosting
    > Exchange 2003 cause a problem? We plan to move Exchange to a stand
    > alone server in the future, and would like to upgrade to Exchange 2007
    > or Exchange 2010. However I am not sure when the new server will be
    > setup, so there could be a time period where the 2003 Server is still
    > running after we move the DC responsibilities to the new server.
    >
    > If anyone has been through this process I would like to know how your
    > process went and any tips you can provide.
    >
    > http://forums.techarena.in
    >


      My System SpecsSystem Spec

  3. #3


    jdecker Guest

    Re: Moving from Server 2003 to Server 2008 R2 64 bit


    Thanks for the reply, I will read all the information and digest it
    before going any further.

    One further question. Would it be possible to run the network with
    both servers as DC's, and then when we have all programs converted just
    shutdown and remove the old server?


    --
    jdecker
    ------------------------------------------------------------------------
    jdecker's Profile: http://forums.techarena.in/members/62076.htm
    View this thread: http://forums.techarena.in/windows-s...lp/1254556.htm

    http://forums.techarena.in


      My System SpecsSystem Spec

  4. #4


    Meinolf Weber [MVP-DS] Guest

    Re: Moving from Server 2003 to Server 2008 R2 64 bit

    Hello jdecker,

    You can run as much DCs as you like together. At least you should have 2
    per domain, also DNS server and Global catalog.

    Do NOT shutdown a DC to remove it from the domain, it MUST be demoted to
    get it out of the AD database correct. See the end of my article about demoting.

    Best regards

    Meinolf Weber
    Disclaimer: This posting is provided "AS IS" with no warranties, and confers
    no rights.
    ** Please do NOT email, only reply to Newsgroups
    ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


    > Thanks for the reply, I will read all the information and digest it
    > before going any further.
    >
    > One further question. Would it be possible to run the network with
    > both servers as DC's, and then when we have all programs converted
    > just shutdown and remove the old server?
    >
    > http://forums.techarena.in
    >


      My System SpecsSystem Spec


Moving from Server 2003 to Server 2008 R2 64 bit
Similar Threads
Thread Forum
Server 2003 to Server 2008 R2 Server General
Re: Server 2003 Upgrade to Server 2008? Server General
SBS 2008 and Windows Server 2003/Terminal Server SBS Server
Discussion Group for Server 2003 and Server 2008 Server General
Virtual Server 2005 r2 - moving VPC server to server - blue screen Virtual Server