none
Need Procedure on moving primary site to new hardware & OS.

    Question

  • Hi guys,
      got new hardware in for my primary site.

    What procedure do I need to follow to move my current primary site across to new hardware?

    • Moved by Torsten [MVP]MVP Thursday, December 10, 2009 8:09 AM backup/restore topic (From:Configuration Manager Setup/Deployment)
    Wednesday, December 09, 2009 4:21 PM

Answers

  • Hi,

    1) Configure the new site as a child site and let packages, collections etc replicate down
    2) Break the parent/child relationship
    3) Configure the new site as parent site and let the data (inventory) flow up
    4) Remove the boundaries from the old site and assign them to the new site
    5) Run this script as a package on the old site (it will work even after boundaries have been removed.
    6) All clients are now assigned to the new site

    'replace with your Site Code
    sSiteCode = "NewSitecode"
    sMachine = "."
    set oCCMNamespace = GetObject("winmgmts://" & sMachine & "/root/ccm")
    Set oInstance = oCCMNamespace.Get("SMS_Client")
    set oParams = oInstance.Methods_("SetAssignedSite").inParameters.SpawnInstance_()
    oParams.sSiteCode = sSiteCode
    oCCMNamespace.ExecMethod "SMS_Client", "SetAssignedSite", oParams


    Just make sure you don't have any packages that will rerun even if they installed successfully. If so then they will rerun when clients are assigned to the new site.
    Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
    Wednesday, December 09, 2009 5:52 PM
  • Moving to new hardware can be done using backup & recovery.
    http://technet.microsoft.com/en-us/library/bb632545.aspx

    "Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm
    Wednesday, December 09, 2009 10:14 PM

All replies

  • Hi,

    1) Configure the new site as a child site and let packages, collections etc replicate down
    2) Break the parent/child relationship
    3) Configure the new site as parent site and let the data (inventory) flow up
    4) Remove the boundaries from the old site and assign them to the new site
    5) Run this script as a package on the old site (it will work even after boundaries have been removed.
    6) All clients are now assigned to the new site

    'replace with your Site Code
    sSiteCode = "NewSitecode"
    sMachine = "."
    set oCCMNamespace = GetObject("winmgmts://" & sMachine & "/root/ccm")
    Set oInstance = oCCMNamespace.Get("SMS_Client")
    set oParams = oInstance.Methods_("SetAssignedSite").inParameters.SpawnInstance_()
    oParams.sSiteCode = sSiteCode
    oCCMNamespace.ExecMethod "SMS_Client", "SetAssignedSite", oParams


    Just make sure you don't have any packages that will rerun even if they installed successfully. If so then they will rerun when clients are assigned to the new site.
    Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
    Wednesday, December 09, 2009 5:52 PM
  • Thanks Kent,
        Is there away of doing it but keeping the same site code?

    how do you set as a parent site? If I recall isnt this an option on the install?
    Wednesday, December 09, 2009 8:55 PM
  • Moving to new hardware can be done using backup & recovery.
    http://technet.microsoft.com/en-us/library/bb632545.aspx

    "Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm
    Wednesday, December 09, 2009 10:14 PM
  • Hi,

    If you want to keep the same site code you need to do as suggested by Kim (backup/restore). To create a parent child relationship check - http://technet.microsoft.com/en-us/library/bb632349.aspx
    Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products
    Thursday, December 10, 2009 6:54 AM
  • Please have a look at similar threads in the Backup&Recovery subforum. That was already covered.
    Thursday, December 10, 2009 8:09 AM
  • From what ive read a backup & restore you can only do on the same drive configuration. Mine will be different so what are my options?

    Old Server C:(OS), E:(SQL,SCCM)
    New Server C:(OS), D:(SQL), E:(SCCM,1E)



    Can I setup the new server with same site code etc & not bother restoring the backup  & start from fresh with data etc? I have two secondary sites below my primary which will remain.

    Saturday, December 12, 2009 12:54 AM
  • Hi Kent

    I'm going through this process at the moment and was wondering you could answer a few questions I have. I'll number my questions so they reflect which part of your process it is for.

    1)
    Is there a way to see when replication has finished?

    3)
    Is there a way to see when replication has finished?

    What happens to the packages and collections on the old site when the new one becomes the primary? Do you end up with two copies of each, or does SCCM know they are the same and the collections just become locked on the original site?

    5)
    Just curious but can you use a GPO to assign the clients to the new site instead of using a script?

    Thanks!
    Tuesday, January 19, 2010 3:26 AM
    • Proposed as answer by legionx Friday, January 22, 2010 5:46 AM
    Tuesday, January 19, 2010 7:16 AM
  • legionx,

    1.  Kent told me it can take a few days to replivcate so I created the child/parent relationship on a firady & then dropped the relationship on the monday after checking some of the packages etc. if I recall kent said there was a log you can check but I didnt bother & cant recall what log it was.

     
    5. I have got a GPO running for site assignment ive used to move clients over to my new site.

    This ADM GPO files can be found in the folder TOOLS\ConfigMgrADMTemplates on the Configuration Manager 2007 installation media

    you need CONFIGMGR2007ASSIGNMENT.ADM
    Tuesday, January 19, 2010 11:38 AM
  • Thanks Torsten and chiner_68
    Friday, January 22, 2010 5:47 AM
  • Hi, I'v got a couple of questions. 1. What type of script is this? 2. Do you create the package for the script from the old site? Thanks
    Friday, January 29, 2010 5:22 PM
  • Obi San,
      i didnt actually use Kents script for changing the clients to point to the new site code. I used the SCCM ADM template for assigning the site code & this pointed my clients to the new site.
    Saturday, January 30, 2010 8:16 PM
  • Hi,

    1) Configure the new site as a child site and let packages, collections etc replicate down
    2) Break the parent/child relationship
    3) Configure the new site as parent site and let the data (inventory) flow up
    4) Remove the boundaries from the old site and assign them to the new site
    5) Run this script as a package on the old site (it will work even after boundaries have been removed.
    6) All clients are now assigned to the new site

    'replace with your Site Code
    sSiteCode = "NewSitecode"
    sMachine = "."
    set oCCMNamespace = GetObject("winmgmts://" & sMachine & "/root/ccm")
    Set oInstance = oCCMNamespace.Get("SMS_Client")
    set oParams = oInstance.Methods_("SetAssignedSite").inParameters.SpawnInstance_()
    oParams.sSiteCode = sSiteCode
    oCCMNamespace.ExecMethod "SMS_Client", "SetAssignedSite", oParams


    Just make sure you don't have any packages that will rerun even if they installed successfully. If so then they will rerun when clients are assigned to the new site.
    Kent Agerlund | http://scug.dk/members/Agerlund/default.aspx | The Danish community for System Center products

    Hi Kent - I have one question regarding this.   Does this re-register/rename all the package IDs  with the new site name ?  If you migrate the existing packages from the 'parent' server then they will maintain the package IDs from that server and remain locked on the new server surely ?

     

    thanks

    Nick B


    Solutions Architect
    Friday, July 02, 2010 2:09 PM
  • Hi Nick

    It is true, I have done one of these migrations and they maintain their old package IDs and unlock. It can take a while depending on your site performance, and I've found that if you have any erroneous jobs pending e.g. packages that cannot distribute to DPs because their package source does not exist anymore, it can mess with this process because SMS waits for these jobs to timeout before doing anything further with the objexts. So my tip, make sure the logs are clean before attempting this. Also when migrating reports be aware that an export import breaks report links, they don't come across, so don't bulk export import build-in reports because you will break links in everything. I did this, but it is simple enough to write a script to fix links by referencing a working site.

    Cheers

    Sunday, July 04, 2010 12:06 PM
  • Hi Kent,

    I'm executing from my machine indicating sMachine = "RemoteMachineName" but it is not working.

    The logs show that SCCM Client com not get SLP from Wins, but I'm not using Wins, but DNS.

    Do you have any ideia?

     

    Please, Could you answer to pierre.satiro@hsbc.com.br ?

     

    Tks,

    Pierre

    Tuesday, March 22, 2011 7:42 PM
  • Is the AD schema extended? Is the siteserver able to publish to AD?


    Torsten Meringer | http://www.mssccmfaq.de
    Wednesday, March 23, 2011 8:18 AM
  • Hello Kent

    Regarding 1) above: do you also add the packages to the Distribution Point on the Child Site before you Break the parent/Child? Or just let the packages replicate down, and later on the child site (when the relationship is broken), add the package to the Distribution point on the new site.

    Thursday, February 16, 2012 8:35 AM
  • I let the packages replicate, afterwards I update the package source to a new location(if needed) using this freeware tool - http://blog.coretech.dk/jgs/coretech-package-source-changer-0-3-0-0/

    Kent Agerlund | My blogs: blog.coretech.dk/kea and SCUG.dk/ | Twitter: @Agerlund | Linkedin: Kent Agerlund

    Thursday, February 16, 2012 10:45 AM
  • I will break the parent/child, and then when logged on to the "Child" site, add the files to the local distribution point.  You gave a demo of that tool on the NIC2012, so I will be using it when needed to change sources when Migrating SCCM 2007-2012.

    Thank you again :)

    Thursday, February 16, 2012 8:32 PM
  • Hi kent

    When do you actually breake the parent/child the second time? After step 6 og 3?

    Thanks.




    • Edited by Jean André Thursday, March 08, 2012 11:02 AM
    Thursday, March 08, 2012 9:14 AM