Cumulative Update 7 for Exchange Server 2013 (KB2986485)

The Exchange Team announces update Cumulative Update 7 for Exchange Server 2013 (KB2986485)

When you install this update your system version will change to: 15.0.1044.25

All informations about changes included in CU 7 for Exchange 2013 can be found here: KB2986485

This Cumulative Update contains the following fixes:

  • 3004235 Exchange Server meetings in Russian time zones as well as names of time zones are incorrect after October 26, 2014
  • 3012655 New-MailboxImportRequest causes unreadable characters when you import an ANSI format .pst file of Russian language
  • 3012652 CalendarProcessing cmdlet does not generate delegate permissions to universal security groups in Exchange Server 2013
  • 3009631 Advanced Find against the Sent Items folder in Outlook returns no result in Exchange Server 2013
  • 3009612 Outlook Web App shows organization details on the contact card beyond the scope of user ABP in Exchange Server 2013
  • 3009291 Shared mailbox cannot be opened in Outlook in an Exchange Server 2013 environment that has multiple domains
  • 3008453 Cannot edit or delete forms from the organizational forms library in Exchange Server 2013

Continue reading

Updated Release of MS13-061 Security Update for Exchange Server 2013

Few days ago we wrote about security update MS13-061, after installation it caused few errors in Exchange 2013 environment.

We wrote about this here:

Exchange 2013 Security Update MS13-061 not recommended to install


This security update was removed from Microsoft Download Center on 08/14/2013

Today Exchange Team released updated security updates for both Exchange 2013 RTM CU1 and Exchange 2013 RTM CU2.


You can download security update here:


As always we recommend to test updates in lab environment first.

More information you can find on Exchange Team Blog

Exchange 2013 RTM CU2 (KB2859928) updated release – fix public folders issue

Cumulative Update 2 for Exchange Server 2013 was re-released yesterday (07/29/2013)

New version of CU2 for Exchange 2013 RTM fixes a serious permission issue when moving modern public folders mailboxes around.


We wrote about this in article:

Exchange 2013 CU2 Issue – Public Folder Permissions Loss After PF Mailbox Move


Regardless of whether you are using modern public folders, we strongly recommend upgrading to this build of Exchange 2013 RTM CU2.


New CU2 has build number: 15.0.712.24 (KB2859928)

and can be downloaded from Microsoft Download Center:

 Cumulative Update 2 for Exchange Server 2013 (KB2859928)


Continue reading

Exchange 2013 CU2 released (KB2859928)

Microsoft announced the release of Exchange 2013 CU2 on the Microsoft Exchange Team Blog.

Exchange 2013 Cumulative Update 2 can be downloaded here:

Cumulative Update 2 for Exchange Server 2013 (KB2859928)


After installation CU2 you will get version number: 15.0.712.22


CU2 contains a number of fixes as well as new/improved features, including:

  • Per-server database support increased back to 100
  • OWA Silent Redirection
  • Addition of the DAG Management service
  • Changes to Managed Availability
  • Improved PowerShell Help Updating
  • OWA Search improvements
  • Malware Filter Rules


Description of Cumulative Update 2 for Exchange 2013 you can find below:

Continue reading

Exchange 2013 CU2 – mailbox databases limit changes

Administrators of Exchange 2010 who have more than 50 databases can now be happy.

Exchange 2013 enterprise has limit of 50 databases per server, but not with CU2 !!!!

Exchange Team has released that many of us have Exchange 2010 environments with more than 50 databases. And during migration to Exchange 2013 enterprise it could be a problem to decrease number of mailbox databases to 50 per server.

So when you install CU2 for Microsoft Exchange 2013, mailbox databases limit for enterprise version will be increased to 100.

CU2 is expected later this summer.

CU2 won’t change number of databases pers server for standard edition, and it will be 5 per server.

More information you can find on Exchange Team Blog:

Per-Server Database Limits Explained