Oct 13

Exchange 2010: Loadbalancing Relay Connector

Remko WeijnenComments Off on Exchange 2010: Loadbalancing Relay Connector

Exchange Logo

On an Exchange 2010 environment I needed to allow smtp relaying for specified hosts. The procedure for doing this is explained clearly in the Exchange 2010 documentation.

So I created a relay connector on all servers with the HT role and since we are using Virtual Loadbalancing appliances from LoadBalancer.org to loadbalance the HT and CAS roles I wanted the relay connectors to be loadbalanced as well.

So how do we configure this?

Continue reading »

Oct 04

Exchange Move Mailbox Experiences Part 5

Remko WeijnenComments Off on Exchange Move Mailbox Experiences Part 5

imageAnother interesting Move Mailbox error and in this case I am really unsure how this would be possible!

Let’s look at the Move Mailbox log:

1-10-2011 11:49:18 [The Exchange Server] A corrupted item was encountered during the move operation. The item wasn't copied to the destination mailbox.

  Top of Information Store
  John Doe
  
  archive.pst
  IPM.Document.PSTFile
  38621879
  01/19/2006 14:30:57
  01/19/2006 14:30:19
  Message (size 36.83 MB (38,621,879 bytes)) exceeds the maximum allowed size for submission to the target mailbox. You can increase this limit by using the Set-Mailbox cmdlet in the Exchange Management Shell.
Error details: MapiExceptionMaxSubmissionExceeded: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80004005, ec=1242)

This error occurs because of a size constraint just like the one in the previous part.

imageBut the strange part is that it seems to be a PST file (type IPM.Document.PSTFile) located in the Root folder of the Exchange mailbox (which is not possible AFAIK).

 

Continue reading »

Oct 04

Exchange Move Mailbox Experiences Part 4

Remko WeijnenComments Off on Exchange Move Mailbox Experiences Part 4

The previous part (part 3) addressed Mailbox Size but did you know that even Message Size (or rather Item size) can prevent a successful move as well?

Here’s an example move mailbox log:

2-10-2011 3:18:58 [The Exchange Server] A corrupted item was encountered during the move operation. The item wasn't copied to the destination mailbox.

  verzonden nov 2004-aug 2005
  Jane Doe
  
  Foto's afscheid John Doe 10 februari jl.
  IPM.Note
  76121694
  02/15/2005 15:28:06
  02/15/2005 15:28:06
  Message (size 72.6 MB (76,121,694 bytes)) exceeds the maximum allowed size for submission to the target mailbox. You can increase this limit by using the Set-Mailbox cmdlet in the Exchange Management Shell.
Error details: MapiExceptionMaxSubmissionExceeded: IExchangeFastTransferEx.TransferBuffer failed (hr=0x80004005, ec=1242)
Diagnostic context:

As you can see in the log this mailbox there is one item with a size of 72 MegaBytes.

Let’s see this in Outlook:

image

It gets even worse when we open the Message:

image

It was addresses to several internal recipients and as you know Exchange 2010 no longer supports Single Instance Storage

Sep 28

Exchange Move Mailbox Experiences Part 3

Remko WeijnenComments Off on Exchange Move Mailbox Experiences Part 3

In Part 2 I showed some details about Mailbox Rule corruptions that can disturb Mailbox Moves.

For this part the topic is Mailbox size, which can be an important factor in deciding which mailboxes you want to move first.

In my case the mailbox size was important because we agreed to move smaller mailboxes during the day but larger mailboxes only outside working hours.

For Exchange 2010 mailboxes it’s very easy to obtain the size using PowerShell.

Example:

Get-Mailbox "rweijnen" | Get-MailboxStatistics | select DisplayName, ItemCount, TotalItemSize
DisplayName ItemCount TotalItemSize
Remko Weijnen 313 34.87 MB (36,564,183 bytes

But how can we get the Mailbox Size for Exchange 2003 mailboxes?

 

Continue reading »

Sep 27

The case of the mailbox validation error

Remko WeijnenComments Off on The case of the mailbox validation error

Today I noticed a strange warning when opening a mailbox:

WARNING: The object domain.local/Productie/Users/SomeOU/LoaderA0001 has been corrupted, and it's in an inconsistent state. The following validation errors happened:
WARNING: Property expression "LoaderA0001" isn't valid. Valid values are: Strings that includes '@', where '@' cannot be the last character

 

Continue reading »

Sep 27

Exchange Move Mailbox Experiences Part 2

Remko WeijnenComments Off on Exchange Move Mailbox Experiences Part 2

In part 1 we saw that a corrupted rule made the Mailbox Move fail.

I wanted to know if I had really a corrupted mailbox or maybe even corruption in the store or another problem.

So in this part I will describe how to break down the Mailbox Move Log.

First go to the Failed Move Request and select Properties:

image

 

Continue reading »

Sep 27

Cannot open Mailbox as Additional Mailbox

Remko WeijnenComments Off on 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

 

 

Continue reading »

Aug 17

Cannot achieve Exchange Server authentication

Remko WeijnenComments Off on 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.

Continue reading »

Aug 16

Get smallest Exchange Database in PowerShell

Remko WeijnenComments Off on Get smallest Exchange Database in PowerShell

SNAGHTML1ca684c

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()
Aug 15

Set Exchange Product Key with PowerShell

Remko WeijnenComments Off on Set Exchange Product Key with PowerShell

SNAGHTML1ca684c

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:

image

Continue reading »