locked
Migrate SCCM to new server and from SP1 to SP2 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    We are looking to upgrade our SCCM server from Windows 2003 to Windows 2008 R2 and migrate the DB to a SQL 2005 64bit server (from 2005 32 bit).  We will also be going from SCCM SP1 to SP2 during the migration.  We only have one SCCM server.   I believe I have figured out the best way to do this but if somebody can doublecheck my steps, I would greatly appreciate it.  We are going to do a side-by-side upgrade (migration). Both servers are mixed mode:
     
    1. Build a new SCCM server on Windows 2008 R2 and create a new DB on the SQL server.
    2. Make the new SCCM server the central site (parent) and the current SCCM server a child
    3. Once all data flows up to the central site, break child/parent replication.
    4. Shut down current SCCM server and configure new SCCM server roles
    5. Push new SCCM client to all machines reflecting the SP2 build and new site code
     
     
    Is this the best way to do a migration?  The main questionable area is will I be able to deploy the updated SCCM client to all machines after the upgrade?  Especially because they have different site codes and service packs?
     
     
    Thanks for your help
    Tuesday, April 27, 2010 5:56 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    you can also use this methode :

    1. backup your sccm server using the sccm backup maintenance task. Also, you will need to backup all packages you have setup, including the Package source folders because it's not included on sccm backup.

    2. Rebuild the machine with Windows 2008 R2 (keep same name, domain, drive letter, ...) and all requirements of course (SQL/IIS, ...)

    3. Install ConfigMgr (keep same site code, ...) & Restore backup. To restore all package, you can use PreloadPkgOnSite.exe tool : http://www.microsoft.com/downloads/details.aspx?FamilyID=C36FCDA8-9336-4D44-9568-5530FF7635DD&displaylang=en

    Bechir Gharbi. MCSA, MCSE M+S, MCITP Server/Enterprise Administrator, MCT, MCTS Configuration Manager/Forefront (Time Zone : GMT+1)
    • Proposed as answer by John Marcum Tuesday, April 27, 2010 10:23 PM
    • Marked as answer by Robinson Zhang Thursday, April 29, 2010 5:47 AM
    Tuesday, April 27, 2010 6:28 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I wouldn't shut down the old server until all ressources were migrated. Furthermore I would create a package on the old server and reassign the clients to the new site (or a group policy). How about all the old packages, collections and other objects. They wont replicate up only down.

    Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
    Tuesday, April 27, 2010 6:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    you can also use this methode :

    1. backup your sccm server using the sccm backup maintenance task. Also, you will need to backup all packages you have setup, including the Package source folders because it's not included on sccm backup.

    2. Rebuild the machine with Windows 2008 R2 (keep same name, domain, drive letter, ...) and all requirements of course (SQL/IIS, ...)

    3. Install ConfigMgr (keep same site code, ...) & Restore backup. To restore all package, you can use PreloadPkgOnSite.exe tool : http://www.microsoft.com/downloads/details.aspx?FamilyID=C36FCDA8-9336-4D44-9568-5530FF7635DD&displaylang=en

    Bechir Gharbi. MCSA, MCSE M+S, MCITP Server/Enterprise Administrator, MCT, MCTS Configuration Manager/Forefront (Time Zone : GMT+1)
    • Proposed as answer by John Marcum Tuesday, April 27, 2010 10:23 PM
    • Marked as answer by Robinson Zhang Thursday, April 29, 2010 5:47 AM
    Tuesday, April 27, 2010 6:28 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I would do as Bechir says. As a matter fact I did do that recently. There's a good guide here, altough I did update it to fit my needs and there are a few minor misconceptions in it such as the SQL and OS version on the new server do not have to match the old server.

    http://www.myitforum.com/articles/8/view.asp?id=10834

     

     

     

    John Marcum | http://myitforum.com/cs2/blogs/jmarcum |
    Tuesday, April 27, 2010 10:25 PM