Home

Migrating from SCCM to another deployment tool

%3CLINGO-SUB%20id%3D%22lingo-sub-1174994%22%20slang%3D%22en-US%22%3EMigrating%20from%20SCCM%20to%20another%20deployment%20tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1174994%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20work%20was%20in%20the%20process%20of%20migrating%20to%20SCCM%2C%20but%20for%20a%20few%20reasons%20has%20decided%20to%20retire%20SCCM%20from%20our%20environment.%26nbsp%3B%3CSPAN%3EWe%20still%20have%20the%20previous%20tool%20in%20place%20so%20that%20tool%20is%20fully%20functional.%3C%2FSPAN%3E%20Is%20there%20a%20best%20practice%20on%20the%20order%20on%20how%20to%20retire%20SCCM%20from%20a%20environment%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJeff%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1174994%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECM%202012%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EGeneral%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1175809%22%20slang%3D%22en-US%22%3ERe%3A%20Migrating%20from%20SCCM%20to%20another%20deployment%20tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1175809%22%20slang%3D%22en-US%22%3E%3CP%3ESince%20no%20one%20can%20possibly%20know%20how%20you%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F558251%22%20target%3D%22_blank%22%3E%40alekmanj%3C%2FA%3E%26nbsp%3B%20install%20CM12.%20There%20is%20no%20such%20things%20as%20best%20practices%20for%20this.%20However%2C%20uninstall%20the%20CM12%20client%2C%20uninstall%20all%20DPs%2C%20SUP%2C%20Etc%20from%20CM12.%20Once%20that%20is%20completed%2C%20turn%20off%20CM12.%20Then%20removed%20the%20system%20management%20container%20from%20AD%20and%20any%20user%20accounts%20BUT%20leave%20the%20CM%20server%20account%20for%20a%20while.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1182089%22%20slang%3D%22en-US%22%3ERe%3A%20Migrating%20from%20SCCM%20to%20another%20deployment%20tool%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1182089%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F558251%22%20target%3D%22_blank%22%3E%40alekmanj%3C%2FA%3E%26nbsp%3BDon't%20forget%20the%20Systems%20Management%20container%20in%20AD.%26nbsp%3B%20No%20harm%20leaving%20the%20schema%20extensions%20in%20place.%26nbsp%3B%20You'll%20want%20to%20clear%20the%20various%20components%20you've%20placed%20in%20DNS%20out.%26nbsp%3B%20Same%20for%20any%20IP%20Helpers%20for%20OSD%20across%20network%20subnets.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20you%20have%20AAD%2C%20you%20may%20have%20replicated%20AD%20groups%20used%20for%20SCCM%2C%20so%20you%20may%20need%20to%20clear%20those%20out.%26nbsp%3B%20Make%20sure%20any%20CMG%20servers%20are%20shut%20down%2C%20and%20there%20may%20be%20some%20other%20AAD%20work%20with%20load%20balancers%2C%20networks%2C%20resource%20groups%2C%20etc%20to%20be%20done.%26nbsp%3B%20Best%20practice%20is%20to%20document%2C%20document%2C%20document%2C%20so%20if%20you've%20done%20that%2C%20surgical%20removal%20should%20be%20at%20least%20easily%20plannable.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Visitor

My work was in the process of migrating to SCCM, but for a few reasons has decided to retire SCCM from our environment. We still have the previous tool in place so that tool is fully functional. Is there a best practice on the order on how to retire SCCM from a environment?

 

Thanks,

 

Jeff

2 Replies
Highlighted

Since no one can possibly know how you @alekmanj  install CM12. There is no such things as best practices for this. However, uninstall the CM12 client, uninstall all DPs, SUP, Etc from CM12. Once that is completed, turn off CM12. Then removed the system management container from AD and any user accounts BUT leave the CM server account for a while. 

Highlighted

@alekmanj Don't forget the Systems Management container in AD.  No harm leaving the schema extensions in place.  You'll want to clear the various components you've placed in DNS out.  Same for any IP Helpers for OSD across network subnets.

 

If you have AAD, you may have replicated AD groups used for SCCM, so you may need to clear those out.  Make sure any CMG servers are shut down, and there may be some other AAD work with load balancers, networks, resource groups, etc to be done.  Best practice is to document, document, document, so if you've done that, surgical removal should be at least easily plannable.