Skip to content
Trending
Simplify Windows Devices to Run Only the Required Applications using Intune Enhance macOS Compliance with Custom Security and Compliance Checks to Improve Device Security using Microsoft Intune Manage Samsung Galaxy Firmware Versions to Improve Security and Compliance using Microsoft Intune MS Intune Adds Windows Registry Data Collection to Device Inventory for Single Values All Key Values and Subkeys Updated Windows Device Sync Experience Enhances Per-Device Troubleshooting Configure Windows Sandbox vGPU Policy using Intune for Better Graphics Performance or Reduced Attack Surface Simplify Windows Devices to Run Only the Required Applications using Intune Enhance macOS Compliance with Custom Security and Compliance Checks to Improve Device Security using Microsoft Intune Manage Samsung Galaxy Firmware Versions to Improve Security and Compliance using Microsoft Intune MS Intune Adds Windows Registry Data Collection to Device Inventory for Single Values All Key Values and Subkeys Updated Windows Device Sync Experience Enhances Per-Device Troubleshooting Configure Windows Sandbox vGPU Policy using Intune for Better Graphics Performance or Reduced Attack Surface
ConfigMgr SCCM Package Migration During Side-by-Side Upgrade

ConfigMgr SCCM Package Migration During Side-by-Side Upgrade

Written By Anoop C Nair
Last Updated August 7, 2024
Posted In SCCM
SHARE

ConfigMgr SCCM Package Migration During Side-by-Side Upgrade. I want to share an exciting question that targets me and possible answers.

How to perform package migration? (Scenario – Side By Side Upgrade from SMS to SCCM).

Transferring an SCCM server from one hardware environment to another is regular in organization settings. For several analyses, such server hardware migration may be required, with server OS upgrades indicating a common situation.

Initially, I planned to use a third-party tool (1E Migration Tool), which I never tried. Then, the question arose: How can we achieve this without third-party tools?

Patch My PC

ConfigMgr SCCM Package Migration During Side-by-Side Upgrade

I thought of a few options (I won’t go into details of every step).

Option A ConfigMgr SCCM Package Migration During Side-by-Side Upgrade

1. Attach a new SMS server to the current central server.
2. Packages and collections will get replicated automatically.
3. Detach the server from the existing hierarchy.
4. Upgrade the server to SCCM.

Option B ConfigMgr SCCM Package Migration During Side-by-Side Upgrade

Microsoft offers a tool called “CopySCCMObj,” which you can get from your Microsoft TAM. It will help you migrate Packages, collections, and Advertisements.

Option C (Kim’s solution Data is not been updated since 2008)

1. Install SMS 2003 SP2 on the new server.
2. Attach the new SMS 2003 SP2 site as a child site.
3. Let objects replicate.
4. Break the Parent-Child relationship.
5. Upgrade new Site to Configmgr 2007.
6. Install KB945898.
7. Migrate clients to the new site.
8. Remove boundaries from the original site.
9. Add boundaries to the new site.
10. Decommission the original site.
11. Migrate non-replicating objects (queries/reports).

Option D ConfigMgr SCCM Package Migration During Side-by-Side Upgrade

1. Take the backup of the SMS central server.
2. Restore that in the LAB environment.
3. Upgrade it to SCCM.
4. Build another SCCM server with the site code and name (which you plan for the new SCCM hierarchy) and attach it to the central server.
5. All the packages and collections will be replicated.
6. Take the backup of the later SCCM server and restore it in the production environment.

We are on WhatsApp. To get the latest step-by-step guides and news updates, Join our Channel. Click here –HTMD WhatsApp.

Author

Anoop C Nair is Microsoft MVP! He is a Device Management Admin with more than 20 years of experience (calculation done in 2021) in IT. He is a Blogger, Speaker, and Local User Group HTMD Community leader. His primary focus is Device Management technologies like SCCM 2012, Current Branch, and Intune. He writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc.

Written by

Anoop C Nair is Workplace Technology solution architect with 25+ years of experience in global enterprise organizations such as JP Morgan, Capgemini, etc. Microsoft Certified Trainer. Microsoft MVP from 2015 onwards for consecutive 11+ years! He also conducts Intune and modern workplace tech training for enterprise organizations. He is Blogger, Speaker, and Founder of HTMD Community and HTMD Conference. His main focus is on Device Management technologies like Intune, Windows, Cloud PC. He writes about technologies like Intune, SCCM, Windows, Cloud PC, Windows, Entra, Microsoft Security.

Discussion · 6 comments

  3. Hi Anup,

    I have a situation i need to upgrade SMS 2003 to SCCM 2007. I never performed previously.
    Our client want to Upgrade their SMS to SCCM without removing SMS.
    SMS 2003 is running fine and managing their clients.
    SCCM 2007 is installed and schema is upgraded.

    Here is my question what is the best plan ?

    Here is my plan, please verify and please suggest.

    SMS 2003 Work ground.
    1. Stop SMS 2003 Active Directory System Discovery (Why this important because of Overlapping if we run Overlapping tool scripts its says Overlapping True)
    2. SMS 2003 still manage sites desktops
    3. We can check with push some small applications on Site system clients.

    SCCM 2007 Workaround.
    1. Add IP ranges on Site Boundaries **
    2. Go to Client Installation Methods Client Push Installation  Do not enable Client Push Installation …….(Its stop automatic Client installation or Up-gradation with un-manage way)
    3. Start System Discovery with  Discovery Methods Active Directory System Discovery Enable Active Directory System Discovery
    4. Optional  here we can check OVERLAPPING with scripts or tools.
    5. Navigate to Computer Management Collections  All System right click and update collection Membership
    6. Refresh on right hand side Console twice  here we can see all systems within the boundaries and specific criteria based collections
    7. We can check also on client side machines are not upgraded with un-managed way.
    8. We can push client on machine in one machine/ one collection.

    Thanks in Advance.

    Reply

  5. Thanks for Reply Anup

    Yes ..we are going to update SMS clients to SCCM Client and future SMS will be down permanently.

    What is the basic diff between side by side and inplace ?

    Thanks i am waiting for your reply..

    Reply

  6. Please forget about QST… What is the basic diff between side by side and inplace ?

    Just want to know, if we want to upgrade their SMS client to SCCM client how to do that ?

    Please verify also my PLAN.

    Reply

Join the discussion

Your email address will not be published. Required fields are marked *

Related guides

Intune

Windows 11 KB5101650 KB5099414 July 2026 Patch and 3 Zero Day Vulnerabilities and 570 Flaws

Key Takeaways Windows 11 KB5101650 KB5099414 July 2026 Patch and 3 Zero Day Vulnerabilities and 570 Flaws! In the July 2026 Patch, Microsoft introduced new features designed to improve the overall Windows experience. The update adds enhancements to Windows Update for more flexible update management and introduces Point-in-Time Restore, providing an additional recovery option for […]

AC Anoop C Nair 9 min read
Intune

2026 June KB5094126 KB5093998 Windows 11 Patch | 3 Zero Day Vulnerabilities and 200 Flaws

Key Takeaways 2026 June KB5094126 KB5093998 Windows 11 Patch | 3 Zero Day Vulnerabilities and 200 Flaws! The June 2026 Windows 11 Patch Tuesday update brings several improvements to File Explorer. It adds support for additional archive formats, including UU, CPIO, XAR, and NuGet Packages (NUPKG). The update also preserves View and Sort preferences in […]

AC Anoop C Nair 10 min read
Intune

2026 May KB5089549 KB5087420 Windows 11 Patch | 0 Zero Day Vulnerabilities and 120 Flaws

Key Takeaways The Windows 11 May 2026 Patch KB5089549 KB5087420 Update brings important security fixes, performance improvements, and reliability enhancements across the operating system. The update introduces new features such as Xbox Mode for gaming, File Explorer improvements, enhanced input and sharing experiences, better taskbar and Windows Hello reliability, and additional enterprise management capabilities for […]

AC Anoop C Nair 8 min read
SCCM

ConfigMgr 2603 Introduces New Early Update Enrollment Process

Key Takeaways In this post we are discussing the ConfigMgr 2603 Introduces New Early Update Enrollment Process. Microsoft has officially released Configuration Manager version 2603 to the Early Update Ring, giving organizations an opportunity to test upcoming improvements before the global production rollout. The release is targeted at enterprises running ConfigMgr version 2409 or later […]

AC Anoop C Nair 3 min read