Monday 11 February 2013

Exchange Server 2013 Servicing (patching cycle)

The Exchange Team have written an article here that explains the changes to patching Exchange Server 2013; updates are now quarterly with each cumulative update (cu) being a full Exchange Server release.

The primary benefits to customers with this approach include:

  • Predictable release cadence – CU’s will be delivered on a pre-determined schedule four times a year allowing customers to plan their deployments more deliberately. Lync and SharePoint also release CU’s at a regular cadence.
  • Dedicated security releases – Independent security releases will allow customers to quickly install an update with confidence knowing that only the fixes which address a particular problem will be included. In the event there are multiple security releases required for a particular CU, all fixes will be delivered in a single package simplifying the deployment of multiple security fixes.
  • Datacenter scale validation – On-Premises and Hybrid customers will be able to deploy CU’s knowing that the same code is already deployed in the Exchange Online service and has been validated against millions of mailboxes in the world’s largest and most demanding Exchange installation.
  • Improved support for hybrid deployments– System requirements will be better aligned because the on-Premises server and datacenter servers will be running identical code.
  • More rapid changes to language resources – In the RU model, language modifications to releases were limited to Service Pack releases. With the CU model, updates to language resources will be available in each release.

Still no word on SP3 for Exchange 2010!

No comments: