Home > ConfigMgr 2007 > SMS to SCCM Side by Side

SMS to SCCM Side by Side

I wanted to put together a Blog that will help you with transitioning from SMS2003 one an older server to SCCM2007 on a new server while still maintaining your custom collections and packages. I hope you find this helpful.

Background: Single SMS 2003 site with no child sites. SQL 2005 with SP2 on a single system.

Goal: to move to SCCM 2007 SP2 R3 on new hardware, retain custom groups, packages and reporting.

  1. You will need to install SCCM 2007 in a Primary Site, configure all site systems and settings (except the site boundaries). As a best practice give this a new site code.


  2. Once your new SCCM 2007 server is installed, attach the SMS 2003 site as a child site to SCCM 2007.


  3. Create a standard sender address in both directions


    SCCM2007 Server

    SMS2003 Server

    Add the SMS2003 Server to the local group SMS_SitetoSiteConnection_(sitename) group

    Do the same for the SCCM2007 server on the SMS 2003 local group

    On the SMS 2003 Server configure the parent Site

    The Site now appears as a child site in SCCM

  4. Use an existing client installation method at the sms 2003 site to upgrade the client to SCCM 2007 and assign it to the new site.


    I create a package and point it to the client installation of the new SCCM2007 Server

  5. Once all clients have been upgraded and reassigned, disable all discovery and client installation methods at the SMS 2003 site.


    (Do this for all Discovery Methods you wish to discover)

  6. If your SMS 2003 site has boundaries, you will need to remove them as well as the roaming boundaries from the SMS 2003 site. Make a note of these as you will need them for the next step.


  7. Add the boundaries you just removed from the SMS 2003 site to the SCCM 2007 site.


  8. If the SMS 2003 site is publishing site information to AD DS you will need to disable this.


  9. If the SMS 2003 site system has been registered with WINS you will need to uninstall the site systems that have been published to wins and remove the wins registration from the sms 2003 site systems


  10. Do you need to migrate custom collections or software distribution objects to the new SCCM 2007 site? If so upgrade the SMS 2003 site to configuration manager using the in-place upgrade method.


    Since I had some collections and packages I wanted to migrate, I had to upgrade my existing SMS2003 to SCCM.

    1. Detach the upgraded site from the hierachy and attach the new 2007 as a child site of it.

      Note (Upgraded site=SMS2003 that you just upgraded and the New 2007 is the SCCM2007 that you first implimented)

      (on the server you just upgraded change this setting to Central Site)

      (on the original sccm server, change to Report to Parent Site)

    2. Allow the custom collections and software distribution objects to replicate down to the new site.

      Go back to your New SCCM server and expand collections as well as your software distribution. You should notice a padlock next to the collections and the software packages. This will show that the sites are communicating.

      Let the replication complete. In my lab scenario I let it complete over lunch. In a larger environment it will take a little longer.

    3. Distribute packages to the distribution points on the new site and remove references to distributon points on the old site.


    4. Detach the upgraded site from the hierachy and reconfigure parent site settings if necessary.
    5. Decomission or reattach the orginal site as required by your upgrade plans.


  11. The upgrade from SMS to SCCM is now complete.


I hope this blog has helped.

Kind Regards,


Categories: ConfigMgr 2007
  1. November 29, 1999 at 7:00 pm

    Nice write up! Its really quite pathetic how unorganized technet is on SCCM.

  2. May 20, 2011 at 1:46 pm

    Thank you for this write. Why can’t Microsoft provide something like this on Technet? SCCM as a product is great but the documentation is awful.

  3. Bay
    November 1, 2011 at 10:22 pm

    Hi…I am new to the world of SCCM, but am really interested in learning more. My site currently has SCCM 2003 R2 installed on a Windows 2003 Server 32-bit(we will call this site OLD). My site has installed SCCM 2007 Sp2 on a Windows 2008 Server 32-bit (will call this NEW). They want a fresh install of SCCM on the 2008 server. SCCM was installed and linked with SQL DB on a remote server. My question would be how to procede from hear. Can I migrate the SCCM clients on the OLD server to the NEW server? What would be the best way to configure. Also, will I need to delete the boundaries already configured on the OLD server and reconfigure on the NEW server? I have tried to read all the information that I can find on the internet, but that can be overwhelming. Any advise or assistance would be greatly appreciated. I have read some post on performing a migration from SMS 2003 to SCCM 2007. However, is there any information on migrating SCCM 2007 R2 on a Windows 2003 box to SCCM 2007 Sp2 (not going to R2) on a new Windows 2008 server?

    • November 24, 2011 at 12:32 am


      I have performed many of SCCM 2007 to SCCM 2007 migrations before. I have a question for you. Are there packages that need to be migrated as well? Here are the basic steps…

      1. Join the new site to the existing site
      2. wait for the new site to see the parent site… you should be able to see the packages with the padlock.
      3. copy the source files for the package to the new server (if they were local)
      4. Add the new distribution point to these packages
      5. set discovery settings as they were in the primary site for the new site.
      5. remove the discovery settings from the primary site (original server)
      6. setup the boundaries on the new server
      7. remove the boundaries from the original server
      8. Remove the original DP from the packages.
      8. stop pointing the new server to the original server
      9. run a discovery on the new server.
      10. use a tool such as SCCM right click tools and you can point the clients to the new site code.
      11. When you are ready, the old site can be taken down.

      The descripting above is very simplified, but you should get the jist of it. The steps too are for a very simple environment.



  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: