Released: Exchange Server 2013 Cumulative Update 3 & Update Rollup 3 For Exchange 2010 Service Pack 3

Exchange 2013 CU3 The Exchange team is announcing today the availability of our most recent quarterly servicing update to Exchange Server 2013. Cumulative Update 3 for Exchange Server 2013 and updated UM Language Packs are now available on the Microsoft Download Center. Cumulative Update 3 includes fixes for customer reported issues, minor product enhancements and…


Exchange Server 2013 Service Pack 1 Coming in Early 2014

  The big news is here 🙂 Exchange Server 2013 Service Pack 1 Coming in Early 2014 Few notable improvements are:   Windows Server 2012 R2 Support S/MIME support for OWA Support for S/MIME Edge Transport Server Role   For further details , check the Exchange team blog @


The Exchange ActiveSync Admin (EASAdmin)

Nice tool, adding it to the blog , so we never forget about it   The Exchange ActiveSync Admin (EASAdmin) tool enables administrators to manage the process of remotely erasing lost, stolen, or otherwise compromised mobile devices. The EASAdmin Tool is designed for use with Exchange Server 2010, Exchange 2013, Office 365 (Wave14 and 15)….


Office 365: New version of DirSync released

Version: 6553.0002Date Released:11/4/2013Notable Changes:  Fix to handle Read-Only Domain Controllers in Password Sync. DirSync can be installed on a Domain Controller (Development purposes).  Documentation on how to deploy can be found here       You can check your DirSync version by running the following PowerShell command:  (GP ‘hklm:SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Online Directory Sync’).DisplayVersion   The latest version can…


Moving to Exchange 2010 SP3 ? pay attention to “Logfile ‘f:logsDBEnn.log’ is generation 2024; however the expected generation is 2004”

I have seen the following behavior in certain customer environments, and this is due to the 8DOT3 name creation enforcement. If 8DOT3 name creation is enabled on volumes that contain transaction logs in Exchange Server 2010 SP3, this can cause invalid transaction logs to be returned as part of a findfile query during the databases’…


Updated Exchange Server 2013 docs on TechNet

Enjoy And make sure you have a look at “Exchange Server 2013 DeploymentAssistant”