migrate from windows server 2003 to windows server 2008R2

Discussion in 'Windows Server' started by weedfrog, Oct 23, 2009.

  1. weedfrog

    weedfrog Guest

    Do you know of a white paper or article that discribes the best process to
    migrate from windows server 2003 to windows server 2008 R2? I am planning
    on replacing my existing server hardware running windows server 2003 and
    purchasing a new server running windows server 2008. How do you migrate my
    old server settings to a new server 2008 R2? Or is it easier to just start
    over from scratch with the new server 2008 R2? I only have 12 or so users and
    not a lot of stuff on my current windows server 2003 that is any good.
    weedfrog, Oct 23, 2009
    1. Advertisements

  2. Hello weedfrog,

    Is this a domain controller or workgroup server? Which server roles and applications
    are installed on it?

    Best regards

    Meinolf Weber
    Meinolf Weber [MVP-DS], Oct 23, 2009
    1. Advertisements

  3. weedfrog

    weedfrog Guest

    It is a domain controller. Just a basic server 2003, I think DNS server is
    but not correctly configured anyway. As far as applications Quickbooks is
    the main
    application server is used for.
    weedfrog, Oct 23, 2009
  4. weedfrog

    weedfrog Guest

    I did find some of your other posts to similiar question in MIGRATION section.
    Looks like a lot of steps to complete migration. If I just start from
    scratch, this
    process might be a lot easier. And if I do start from scratch and
    I would probably use the exact domain name on my new 2008 server. Then
    would I even need to change anything on my WindowsXP client computers? I
    would setup 2008 server with the exact TCP/IP address. My active directory
    seems to be just a list of user names for each Windows XP client. I would
    then just add each user into the Active Directory (they would then be able to
    logon to the server without rejoining the domain?). Then unplug old 2003
    server and plug in new 2008 server. Any suggestions on starting from
    scratch process?
    weedfrog, Oct 23, 2009
  5. Hello weedfrog,

    See inline.

    Best regards

    Meinolf Weber

    A new installation is more complex work then upgrading to the new OS.
    Yes, they must be rejoined to the new domain, evevn if you use the same name
    it will have a complete NEW SID, which requires new creation of user accounts,
    policies, etc. Also the users will have new profiles on there local computers
    and must reconfigure everything for there settigns.
    No, see above why not.
    Meinolf Weber [MVP-DS], Oct 25, 2009
  6. Hello weedfrog,

    What is not correctly configured, please be more specific? DNS is the most
    important part that AD runs correct. So describe what kind of zones you are
    using and how you named them. Additional post an unedited ipconfig /all from
    the DC/DNS server so we can check the settings.

    Best regards

    Meinolf Weber
    Meinolf Weber [MVP-DS], Oct 25, 2009
  7. weedfrog

    weedfrog Guest


    Just want to be clear that I am not planning on UPGRADING my windows 2003
    server to windows 2008R2. I am planning on purchasing windows server 2008R2
    along with new hardware. Thus, do think in my situation it would be better
    to MIGRATE or install windows server 2008R2 from scratch? In other posts I
    have read it seems that the perfered method is to always install clean from
    scratch. Do you agree? And to you have an outline or white paper with
    steps to complete when changing from windows server 2003 to windows server
    2008R2? This is the information I am looking for. Stuff like, should I use
    the same domain name, keep the same IP addresses, and what is the process to
    unjoin/rejoin the domain for my Windows XP client PCs? Do you have this
    As far as my current DNS errors, I am getting error messages in my event log
    every day. I do not have a printout, but I get the same error messages every
    day in the event logs. Some DNS configuration issue. Thus, I am not sure I
    want to migrate my existing DNS settings to my new server 2008R2. Would you
    And I did not think that moving from windows server 2003 to windows server
    2008 would affect my windowsXP PCs local profiles. Can you explain what
    needs to be done here? I guess I am thinking I can just install my windows
    2008R2 server on new hardware, configure as a Domain Controller, then unplug
    my 2003 server and then plug in my server 2008R2. I am sure there will be
    issues doing this, would you have a checklist of things to watch out for or
    a to do list?

    weedfrog, Oct 26, 2009
  8. Hello weedfrog,

    With upgrading i meant the domain not the 2003 server.

    Rest of your questions see inline.

    Best regards

    Meinolf Weber

    Installing the new OS from scratch on the new hardware and adding it as additional
    DC to the EXISTING domain is my preferred way.
    See my next posting abvout detailed steps to add an additional DC to the
    existing domain.
    You are mixing a bit the differences between a NEW installed domain with
    the same name and keeping all information with an upgrade of the existing
    domain. When no need is to rename a domain or to combine multiple domains
    into one there is no need to start complete again with adding computers to
    the domain, creating users, GPOs etc.
    See the next posting.
    Please post the event viewer errors, use the 2paper button on the event properties
    on the right down corner and paste it into the posting. It is important BEFORE
    adding the new DC to remove DNS errors. There is no problem make the 2008
    R2 also DNS server. You should have at least 2 DC/DNS/GC per domain for failover
    and redundancy reason.
    If you add the 2008 R2 to the existing domain nothing has to be done with
    the local profiles. Will still work.
    NO, wrong way, please follow the steps in my next posting how to remove a
    DC from the domain. But keep in mind what i said about the minimum DC/DNS/GCs
    per domain.
    Meinolf Weber [MVP-DS], Oct 27, 2009
  9. Hello weedfrog,


    - 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 /showreps(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 2000 installation disk.

    - run adprep /forestprep and adprep /domainprep and adprep /domainprep /gpprep
    and adprep /rodcprep from the 2008 R2 installation disk against the 2000
    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), there exist adprep32.exe
    (32bit) and adprep.exe (64bit) on the 2008 R2 installation disk

    - 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/paulbergson/archive/2009/03/19/disabling-ipv6-on-windows-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

    - if the new machine is domain controller and DNS server run again replmon,
    dcdiag on both domain controllers. Netdiag.exe is NOT included within 2008 R2

    - Transfer, NOT seize the 5 FSMO roles to the new Domain controller (http://support.microsoft.com/kb/324801
    applies also for 2008/2008R2), 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

    Demoting the old DC(if needed)

    - 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

    Best regards

    Meinolf Weber
    Meinolf Weber [MVP-DS], Oct 27, 2009
  10. weedfrog

    sentinelace Guest

    I'm in the same boat. Did you end up doing the "swing" ? I heard there
    were some built in tools you can use?
    sentinelace, Dec 15, 2009
    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.