To import a PST file into a mailbox on Exchange 2010, you need to assign rights to a user account to import emails. Do so by running the following command (You can reference every command in this article with the links at the bottom):

New-ManagementRoleAssignment –Role “Mailbox Import Export” –User DOMAIN\Administrator

Run the following command on a mailbox server to import the PST (The share for -FilePath must have Read/Write permissions for the group Exchange Trusted Subsystem). While this example is for importing mail, the same rules apply for moving mailboxes using the New-MoveRequest command:

New-MailboxImportRequest -Mailbox <MailboxOrMailUserIdParameter> -FilePath "\\fileserver\usermail.pst"

By default, if there are any bad items in the PST, the import will fail with the following error message:

This mailbox exceeded the maximum number of corrupted items that were specified for this move request

To fix this, you must first remove the failed import request:

Get-MailboxImportRequest -Status Failed |  Remove-MailboxImportRequest

If I remember correctly when /hosting came out you could use the Add-MailboxPermission as the domain administrator. It seems now with a later rollup [correct me if I'm wrong] you can no longer use this command because it gives you errors such as:

 The operation on mailbox "host.local/Microsoft Exchange Hosted Organizations/****/user01" failed because it's out of the current user's write scope. The object 'host.local/Microsoft Exchange Hosted Organizations/****/user01' must be within the read scope before and after it's modified. Can't perform the save operation.

    + CategoryInfo          : NotSpecified: (host.local/Micr...S/checkrequests:ADObjectId) [Add-MailboxPermission], TaskInvalidOperationException
    + FullyQualifiedErrorId :7F410251,Microsoft.Exchange.Management.RecipientTasks.AddMailboxPermission

   To fix this issue you must run the powershell as the organization administrator instead of the domain administrator.

Below is how you can accomplish this using remote powershell:

• Launch Exchange Shell / Powershell
• Run:

$c = Get-Credential

$session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http:///powershell -Credential $c

Import-PSSession $session -AllowClobber

During the migration to Exchange 2010 you might have the need to keep your Exchange 2003 server up and running. This is a supported configuration but sometimes you can run into problems even though everything is technically configured correctly.

In our case our send connectors and routing group connectors were perfectly fine. Yet people on Exchange 2010 couldn’t email Exchange 2003 users via Outlook. Now the stranger thing was they could using OWA.

Well the problem had to do with Event ID: 9667:

Event ID: 9667

Type: Error

Category: General

Source: msgidNamedPropsQuotaError

Description: Failed to create a new named property for database “” because the number of named properties reached the quota limit (). User attempting to create the named property: . Named property GUID: . Named property name/id: .

So to fix the problem we had to goto the registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeIS\Private-*************

Next we modify the registry value: NonMapi Named Props Quota

Change the value from 8192 to 16384

Now Dismount and remount the store

 In order to remove an Organization from Exchange 2010 multi-tenant you must first delete all mailboxes from the organization. You can delete most of them through the ECP (Exchange Control Panel), but you will still be left with the administrator mailbox you are using, DiscoverySearchMailbox, and some others.

First you must find your organization you want to remove. You can do this by typing:

• Get-Organization

Next you want to remove all mailboxes from the organization. Like I said above you can delete most of them using ECP or you can remove all the mailboxes quickly by typing:

• Get-Mailbox-Organization"<ORG NAME HERE>"| Remove-Mailbox

Now that all mailboxes are removed you can type this to remove the organization: 

• Remove-Organization -Identity "<ORG NAME HERE>"

Give it a minute and you should be able to do another Get-Organization and notice that your organization is gone! I took a picture for your viewing pleasure: