Microsoft over the years has released CUs (Cumulative Updates), and users have become familiar with a particular type of deterrent messaging around those updates.
Microsoft states,
“Over the years, as we released CUs (Cumulative Updates), you have become familiar with a certain type of deterrent messaging around those updates. Examples like the below messages often lead DBA’s to plan for a deployment of a certain CU, only if and when they hit an issue.”
- “This cumulative package is intended to correct only the problems that are described in this article. Apply it only to systems that are experiencing these specific problems.”
- “A supported cumulative update package is now available from Microsoft. However, it is intended to correct only the problems that are described in this article.”
As of the January CU releases, these caution messages have been updated, and Microsoft is now recommending the ongoing proactive installation of CUs as they have become available. In order to install the CU with the same level of confidence you need to install SP’s (Service Packs) as they are released. The reason for this is that CUs are certified and tested to the level of SPs. Microsoft CSS data indicates that a significant percentage of customer issues are often previously addressed in the released CU, but not applied proactively. Moreover, the CUs contain added value over and above hotfixes. This may contain supportability, logging, and reliability updates enhancing the overall experience.
In addition to messaging and guidance updates, Microsoft has made updates to the CU acquisition model, as per the
official blog,
- CUs, of course, have traditionally been made available on the “Hotfix” server (accompanied by the “cautionary language” associated with a ‘QFE’ or ‘Hotfix’). The inconsistency here is that CUs are not really simple quick hotfixes anymore. The encompassed updates are well tested at individual as well as full system integration levels today.
- Therefore, we are now placing the latest CU per mainstream supported baseline (2012 SP2/SP3 and 2014 RTM/SP1 today) on microsoft.com/downloads, just as is done for Service Packs today
- Additionally, we will soon release, and maintain, all CUs into the Windows Update Catalog to facilitate acquisition and distribution
- Only interim CU ‘On-Demand’ fixes will be placed on the hotfix server moving forward
- To reduce friction, downloading CUs from the microsoft.com/downloads will not require providing/receiving an email and URL
- We are also evaluating offering the latest CU as an Optional update on Microsoft Update, just like Service Packs today.
The following are the acquisition changes:
- CUs, of course, have traditionally been made available on the “Hotfix” server (accompanied by the “cautionary language” associated with a ‘QFE’ or ‘Hotfix’). The inconsistency here is that CUs are not really simple quick hotfixes anymore. The encompassed updates are well tested at individual as well as full system integration levels today.
- Therefore, we are now placing the latest CU per mainstream supported baseline (2012 SP2/SP3 and 2014 RTM/SP1 today) on microsoft.com/downloads, just as is done for Service Packs today
- Additionally, we will soon release, and maintain, all CUs into the Windows Update Catalog to facilitate acquisition and distribution
- Only interim CU ‘On-Demand’ fixes will be placed on the hotfix server moving forward
- To reduce friction, downloading CUs from the microsoft.com/downloads will not require providing/receiving an email and URL
- We are also evaluating offering the latest CU as an Optional update on Microsoft Update, just like Service Packs today.
Microsoft concluded by saying,
“We hope these changes will drive more proactive, informed, confident, and simplified CU adoption. Updates reflecting this change to various MSDN and Knowledge Base articles are rolling out now.”