Microsoft recently released a Cumulative Update (CU) for Exchange 2013 and Update Rollups (UR) for Exchange 2007 and 2010.
At this time you probably heard that UR 8 for Exchange 2010 had to be pulled up, but it has been re-released, so the discovered problems should be fixed now.
- Cumulative Update 7 for Exchange Server 2013 (KB2986485)
Cumulative Update 7 for Exchange Server 2013 resolves issues that were found in Exchange Server 2013 SP1 since the software was released. This update rollup is highly recommended for all Exchange Server 2013 customers.
- Update Rollup 8 v2 For Exchange 2010 SP3 (KB2986475)
Update Rollup 8 v2 for Exchange Server 2010 Service Pack 3 (SP3) resolves issues that were found in Exchange Server 2010 SP3 RU7 since the software was released. This update rollup is highly recommended for all Exchange Server 2010 SP3 customers.
For a list of changes that are included in this update rollup, see KB2986475.
This update rollup does not apply to Exchange Server 2010 Release To Manufacturing (RTM), Exchange Server 2010 Service Pack 1 (SP1) or Exchange Server 2010 Service Pack 2 (SP2).
For a list of update rollups applicable to Exchange Server 2010 RTM , Exchange Server 2010 Service Pack 1 (SP1) or Exchange Server 2010 Service Pack 2 (SP2), refer to the Knowledge Base article KB937052.
- Update Rollup 15 for Exchange Server 2007 Service Pack 3 (KB2996150)
Update Rollup 15 for Exchange Server 2007 Service Pack 3 (SP3) resolves issues that were found in Exchange Server 2007 SP3 since the software was released. This update rollup is highly recommended for all Exchange Server 2007 SP3 customers.
For a list of changes that are included in this update rollup, see KB2996150.
This update rollup does not apply to Exchange Server 2007 Release To Manufacturing (RTM), Exchange Server 2007 Service Pack 1 (SP1) or Exchange Server 2007 Service Pack 2 (SP2).
For a list of update rollups applicable to Exchange Server 2007 RTM , Exchange Server 2007 Service Pack 1 (SP1) or Exchange Server 2007 Service Pack 2 (SP2), refer to the Knowledge Base article KB937052.
from Exchange News Full Article
No comments:
Post a Comment