With the release of System Center 2012 Configuration Manager, the Configuration Manager Sustained Engineering team has moved to a new servicing model for product updates. Instead of individual hotfixes, there will be regularly released cumulative updates.
This new approach will reduce confusion about which fixes to apply, and provide a consistent approach to Configuration Manager servicing. Testing all code changes together minimizes the historical risk of applying multiple hotfixes at the same time.
Cumulative updates are, essentially, hotfixes; they simply address more than one issue at a time. It will be available for download via the Knowledge Base (KB) article and our hotfix servers. We anticipate quarterly releases but that is subject to change based on the volume and nature of issues addressed.
The KB article that documents each cumulative update should make every issue identifiable to our customers. If you are not encountering one of the documented issues you will not need to apply the update.
For information about installing Cumulative Updates, see “Update System Center 2012 Configuration Manager” on TechNet.
-- Brian Huneycutt
This posting is provided "AS IS" with no warranties and confers no rights.
Finally!!!!!!!!!!!!!! This is most Welcome.
Am I hallucinating after installing this, it appeared that this did not add itself to the Site process for applying the patch for the SCCM Client. I thought that was the whole reason for the Site Hierarchy Client Installation Settings feature for upgrading the SCCM Client.
Fantastic news. It's great to see that we are moving down the cumulative update path just like OpsMgr 2007 has been, ConfigMgr 2007 was an absolute nightmare to patch. It's also good to know you are aiming for quarterly released. Once again, thankyou and great work.
This seems like a good idea, until you have to apply a cumulative to a system servicing 100,000 users, where service managers are extremely nervous about what they consider a large update, compared to applying a hotfix for a specific issue.
After the experiences of SP1 breaking PXE, and adding a number of other minor problems, I'd prefer to pick and choose what hotfixes I apply to our service, rather than throw a bunch of them at the servers and hope none introduce further problems.
That's what TEST and PROD are for