not so foreign Exchange 2013

I have been banging my head over issues with the new Exchange 2013. Install seems to go well but doesn’t seems to want to coexist with Exchange 2010. Moments aware from calling in a product support case I find Cumulative update 1 for Exchange Server 2013 (KB2816900):

It seems I now need to wait about an hour for this update to complete before I know if this fixes the issue*

* issue I am having is email routing between Exchange 2010 and Exchange 2013

More on this here


Internet Explorer 10, Crashing Exchange 2013 Exchange Admin Console

If you are running Exchange 2012 on Windows Server 2012 you will soon noticed that Internet Explorer 10 randomly crashes during operations in the new Exchange Admin Console (EAC).

I have found this to be very annoying. However there are options which you could take.

1. You can use Internet Explorer 10 from Windows 8 to access the EAC which works without issues or

2. You can install the following patch to stop the IE10 crashes on Server 2012 when working with Exchange 2013’s EAC:

Here is a direct link to the KB for this patch:


Removing an auto-mapped mailbox

In Exchange Server 2010 SP1, shared mailbox with full access rights will be auto mapped to the users given such rights. This is fine for that user who doesn’t seem to know how to add an additional mailbox to their Outlook 2007, 2010, 2013 client. But what about those support and systems admins who grant themselves access for troubleshooting and find out later they are stuck with this new folder under their Outlook folder that can’t be removed.

Well we never say “can’t”. So what you need to do to remote the auto-mapping attribute is to reach out to the administrator if you are not one or if you are just find your way to the Exchange Management Power Shell and issue the following command:

Add-MailboxPermission -Identity <shared mailbox alias> -User <your mailbox alias> -AccessRights FullAccess -InheritanceType All -Automapping $false

Once this command is run the additional mailbox will automatically be removed.

Reference: Disable Outlook Auto-Mapping with Full Access

Issue: Outlook Address Book Not Updating


New users added to Exchange 2010 do not show up in global address book

Tests Performed:

1. Searched for new users from Outlook – This failed
2. Searched for new users from OWA – This works
3. Put Outlook in non-cached mode and searched – this worked

Suspected Problem:

Offline Address Book Generation is not happening – Possible cause, resources (memory) on host server, service failure.

Steps Taken: *note* I have seen this before so I know where I am looking first

1. Stop the Microsoft Exchange File Distribution Service

2. Stop the Microsoft Exchange Address Book

3. Clear the files from ‘C:Program FilesMicrosoftExchange ServerV14ExchangeOAB’ putting them into a backup folder of some sort.

4. Restart the services above.

5. To get the OAM to immediately generate run the following command: Update-OfflineAddressbook “name of offline address book”. You may encounter an issue stating that the System Attendant Service is not running or you do not have permission. 1. Make sure you are running the Exchange Management Shell as Administrator and 2. The System Attendant Service is running. *note* The Service is named “Microsoft Exchange System Attendant”.

6. You will now notice that the GUIDS and files have started to populate under ExchangeOAB folder

Follow-up Testing that things now work:

1. Exit Outlook and delete the Offline Address Book cache from ‘C:Users%user profile%AppDataLocalMicrosoftOutlookOffline Address Books’

2. Open outlook again cache should repopulate at this point.

3. Open a new email message or click the Address Book and search for the person(s) who were not showing previously.


The Outlook Client failed to download an updated copy of the Offline Address Book because the services have stopped functioning. I was unable to obtain errors in the event logs regarding this, however having experienced this in the past it has become suspect

– For Darlene

Simple Exchange 2010 Database White Space Report

I was looking at some of my database on Exchange that seemed to be very large in size so first thought was that an offline defrag may be needed, but before I reach that point I wanted to know how much ‘slack’ or white space existed in each of my Exchange databases.

This was done by using the following command syntax in the Exchange Management Shell:

To export this into a CSV format the following can also be done, so that you can give to any management members for review of your findings:

Next, I may find a way to setup this to email a weekly report…