Microsoft have released an updated version of the Exchanger 2013 Server Roles Requirements Calculator.

In addition to numerous bug fixes, this version includes new functionality: CPU utilization table, ReplayLagManager support, MaximumPreferredActiveDatabases support, Restore-DatabaseAvailabilityGroup scenario support, and guidance on sizing recommendations. You can view what changes have been made or download the update directly.

Read the full article here.


Earlier this week the Microsoft Exchange product team released the latest version of the Server Role Requirements calculator, now at version 6.6

The Exchange Server role requirements calculator is essential for proper design and planning of your Exchange Server environment and it even includes recommendations for your client access servers too!

For more information and to download it check out the Exchange Team blog here


In this scenario I have a Exchange 2013 Hybrid environment with Office 365 and 99% of the users have mailboxes in Office 365.

Creating a mailbox for an existing Active Directory user isn't possible through the Exchange GUI using the Exchange Admin Console (EAC) and must be done through PowerShell, here is how its done. ...continue reading "Creating an Office 365 mailbox for an existing Active Directory user"

I was spending some time going through Exchange PowerShell cmdlets to create an Admin Role with the least permissions required for an account for the System Center Configuration Manager Exchange Connector when I stumbled across this excellent script. It was hard to find so I am putting it out there for others in the hope it gets more exposure


When trying to access the legacy url /Exchange on an SBS 2011 server you get an error like this "Server Error in '/' Application" which is most annoying when you have users who struggle to update their bookmarks to /owa as it is now. ...continue reading "SBS 2011 Exchange redirect Server Error in ‘/’ Application"

Earlier this year Microsoft released an important hotfix for .NET 4.5:

A .NET Framework 4.5-based application that excessively uses ExecutionContext objects or WCF may result in too many objects being pinned on the Garbage Collector heap. This causes heap fragmentation along with an increase in memory and CPU usage by the Garbage Collector.  ...continue reading ".NET 4.5 hotfix available to reduce memory consumption of Exchange 2013 store worker processes"

Due to a version incompatibility between outlook.exe and mso.dll, a mismatched reference to a data structure causes the “Minimize” button in the navigation pane to render incorrectly, typically extremely large to the point that the navigation pane is "invisible" to the user. The issue only manifests when incompatible versions of outlook.exe and mso.dll exist on the system. ...continue reading "Outlook 2013 Folder Pane Disappears After Installing September 2013 Public Update"

On the 9th of this month Microsoft released the latest cumulative update to Exchange Server 2013 and is it now available from the Microsoft download centre. ...continue reading "Updated: Exchange Server 2013 RTM Cumulative Update 2"

I had this occur to me recently as I had an Exchange 2010 environment and having installed my first Exchange 2013 server as a CAS & Mailbox. I tried logging into the Exchange Admin Center using the URL https://localhost/ecp and noticed that after I logged in it looked very much like the Exchange 2010 version of ECP. ...continue reading "Accesing the Exchange 2013 Admin Center when your mailbox is on Exchange 2010"

I came across an interesting issue the other day whilst working with a client and setting up a new PC for them. The PC had come with Office 2013 OEM which as you know is the latest edition of the popular Microsoft Office suite of programs. What struck me as odd was when trying to connect Outlook to the users Exchange mailbox I was getting the following error:

The resource that you are trying to use is located on an unsupported version of Microsoft Exchange. Contact your e-mail administrator for assistance ...continue reading "Office 2013 will not connect to Exchange 2003 mailboxes"