Installation and Upgrade of System Center 2016
With the launch of the media RTM (Release To Manufacturing or End) of the Windows System Center 2016 2016 and it comes time to do the upgrade of 2012 and 2016 R2 releases Technical Preview.
I will address each of them from 2016 Technical Preview releases since the migration of 2012 R2 versions is typically simpler and supported.
Update: After install or upgrade download Update Rollups of System Center 2016: https://msincic.wordpress.com/2016/10/25/system-center-2016-updates-rollup/
System Center Configuration Manager (SCCM)
SCCM is one of the products that were already in 2016 version since the beginning of the year, when it was released as SCCM 1511, following Windows nomenclature 10.
Follow the posts that I’ve written about this version:
For those who have the SCCM R2 upgrade 2012 is quiet and just run the Setup to work.
System Center Operations Manager (SCOM)
The SCOM upgrade can be done both of the 2012 version R2 as of 2016 Techincal Preview versions in the same way, it supports both paths.
The only recommendation that the setup is to back up the databases (and DW) before, because there’s no way back if errors occur in the middle of the process:
You will need to upgrade the Report Viewer, before we use the RV of SQL 2012 and should now be used RV of SQL 2016, which is found in the link of the actual Setup:
System Center Service Manager (SCSM)
Upgrade both the 2012 R2 as the Technical Preview is simple, requires no type of restriction, occurring very quiet:
It is important to remember at the end which will upgrade the Management Packs from the wizard to the SCOM 2016 has:
System Center Virtual Machine Manager (VMM)
This is a product that does not allow the automatic upgrade of the Techinical version Preview, but allows from the 2012 R2.
In the case of Tecnhinical Previwe, the Setup will indicate that already exists and will ask to uninstall:
However, the reinstallation is simple. Just when choosing to keep the database:
When you run Setup again using the same database and directory of libraries:
After that VMM will function normally, but it’s good to remember that you will need to uninstall and reinstall agents, if he doesn’t do the automatic upgrade of the agent.
Recalling that one of the most interesting features is integration with Azure: https://msincic.wordpress.com/2015/06/03/system-center-virtual-machine-manager-2016-tp2-integrated-with-azure/
System Center Orchestrator (SCORCH)
As well as the VMM, it requires reinstalling but it is possible to maintain the database and repointing on new installation:
After the process, the normally appear with the same runbooks Integrations Packs.
In the case of SCORCH Packs and Integrations of the SCOM 2007 is important to upgrade the packages, and in SCOM 2007 is a lot easier to have the menu, while not the Orchestrator.