Forum Discussion
Solved
Exchange 2016 Patch availability - can someone confirm that monthly patches are only for latest CU
We are looking to upgrade an existing on premise Exchange 2010 organisation to Exchange 2016. Reading the below, my highlight in bold https://nam02.safelinks.protection.outlook.com/?url=https%3A...
- We only issue security patches for the current and previous CU. We also roll them in to the next CU.
Put it another way: If you install with CU14 and we have to issue a security patch, we'll release the patch for CU14 and CU13. When CU15 becomes available and if we have to issue a security patch we'll release it for CU15 and CU14.
A quarter later we release CU16, and again, some security issue. We will release security patches for CU16 and CU15 only.
If you are still on CU14, no patch for you.
So you should always try to be current, or worst case be one CU behind, or you won't get security patches.
Hope that's clear enough.
Greg Taylor - EXCHANGE
Microsoft
MicrosoftWe only issue security patches for the current and previous CU. We also roll them in to the next CU.
Put it another way: If you install with CU14 and we have to issue a security patch, we'll release the patch for CU14 and CU13. When CU15 becomes available and if we have to issue a security patch we'll release it for CU15 and CU14.
A quarter later we release CU16, and again, some security issue. We will release security patches for CU16 and CU15 only.
If you are still on CU14, no patch for you.
So you should always try to be current, or worst case be one CU behind, or you won't get security patches.
Hope that's clear enough.
Put it another way: If you install with CU14 and we have to issue a security patch, we'll release the patch for CU14 and CU13. When CU15 becomes available and if we have to issue a security patch we'll release it for CU15 and CU14.
A quarter later we release CU16, and again, some security issue. We will release security patches for CU16 and CU15 only.
If you are still on CU14, no patch for you.
So you should always try to be current, or worst case be one CU behind, or you won't get security patches.
Hope that's clear enough.
Thanks Greg,
That confirms exactly how we read it, I was just hoping we had read it wrong 😉