Exchange Server | Murat Bilici

"Empower your knowledge"

Action ‘Update’ could not be performed on object ‘Default Offline Address List’

I attempted to use the ‘update’ OAB function in the Exchange 2010 Management Console. Basically you can look at all your OABs

and select the one you want (we only have one), right click and select ‘update’.

When I did this it threw back this error:
————————–———-———-———- Microsoft Exchange Error ————————–———-———-———-

Action ‘Update’ could not be performed on object ‘Default Offline Address Book’.

Default Offline Address Book Failed Error: Couldn’t find database “DOMAINNAME.local/Configuration/Deleted Objects/Public Folder Store (OLD EXCHANGE 2003 SERVER) DEL:ec77c3ad-4128-46d6-9bc0-176b67d717bc”. Make sure you have typed it correctly.

————————–———-———-———- OK ————————–———-———-————————-———-

To fix this:

a) Open Adsiedit.msc

b) Browse to Configuration, Services, Microsoft Exchange, , Address List Container, Offline Address Lists

c) Open properties of the Default Offline Address List on the right

d) Change siteFolderServer attribute to the DN of the correct Public Folder e.g.

CN=Public Folder Database,CN=Databases,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=MAIL,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=CONTOSO,DC=com

1 Mart 2013 at 09:10 - Comments

Cannot Send E-Mail To A Mail Enabled Public Folder

I was recently assisting a colleague with an issue he had experienced with a Microsoft Exchange 2003 to Microsoft Exchange 2010 migration. The migration had completed correctly, however for an unknown reason you could not send e-mail to any mail-enabled public folders, despite whether these were created newley from within the Exchange Management Console or were replicated as a part of the migration. All of the mail-enabled public folder properties were correct, including permissions, and Exchange 2010 Service Pack 1 had also been applied. When e-mailing a mail-enabled public folder from an external network no NDR was produced, however when e-mailing from the internal network the following NDR was returned:

#554 5.2.0 STOREDRV.Deliver.Exception:ObjectNotFoundException; Failed to process message due to a permanent exception with message The Active Directory user wasn’t found. ObjectNotFoundException: The Active Directory user wasn’t found. ##

After performing some research it turned out this is a known problem with Exchange 2010 migrations as detailed here. The issue occurs due to the legacy administrative group (First Administrative Group) being empty following the migration. To resolve this issue perform the following actions:

1. Open ADSI Edit on either a domain controller or your Microsoft Exchange 2010 server.

2. Navigate to the “CN=Servers” ADSI attribute by locating the below path, I have also included a screenshot of the location to help identify the attribute:

CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration, DC=domain,DC=local


3. Right click the “CN=Servers” container and select delete. Click OK when prompted in order to confirm the action. Note: Do not delete the top level container “First Administrative Group”, this is against Microsoft best practices and may have a negative affect on your Exchange organisation.

4. Ensure replication of your Active Directory database has occurred to all domain controllers and then attempt sending an e-mail to one of your mail-enabled public folders. You should now find e-mail makes it way to these folders as expected.

For more information on this issue, please see the following URL:


5 Şubat 2013 at 19:52 - Comments

Unable to access Public folder via outlook in Exchange 2010 environment

“Cannot expand the folder. The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network problems or the Exchange is down for maintenance.”

Steps taken?

  • Verified that the Mailbox databases are pointing to correct Public Folder database.
  • Verified that the RPC Client access service is running on the CAS/HUB server.
  • Something hit my mind at this point, and I took a look at the “RPC Client access service” in the mailbox server, it was stopped.
  • I tried to restart it and bang!!! PF access thru outlook restored.
  • taskkill /f /pid xxx

Logic applied:

We know that “RPC Client access service” in the CAS/HUB servers do a lot of operations pertaining to managing client connections for exchange. But, why do we need this service in the Mailbox server?

“RPC Client access service” in the mailbox server is used for none other than public folder access. When the outlook client queries for Public folders, it directly connects to the PF server (You can view it by checking the “Connection status” from outlook). This request is taken care of by the “RPC Client access service” in the mailbox server. In any case if this service is stopped/Hung, then we may see the above problem.

30 Ocak 2013 at 11:43 - Comments

Update Rollup 5 for Exchange Server 2010 Service Pack 2

Microsoft released Update Rollup 5 for Exchange Server 2010 Service Pack 2.

Details about the rollup can be read here: Description of Update Rollup 5 for Exchange Server 2010 Service Pack 2:

I applied it a while back in my lab and nothing seem to be broke will now.

Download it here: Update Rollup 5 for Exchange Server 2010 Service Pack 2 :

You may also want to have this link handy with details on update rollups, versions and numbers:

Exchange Server and Update Rollups Build Numbers (en-US):

14 Kasım 2012 at 16:38 - Comments

Microsoft Exchange 2013 RTM Released

Here comes RTM of Microsoft Exchange 2013…

Just thought of letting you know that the latest version of Microsoft Exchange – Microsoft Exchange 2013 RTM version is out now and available for download:

You can download your copy here:

Once you click the link, you will be asked to sign in with your Hotmail or Live id.

2 Kasım 2012 at 20:55 - Comments

iOS 6 and Exchange meetings update resolved

Apple just released an update for iOS6 and claims issue with meetings stands resolved

iOS 6.0.1 Software Update:

Description shows:

This update contains improvements and bug fixes, including:

• Fixes a bug that prevents iPhone 5 from installing software updates wirelessly over the air
• Fixes a bug where horizontal lines may be displayed across the keyboard
• Fixes an issue that could cause camera flash to not go off
• Improves reliability of iPhone 5 and iPod touch (5th generation) when connected to encrypted WPA2 Wi-Fi networks
• Resolves an issue that prevents iPhone from using the cellular network in some instances
• Consolidated the Use Cellular Data switch for iTunes Match
• Fixes a Passcode Lock bug which sometimes allowed access to Passbook pass details from lock screen
Fixes a bug affecting Exchange meetings
Hopefully the famous User taking ownership of meetings is resolved now
1 Kasım 2012 at 21:26 - Comments

TMG 2010 SP2 Upgrade Error

I came across a “typical” Microsoft error while upgrading my TMG 2010 SP1 to SP2. I say typical because the error message is confusing and has no relation to the actual cause of the problem. Well, there is a relation and you will only understand it if you know the solution upfront.

The error below came up while upgrading TMG 2010 SP1 to SP2 (yes, it’s about time) in my lab.

“The upgrade patch cannot be installed by the Windows Installer service because the program to be upgraded may be missing or the upgrade patch may update a different version of the program”

The issue is that the TMG upgrade has to be performed in a specific order.

  • If you upgrade from TMG 2010 RTM to SP2, you need to upgrade to TMG 2010 SP1 first, then to SP1 Rollup1 and finally to SP2. You can’t jump any hop.
  • In my case, I had to upgrade 2010 SP1 to SP1 Rollup1 and then to SP2. You will get the same error even if you try to skip SP1 rollup 1.

Once the upgrade order was followed, I was able to run the SP2 setup.

List of Build Numbers for Microsoft Forefront Threat Management Gateway (TMG)


31 Ekim 2012 at 09:08 - Comments

Mailboxes not showing up in Disconnected Mailboxes

Ever experienced a disconnected mailbox, that doesn’t show up in Disconnected Mailbox, after the mailbox has be disabled or removed ? If you disable a mailbox within the Exchange Management Console or EMS and you for some reason want to reconnect it again, soon after. But are unable to find the disconnected mailbox within Disconnected Mailbox. There is a reason for it, it will show up in Disconnected Mailbox after the nightly maintenance. But it is possible to force this, like it was in Exchange 2003. The documentation for Exchange 2010 tell you otherwise, but it doesn’t always work that way:

The Disable-Mailbox cmdlet also performs the cleanup task on the individual mailbox, so the mailbox is disconnected immediately after this task completes. You don’t have to wait for nightly maintenance or run the Clean-MailboxDatabase cmdlet for the mailbox to be disconnected.

But still if it doesn’t show up in the Disconnected Mailbox, you can use the commands listed below. Get an overview of disconnected mailboxes on a certain server with this command:

Get-Mailboxstatistics -Server EXCH-MBX-01 | Where-Object { $_.DisconnectDate -ne $null } | FL DisplayName,LegacyDN,ItemCount,OriginatingServer -wrap
Get an overview of disconnected mailboxes on a certain database with this command:
get-mailboxstatistics -database “Mailbox Database” |where{$_.DisconnectDate -ne $null}| FL displayName,LegacyDN,ItemCount,OriginatingServer -wrap

Clean a certain mailbox database with this command:

Clean-MailboxDatabase “Mailbox Database”

Clean all databases with this command:

Get-MailboxDatabase | Clean-MailboxDatabase

31 Ağustos 2012 at 09:06 - Comments

Released: Update Rollup 4 for Exchange 2010 Service Pack 2

On August 13th 2012, the Exchange CXP team released Update Rollup 4 for Exchange Server 2010 SP2 to the Download Center.

This update contains a number of customer reported and internally found issues. See KB 2706690 Description of Update Rollup 4 for Exchange Server 2010 Service Pack 2 for more details.

In particular we would like to specifically call out the following fixes which are included in this release:

Note: Some of the following KB articles may not be available at the time of publishing this post.

  • New updates for August DST – Exchange 2010 – SP2 RU4 – Display name for OWA.
  • 2685001 Retention policies do not work for the Calendar and Tasks folders in an Exchange Server 2010 SP1 environment
  • 2686540 Exchange 2010 Messages are not delivered to Journal Mailbox
  • 2701162 Granting Full Mailbox Access Does Not Allow Full Details of Free/Busy To Be Displayed
  • 2724188 Information loss due to unexpected subject modification while copying a message in Outlook
  • 2743871 Stop Forefront services in RU setup so no manual steps are required
  • 2740358: MS12-058: Vulnerability in Microsoft Exchange Server WebReady document viewing could allow remote code execution: August 14, 2012
17 Ağustos 2012 at 12:22 - Comments

Exchange Server and Update Rollups Build Numbers (en-US)

Exchange Server Release dates

Product name Build number Date
Microsoft Exchange Server 2003 6.5.6944 6/30/2003
Microsoft Exchange Server 2003 SP1 6.5.7226 5/25/2004
Microsoft Exchange Server 2003 SP2 6.5.7638 10/19/2005
Microsoft Exchange Server 2007 8.0.685.24 12/9/2006
Microsoft Exchange Server 2007 8.0.685.25 12/9/2006
Microsoft Exchange Server 2007 SP1 11/29/2007
Microsoft Exchange Server 2007 SP2 8/24/2009
Microsoft Exchange Server 2007 SP3 6/20/2010
Microsoft Exchange Server 2010 14.0.639.21 11/9/2009
Microsoft Exchange Server 2010 SP1 8/24/2010
Microsoft Exchange Server 2010 SP2 12/4/2011


13 Ağustos 2012 at 14:28 - Comments