Sign in
 
HomeWindows Server 2012Windows Server 2008 R2Windows Server 2003LibraryForums
Windows Server TechCenter >
> 
> 
Hardware upgrade/replacement for W2K3 server - steps to follow?

已答覆 Hardware upgrade/replacement for W2K3 server - steps to follow?

  • Thursday, April 26, 2012 5:57 PM
     
     
    Sign In to Vote
    0

    Good day.

    I was asked by a family friend to assist them with doing a server move of a W2K3 server whose hardware is close to failure, and needs to be transferred over to newer hardware. I didn't think it would be that complicated, however, it became a lot more complex than I had anticipated. This is a same OS replacement, not an OS upgrade as well (he doesn't want to go to 2008, for instance..)

    Issues/What is Configured

    1. He doesn't have another license key for W2K3 - I assumed that since he was doing a whole hardware replacement (and the other hardware is going to be thrown out/hard drives destroyed) that he would be able to reuse the same key. Is this the case?

    2. He is using Terminal Services for several rooms in the same location - based on what I read for Terminal Services cal's, I should be able to move these over to the new server.

    3. DNS/DHCP is being used on the current server.

    4. User/Group information and files exist on the current system. These will need to be copied over to the new server.


    The main question is, what steps do I need to take to recreate the server on the new hardware? My plan, such as it was, was as follows, based on this:

    How to replace single domain controller in domain with a single domain controller

    There was another document, which used to be available at this link here, however, I am now unable to find it.

    1. Install W2K3 on the new hardware, so all the correct drivers/etc. are configured and running properly (give server a different hostname than the original, with static IP). Add the server as a member of the current domain).

    2. Patch system to current level of patches (as this is 2003, I imagine it may be a little backlevel from 2008).

    3.  Verify the new, replacement server is resolvable via DNS (which is still on the original system).

    4. Backup the system state of the original system  link here

    5. Promote the new server to be a domain controller using 'dcpromo /adv' link here and restore from the backup made in #4.

    6. Promote the new Domain Controller to be "Global Catalog" and reboot the server (link here)

    7. Move FSMO rules to the new Domain Controller (link here)

    8. Migrate DNS services to the new DC link here

    9. Verify DNS requests are going to the new system.

    10. Disable/Turn off DNS on the original system.

    11. Migrate DHCP services to the new DC, and keep leases link here

    12. Migrate Terminal Services over to the new DC (from thread here)

    13. Verify Terminal Services are working correctly.

    14. Disable Terminal services on original system.

    15. At this point, once I verify that everything is working (Terminal Services, DNS, DHCP) off the new server, I can demote original system from being a domain controller (link here)

    Is this plan valid? Am I missing any large steps or anything that is a 'gotcha'? :)

    As you can tell, I'm not exactly well versed in Win2k3 - I'm more a Linux/UNIX guy when it comes to servers. Most of the PC's at home are Windows, though. /grin

     

All Replies

  • Friday, April 27, 2012 1:54 AM
     
     Answered
    Sign In to Vote
    1

    That all looks pretty good though you should be able to skip the system state backup/restore as it's not necessary.

     If the original box shipped with server 2003 then it is OEM product and the license likely dies with the hardware.

     

     

     

    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

     
  • Friday, April 27, 2012 3:59 AM
     
     
    Sign In to Vote
    0

    I believe the Win2k3 license was purchased separately and was not an OEM copy. I'll verify.

     
  • Friday, April 27, 2012 8:06 AM
    Moderator
     
     Answered
    Sign In to Vote
    0

    Hi,

    It seems that you would like to upgrade the Windows Server 2003 to Windows Server 2008.

    Could you please let me know whether the domain name on Windows Server 2008 it the same as on Windows Server 2003?

    If above is true, there is another link for your reference:

    Title: Active Directory: Active Directory Upgrade - High Level Steps (en-US)
    URL: http://social.technet.microsoft.com/wiki/contents/articles/2903.active-directory-active-directory-upgrade-high-level-steps-en-us.aspx

    Also, for the migration of Terminal licensing server from one machine to other, these posts will help you:

    Title: Migrating your Terminal Server License Server from Windows Server 2003 to 2008
    URL: http://blogs.technet.com/b/anthoben/archive/2010/05/13/migrating-your-terminal-server-license-server-from-windows-server-2003-to-2008.aspx

    Title: Migrating a Windows Server 2003 TS License Server
    URL: http://blogs.msdn.com/b/rds/archive/2009/03/06/migrating-a-windows-server-2003-license-server.aspx

    I hope the information provided above is helpful to you.

    Regards,
    James

    James Xiong

    TechNet Community Support

     
  • Wednesday, May 02, 2012 9:15 AM
    Moderator
     
     
    Sign In to Vote
    0

    Hi,

    Any Update?

    James

    James Xiong

    TechNet Community Support

     
  • Tuesday, May 22, 2012 4:57 AM
     
     
    Sign In to Vote
    0

    So far, not much - my client had to purchase another W2K3 server license (as the OEM license which is currently being used will go poof under new hardware) - until that is received, I can't execute the plan. :)

    However, I will test first running under VMWare's ESX 4.1 after P2V'ing the server, see how it works first.

    The only change, is that it appears it's not going to be a full copy - the old server will remain as a Terminal Server only, but the remaining services (DNS, DHCP, Fileserver, etc) will move to the new server, which will also become the new primary domain controller.

    Points awarded!