System Center 2016-Updates Rollup
Following the release of Windows 2016 with Rollup 1 (https://msincic.wordpress.com/2016/10/14/upgrade-and-update-of-windows-server-2016/), the same happens with the System Center 2016.
See new SCOM 2016 Management Packs in https://msincic.wordpress.com/2016/10/25/new-system-center-operations-manager-2016-management-packs/
Why this happens?
Before a manufacturer releasing a final media to the public, it is distributed to the manufacturers.
For example, the manufacturer of HW needs to make sure that an update did not affect drivers or functionalities of the server.Developers (ISVs) need to make sure your plugins and software are still “talking” with the new version.
As the two products were made available to the media for manufacturers and developers a few weeks before the launch, Microsoft need to catalog and generate a package of updates that occurred between this launch for the manufacturers and the GA (General Availability) audience, which is usually 45 to 60 days.
Update Rollups of System Center 2016
Update Rollup 1 for VMM: https://support.microsoft.com/en-us/kb/3190597
Update Rollup 1 for SCOM 2007: https://support.microsoft.com/en-us/kb/3190029
Update Rollup 1 for Orchestrator: https://support.microsoft.com/en-us/kb/3190603
Update Rollup 1 for DPM: https://support.microsoft.com/en-us/kb/3190600
Noting that in the case of the SCCM upgrades and updates is carried out in own console as discussed in https://msincic.wordpress.com/2016/10/03/new-sccm-2016-updates-model/