Exchange 2010 Database size growing problem


When you have Microsoft Exchange 2010 environment you can have problem with Exchange database size growing.

This is common problem and mostly caused by Exchange 2010 mailbox dumpster.

But if you have problem with mailbox databases backup, then all items deleted by users and all deleted mailboxes will not be purged until backup will end successful.

If you check size of all mailboxes in Exchange 2010 mailbox database, the sum of mailboxes can be less than mailbox database size. Yes we know that mailbox database has AvailableNewMailboxSpace but you can check that sum of mailboxes size and size of mailbox database white space can be also less then size of .edb file.

You can find informations how to reduce Exchange database size by moving all mailboxes from database to new one, or to dismount database and use Eseutil to defragment mailbox database. You can also find all disconnected mailboxes in database and purge them.

We wrote about this in post:
Microsoft Exchange 2010 how to reduce the size of the database

You can find information on Microsoft Support Website An Exchange Server 2010 database store grows unexpectedly large that if you want to stop mailbox database unexpected growth you need to install Rollup 1 for Microsoft Exchange 2010 SP2.

Unexpected growth of Exchange 2010 mailbox database can be caused by using:

  • using jurnaling mailbox in Exchange 2010 environment
  • using a third-party email message archival system

This issue can occur if the Microsoft Exchange Information Store service does not remove the deleted messages from the database.

Unfortunatelly when you use third-party email message archival system like Symantec Enterprise Vault, all emails moved to archive are deleted from user mailbox but they still remain in dumpster.

When you install Rollup 1 for Exchange 2010 SP2 it will probably fix this problem but it will fix only problem with new data added to archive but not clean the dirty pages or whitespace from preexisisting databases. 

More information you can find on Symantec Support Website:
Archiving of an Exchange 2010 database does not generate the expected amount of re-usable whitespace


How to resolve Exchange 2010 database growth:


When you apply Rollup 1 for Exchange 2010 SP2 you need to check few mailbox databases properties to make sure that all retentions and Quotas are configured properly.

To check Exchange 2010 mailbox database items retention like Mailbox, Deleted items and EventHistoryRetention you need to run Exchange Mangement Shell (EMS) with command:

Continue reading

Exchange 2010 get version number, build number


With every release of Rollup Update for Microsoft Exchange we are trying to get to know what Microsoft Exchange version we use.

When you check Microsoft Support Website Determine Exchange Version you will find out that there are two ways to get Microsoft Exchange version and build version.


Get Exchange 2007, 2010 version using Exchange Management Console:

  1. Start the Microsoft Exchange Management console.
  2. In the navigation pane, expand the Server Configuration objects until you locate the server object, and then select the server object.
  3. On the right side, notice the Exchange version number.



Get Exchange 2007, 2010 version using Exchange Management Shell command:

  1. Start the Microsoft Exchange Management shell.
  2. Run the following command at the command line:


Get-ExchangeServer | select name, AdminDisplayVersion, ExchangeVersion



Unfortunatelly using both of those methods we won’t get correct Exchange 2010, 2007 version.



Continue reading

Exchange 2010 SP2 installation Update Rollup 4-v2 Error code 0x80070643


Installation of Rollup 4 for Exchange 2010 SP2 fails:

Few days ago Microsoft has released new versions of latest Rollups for Exchange 2010 and 2007.

All of those rollups (version 2) we can install on server without uninstalling previous version.

When you are trying to install version 2 of Rollup 4 for Exchange 2010 SP2 you can get error 0x80070643 


How to resolve issue with Rollup 4 v2 for Exchange 2010 SP2 error code 0x80070643


If during installation of Rollup 4 version 2 you will get error code 0x80070643 then you have to do following:

  1. uninstall from Windows Server Windows Management Framework 3.0  (WMF 3.0) (Windows6.1-KB2506143-x64)
  2. reboot server
  3. install update Rollup 4-v2 for Exchange 2010 SP2
  4. reboot server
  5. install Windows Management Framework 3.0 after installing the Rollup 4-v2
    because of issues with installation of Rollup 5 and WMF 3.0 it’s better to not install WMF 3.0
  6. reboot server

We hope it will also help to update yours environments.



Microsoft Exchange 2013 RTM, Lync 2013 RTM


On October 11th 2012 Microsoft announced that Microsoft Lync 2013 has reached the Released to Manufacturing (RTM).

Microsoft Exchange 2013 RTM and Lync 2013 RTM will be available for the first quarter of 2013.

Also Office 2013, Exchange 2013 and Sharepoint 2013 have achieved RTM status and will be available in the same time.

  • Volume License customers with software assurance can start downloading mid-November 2012.
  • TechNet and MSDN subscribers are expected to get access around mid-November 2012 also.
  • The 2013 products will be available on the Volume Licensing price list on December 1.
  • New capabilities will start showing up in Office 365 Enterprise subscriptions in service updates starting in November and continue through to general availability.


All official announcements of RTM versions can be found here:

Microsoft re-releases update rollups for Exchange 2007 and Exchange 2010


Microsoft Re-Releases Exchange 2010 SP2 Rollup 4, Exchange 2010 SP1 Rollup 7, Exchange 2007 SP3 Rollup 8


After users complains Microsoft has re-released the latest rollups update for Exchange 2010 and Exchange 2007.

Last updates address an issue in which digital signatures on files produced and signed by Microsoft will expire prematurely.

This problem is described in:
Microsoft Security Advisory 2749655 


New version of Exchange 2010 SP2 rollup 4 also includes an additional fix:

2756987: Outlook only returns one result after you click the “Your search returned a large number of results. Narrow your search, or click here to view all results” message.


The updates can be found here:


As always we recommend to to test new rollups in Exchange test environment, and also to wait few days or weeks before install in Exchange production environment.




This problem is not common but quite annoying and usually hard to understood by users.

In most cases problem occurs If you remove mailbox and re-create it with the same AD account , for an example after firing and  re-hiring of the employee after some time.

It also occurs after migrations.

When user sends an email to a recipient, to which earlier messages was delivered without any problem. Sudennly gets an Non Delivery Report with this content:

Delivery has failed to these recipients or distribution lists:: 

Test User

The recipient's e-mail address was not found in the recipient's e-mail system. Microsoft Exchange will not try to redeliver this message for you. Please check the e-mail address and try resending this message, or provide the following diagnostic text to your system administrator..

Diagnostic information for administrators: 

Generating server:

#550 5.1.1 RESOLVER.ADR.ExRecipNotFound; not found ##

And now the question is: Why?

Continue reading

Exchange 2010 database create free space (white space)


Every mailbox database in Exchange 2010 has white space. It’s free space which can be used before .edb file will grow.

Sometimes we need to create free space in database right now if we want to avoid of growing of .edb file.

To get free space in mailbox database we can do the following:

  • move few mailboxes from mailbox database to other mailbox database
  • purge disabled mailboxes
  • purge soft-deleted mailboxes


Exchange 2010 check AvailableNewMailboxSpace (white space) in database:

We can check available white space for new mailboxes in mailbox databases using powershell like below:

Get-MailboxDatabase -server MBX1 | select Name, DatabaseSize, AvailableNewMailboxSpace

or if we want to check only one mailbox database:

Get-MailboxDatabase DB01 | select Name, DatabaseSize, AvailableNewMailboxSpace


If we want to see all disabled mailboxes (disabled today) in database we have to wait for scheduled Cleanup Agent or we can run it from powershell:

Get-MailboxDatabase -server MBX1 | Clean-MailboxDatabase

When we run above command, all mailboxes disabled today, will be marked as disabled and we can find them in Disconnected Mailboxes.


Exchange 2010 list disabled mailboxes:

We can get informations about disabled mailboxes to know how much space we will get when we purge disabled or soft-deleted mailboxes.

To list all disabled mailboxes in all mailbox databases in server MBX1 run:

Continue reading

Oultook 2010 Autocomplete problem


Very often we meet with Microsoft Outlook autocomplete problem.

In previous versions of Outlook like 2007, autocomplete file was stored in .nk2 file in user profilename.

Outlook 2010 doesn’t use the .nk2 file anymore for maintaining your nickname cache.

With Outlook 2010 and Exchange 2010, autocomplete cache is stored with user mailbox in a hidden message.
This lets the cache roam with your Exchange mailbox so that you have to access to your cache on any client you use to access your mailbox.


But sometimes Microsoft Outlook 2010 autocomplete doesn’t work.


Fix Microsoft Outlook 2010 Autocomplete function:

You can try to fix problem following the below steps:

First if you don’t want to lose your suggested contacts, export them from Outlook to some folder on your computer.

Continue reading

Exchange 2010 list mailboxes with Full Access or Send As permissions assigned


In previous post Exchange 2010 Mailbox Folder Permissions we explained how to add permissions to mailbox or mailbox folder.

After a while, when you add permissions to mailbox you will forget mailbox, permissions and users.


Exchange 2010 get list of mailboxes with assigned permissions


If you want to get list of all mailboxes with assigned Full Access permisions you need to use example like below:

Get-Mailbox -Server “MX01” -ResultSize Unlimited | Get-MailboxPermission | where {($_.AccessRights -eq “FullAccess”) -and ($_.IsInherited -eq $false) -and ($_.User.ToString() -ne “NT AUTHORITY\SELF”)}

Above example will list all mailboxes on server MX01 and check assigned permissions to those mailboxes. If any of those mailboxes will have assigned Full Access permission which is not Inherited and permission is not for user “NT Authority\Self” (it means for mailbox owner) then you will receive list of mailboxes with user account name and permissions.


We can also check belowed permissions instead of Full Access:

Continue reading

Exchange ActiveSync problems after upgrading IPhone or IPad to iOS6


Lot of users reports problems with Exchange ActiveSync after upgrading IPhone or IPad to iOS6.

If you have IPhone or IPad and you upgrade your device to iOS 6, then if you want to create new ActiveSync profile on your device it fail.
The new iOS 6 has problem with populate all fields required for automatic profiles setup.

But if you already have a ActiveSync profile on your IPhone/IPad and then upgrade to iOS 6, everything works fine.

There is also another bug iOS6 with Exchange meeting invitations.

The issue appear when user with iOS 6 decline a meeting invitation.
After user decline, iOS 6 is sending meeting cancellation notices to the entire distribution list, what causes canceling the invitation for all attendees.

So users with iOS 6 are being asked no to accept or decline calendar appointments until the problem has been resolved.

Some companies are requesting theirs emloyees not upgrade to iOS 6 until a bug with Microsoft Exchange meetings invitations will be fixed.