Cannot open Mailbox as Additional Mailbox

After moving a mailbox from Exchange 2003 to Exchange 2010 a user reported that he was unable to open his mailbox.

I logged with an account with Full Mailbox permissions  and added this user’s mailbox as an additional mailbox in Outlook:

Open these additional mailboxes



Read more

Cannot achieve Exchange Server authentication

Exchange Logo

I was testing outgoing mail flow in my new Exchange 2010 setup, which should go from the CAS Servers to the Edge server in the DMZ.

After configuring the Edge subscription I noticed that outgoing mails got stuck in the queue with the following error:

451 4.4.0 Primary target IP address responded with: “451 5.7.3 Cannot achieve Exchange Server authentication.” Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts.

I verified that name resolution back and forth was ok and that I could communicate on port 25, 50389 and 50636.

Read more

Get smallest Exchange Database in PowerShell


I needed to adapt some scripts that create a user with mailbox for Exchange 2010. The existing scripts had a hardcoded database for new mailboxes.

I wanted the mailbox to be created in the smallest database, but how do we determine this?

For Exchange 2010 this is fairly easy using PowerShell:

# Add Exchange Snapins
if ((Get-PSSnapin | where {$_.Name -match "Exchange.Management"}) -eq $null) { Add-PSSnapin Microsoft.Exchange.Management.* }

# Get largest possible size
$size = [Microsoft.Exchange.Data.ByteQuantifiedSize]::MaxValue.ToBytes()
foreach ($db in Get-MailboxDatabase -Status)
	Write-Host "Database:" $db.Name "Size:" $db.DatabaseSize.ToBytes()

	# Is the Database smaller than previous smallest size
	if ( $db.DatabaseSize.ToBytes() -lt $size )
		# This database is smaller, store size and db
		$size = $db.DatabaseSize.ToBytes()
		$ExDB = $db

Write-Host "Smallest Database:" $ExDB.Name "Size:" $ExDB.DatabaseSize.ToBytes()

Set Exchange Product Key with PowerShell


By default Exchange 2007 and 2010 are installed in Trial mode so before going into production you need to enter the Product Key.

The Exchange Management Console will warn you if one or more servers are still in trial mode:


Read more

PowerShell script to set Exchange Static RPC Ports


I am currently working on an Exchange migration from 2003 to 2010. For the implementation of a load balancing solution for the CAS/HUB servers I needed to set Static RPC Ports for the RPC Client Access Service and the Exchange Address Book Service.

The procedure of changing these ports is described on the Technet Wiki: Configure Static RPC Ports on an Exchange 2010 Client Access Server

Since I am lazy I decided to do this with a PowerShell script that would automatically do this for all CAS/HUB servers in my 2010 environment.

Read more

Exchange 2010 Install-ADTopologyService 0x800706D

Exchange 2010 Logo

I got the following error while installing Exchange 2010: “There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)”

I looked up HRESULT 0x800706D9 which is defined in winerror.h as EPT_S_NOT_REGISTERED with the same error text.

I looked at the ExchangeSetup.log in C:\ExchangeSetupLogs and this indicates that the error occurs when the install-ADTopologyService cmdlet tries to add some rules to the firewall:

[07-04-2011 14:03:04.0111] [2] Beginning processing install-ADTopologyService
[07-04-2011 14:03:04.0189] [2] [WARNING] An unexpected error has occurred and a Watson dump is being generated: There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)
[07-04-2011 14:03:04.0189] [2] [ERROR] There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)
[07-04-2011 14:03:13.0751] [1] The following 1 error(s) occurred during task execution:
[07-04-2011 14:03:13.0751] [1] 0.  ErrorRecord: There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)
[07-04-2011 14:03:13.0751] [1] 0.  ErrorRecord: System.Runtime.InteropServices.COMException (0x800706D9): There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)
   at Interop.NetFw.INetFwRules.Add(NetFwRule rule)
   at Microsoft.Exchange.Security.WindowsFirewall.ExchangeFirewallRule.Add()
   at Microsoft.Exchange.Configuration.Tasks.ManageService.Install()
   at Microsoft.Exchange.Management.Tasks.InstallADTopologyService.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
[07-04-2011 14:03:13.0751] [1] [ERROR] The following error was generated when "$error.Clear();
          if (!(get-service MSExchangeADTopology* | where {$ -eq "MSExchangeADTopology"}))
        " was run: "There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)".
[07-04-2011 14:03:13.0751] [1] [ERROR] There are no more endpoints available from the endpoint mapper. (Exception from HRESULT: 0x800706D9)

Windows Firewall LogoThe Windows Firewall service was disabled, so I set it to Automatic, started it and enabled it and then the setup ran without errors

The case of the duplicate SID’s


I encountered another interesting error during Exchange 2010 installation today. During the Organization Preparation I got the following error:

The requested object has a non-unique identifier and cannot be retrieved.Active directory response: 0000219D: SvcErr: DSID-031A0FC0, problem 5003 (WILL_NOT_PERFORM), data 0

The setup.log doesn’t give us much more detailed info: Read more

Exchange 2010 well-known object entry install error

SNAGHTML1ca684cToday I was testing the installation of Exchange 2010 in a VMWare sandbox environment. We created the sandbox to test migration from a 2003 AD and Exchange environment to 2008 R2 with Exchange 2010.

We used a P2V to get real copies of the Active Directory and the AD upgrade to 2008 R2 was already tested.

But during the Exchange installation in the sandbox I got the following error:

The well-known object entry on the otherWellKnownObjects attribute in the container object CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=zorg,DC=local points to an invalid DN or a deleted object.  Remove the entry, and then rerun the task.

Read more

Migrating Pop3 Connector SBS 2003 to SBS 2008

After a migration of SBS 2003 to SBS 2008 i encountered some problems assigning a pop3 connect mailbox to an exchange user.
No (migrated )mail enabled users appeared in the drop down list.

Only new user who are created with the Windows SBS Console seem to populate the list.
One way to populate the list is changing the msSBSCreationState attribute on the user.
Just open adsiedit.msc and browse to the users you want to populate the list and click preferences.
Then go down to the msSBSCreationState attribute and click edit and fill in the value “Created”

Ok out of all windows and open up the pop3 connector console again.
You can now see the edited account(s) in the dropdownlist

Exchange 2003 Management Pack Storage Add-On

During an implementation of System Center Operations Manager (SCOM) a customer asked me how he can retrieve information about Exchange mailbox stores for trend analysis. Unfortunately the managemeng pack supplied by Microsoft does not collect the size of Mailbox Stores in the datawarehouse.

So I’ve created an add-on for the Microsoft Exchange 2003 Management Pack which adds a rule for collecting the size of Mailbox Stores.


Read more