Upgrading from SCCM 2007 to SCCM 2012 with Adaptiva Onesite? There are loads of customers still in the planning phase of SCCM 2007 to SCCM (System Center Configuration Manager) 2012 migration.
In fact, this is a huge topic and needs to invest a lot of time to study the current environment, plan, test, and execute the migration.
Upgrading from SCCM 2007 to SCCM 2012 with Adaptiva Onesite
There are loads of guides and videos available to help you plan and execute the SCCM 2007 to SCCM 2012 migration. Some of them are noted Here, MMS 2012 and MMS 2013. Another list of videos is here. Migrations from SCCM 2007 to SCCM 2012 would be much easier with Adaptiva OneSite.
As the first phase of the SCCM 2012 migration process, we need to set up/build SCCM 2012 hierarchy. We can’t have an in-place upgrade, and the only way to upgrade is to side my side.
Preparing SCCM 2012 server for migration is the first step in the migration process. The second step would be migrating packages, collections, etc. Adaptiva Onesite helps in a big way to migrate packages and content from the existing SCCM 2007 to SCCM 2012 environment.
Using ConfigMgr, we can migrate all packages. In the Adaptiva Workbench for ConfigMgr 2012, publish all the packages you want OneSite to manage and Adaptiva clients to preserve in their Adaptiva Client cache after being migrated to 2012. The migration of Adaptive server components is very easy.
Client Migration – Once SCCM 2012 infra is ready and prepared along with Adaptiva OneSite servers, we can prepare for SCCM 2012 client migration. The process can be summarized in two steps:
Deploy an Adaptiva workflow to redirect Adaptiva clients to the new Adaptiva server for ConfigMgr 2012.
Upgrade ConfigMgr 2007 clients to 2012.
Any SCCM 2007/Adaptiva client added to the collection created in the previous section will immediately run the workflow, be removed from the SCCM 2007 Adaptiva server, and start reporting to the new Adaptiva server. It is recommended that you deploy the SCCM 2012 client to redirect clients shortly after or as part of this process. The SCCM 2012 client can be deployed using standard methods or via an Adaptiva Content Push policy to automate the process end-to-end. The following diagram illustrates the process:
More details about adaptive-specific documentation are available with Adaptive Support. More Details on Checklist on SCCM 2007 to SCCM 2012 migration via TechNet:-
- Administrator Checklist for Migration Planning
- Administrator Checklist for Hierarchy Migration
- Administrator Checklist for Migration
Anoop is Microsoft MVP! He is a Solution Architect in enterprise client management 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 main focus is on Device Management technologies like SCCM 2012, Current Branch, and Intune. E writes about ConfigMgr, Windows 11, Windows 10, Azure AD, Microsoft Intune, Windows 365, AVD, etc…