Exchange 2013 CU15 has been released to the Microsoft download centre! Exchange 2013 has a different servicing strategy than Exchange 2007/2010 and utilises Cumulative Updates (CUs) rather than the Rollup Updates (RU/UR) which were used previously. CUs are a complete installation of Exchange 2013 and can be used to install a fresh server or to update a previously installed one. Exchange 2013 SP1 was in effect CU4, and CU15 is the eleventh post SP1 release. How time flies…..
- Hi, I found a problem during installation of CU1 for Exchange 2013 in existing envroiment based on SBS 2008 SP1 with Exchange 2007 SP3 RU10. I need to migrate mailbox from Exchange 2007 to Exchange 2013.
- How do you enable Office 365 Group Writeback for a Hybrid Coexistence Environment today? Exchange versions. Exchange 2016 CU1 or higher. Control and isolation.
Exchange 2013 Cu1
Updates Of Particular Note
Issues Resolved
Some Items For Consideration
As with previous CUs, this one also follows the new servicing paradigm which was previously discussed on the blog. The CU package can be used to perform a new installation, or to upgrade an existing Exchange Server 2013 installation. You do not need to install Cumulative Update 4 or 5 for Exchange Server 2013 when you are installing the latest CU. Cumulative Updates are well, cumulative. What else can I say…
- After you install this cumulative update package, you cannot uninstall the cumulative update package to revert to an earlier version of Exchange 2013. If you uninstall this cumulative update package, Exchange 2013 is removed from the server.
- Place the server into maintenance mode prior to installing, confirm the install then take the server out of maintenance mode
- Ensure that you consult with all 3rd party vendors which exist as part of your messaging environment. This includes archive, backup, mobility and management services.
- Ensure that you do not forget to install this update on management servers, jump servers/workstations and application servers where the management tools were installed for an application. FIM and 3rd party user provisioning solutions are examples of the latter.
- Ensure that the Windows PowerShell Script Execution Policy is set to “Unrestricted” on the server being upgraded or installed. See KB981474.
- Disable file system antivirus prior to installing.
- Once server has been restarted, re-enable file system antivirus.
- Note that customised configuration files are overwritten on installation. Make sure you have any changes fully documented!
- While CU15 does not add any new AD Schema changes, if you are on an out-dated CU currently then deploying CU15 may contain AD Schema updates for your organisation – please test and plan accordingly! Whether or not your AD Schema needs to be updated depends upon your initial Exchange 2013 version. This will dictate if the AD Schema needs to be modified. Check the values as noted in this post. Additional RBAC definitions may also be required.
Please enjoy the update responsibly!
What do I mean by that? Well, you need to ensure that you are fully informed about the caveats with the CU and are aware of all of the changes that it will make within your environment. Additionally you will need to test the CU your lab which is representative of your production environment.
Cheers,
Exchange 2013 Cu1 Isolation System
Rhoderick