SCCM servers OS upgrade

%3CLINGO-SUB%20id%3D%22lingo-sub-309601%22%20slang%3D%22en-US%22%3ESCCM%20servers%20OS%20upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309601%22%20slang%3D%22en-US%22%3E%3CP%3ECurrently%20running%20SCCM%20CB%201802%20on%201%20Primary%20and%202%20Secondary%20servers%20and%2075%20DPs.%20All%20running%20on%202012%20R2.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ENeed%20to%20upgrade%20the%20Primary%20and%202%20Secondary%20server%20OS%20to%202016.%3C%2FP%3E%3CP%3EWhich%20is%20the%20best%20method%20either%20Inplace%20or%20Side%20by%20side%3F%3C%2FP%3E%3CP%3EIf%20inplace%20%2C%20what%20are%20the%20risk%20and%20how%20to%20mitigate%20the%20issues%3F%3C%2FP%3E%3CP%3EAny%20document%20for%20inplace%3F%3C%2FP%3E%3CP%3EIf%20side%20by%20side%2C%20how%20to%20migrate%20the%20existing%20SCCM%20CB%201802%20to%20another%20server%20with%20new%20OS%202016.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-309601%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESCCM%20server%20OS%20upgrade%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325940%22%20slang%3D%22en-US%22%3ERe%3A%20SCCM%20servers%20OS%20upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325940%22%20slang%3D%22en-US%22%3E%3CP%3EI%20suggest%20a%20side-by-side%20upgrade.%20Basically%2C%20you%20install%20a%20new%20server%20and%20a%20new%20sccm%20implementation%20and%20configure%20the%20source%20hierarchy.%3C%2FP%3E%3CP%3ECheck%20this%20link%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fwww.systemcenterdudes.com%2Fsccm-1511-migration%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.systemcenterdudes.com%2Fsccm-1511-migration%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309643%22%20slang%3D%22en-US%22%3ERe%3A%20SCCM%20servers%20OS%20upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309643%22%20slang%3D%22en-US%22%3E%3CP%3EI%20would%20do%20a%20side-by-side%20migration%20by%20adding%20new%202016%20servers%20into%20your%20current%20SCCM%20infrastructure%20and%20then%20moving%20the%20roles%20over.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20docs%20page%20should%20help%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsccm%2Fcore%2Fservers%2Fmanage%2Fmodify-your-infrastructure%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fsccm%2Fcore%2Fservers%2Fmanage%2Fmodify-your-infrastructure%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309642%22%20slang%3D%22en-US%22%3ERe%3A%20SCCM%20servers%20OS%20upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309642%22%20slang%3D%22en-US%22%3Eany%20issues%20after%20the%20upgd%3F%3CBR%20%2F%3Eis%20it%20a%20smooth%20upgrade%20from%202012R2%20to%202016%3F%3CBR%20%2F%3Eany%20doc%3F%3CBR%20%2F%3E%3CBR%20%2F%3EI%20think%20WSUS%20role%20need%20to%20be%20uninstalled%20before%20the%20upgrade..%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-309621%22%20slang%3D%22en-US%22%3ERe%3A%20SCCM%20servers%20OS%20upgrade%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309621%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn-Place%20upgrade%20is%20the%20best%20option%20to%20migrate.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Currently running SCCM CB 1802 on 1 Primary and 2 Secondary servers and 75 DPs. All running on 2012 R2.


Need to upgrade the Primary and 2 Secondary server OS to 2016.

Which is the best method either Inplace or Side by side?

If inplace , what are the risk and how to mitigate the issues?

Any document for inplace?

If side by side, how to migrate the existing SCCM CB 1802 to another server with new OS 2016.

4 Replies
Highlighted

Hi,

 

In-Place upgrade is the best option to migrate.

Highlighted
any issues after the upgd?
is it a smooth upgrade from 2012R2 to 2016?
any doc?

I think WSUS role need to be uninstalled before the upgrade..
Highlighted

I would do a side-by-side migration by adding new 2016 servers into your current SCCM infrastructure and then moving the roles over.

 

This docs page should help: https://docs.microsoft.com/en-us/sccm/core/servers/manage/modify-your-infrastructure

Highlighted

I suggest a side-by-side upgrade. Basically, you install a new server and a new sccm implementation and configure the source hierarchy.

Check this link: https://www.systemcenterdudes.com/sccm-1511-migration/