Another 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:

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

But 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).

(more…)

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:

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:

It gets even worse when we open the Message:

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

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:

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

(more…)

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:

(more…)

I am currently working on a migration project from Exchange 2003 to Exchange 2010.

Most Exchange migration projects use Mailbox Moves to move the mailbox data to the new Exchange environment.

But there are some things I observed during Mailbox Moves (from Exchange 2003 to 2010) that are worth mentioning.

(more…)

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.

(more…)

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:

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:

(more…)

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.

(more…)

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

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

I remembered from a Tweet by Helge Klein recently that the Active Directory schema has no mechanism for enforcing uniqueness of an attribute.

(more…)