After downloading and attempting to install the French language pack for Exchange 2010 UM I was less than pleased to the receive an error:

It took me a few moments to digest what was occurring but after reading the error (always a good start) and looking through the Exchange setup logs ([ERROR] Could not find a part of the path ‘C:SupportUM,Language,Packsfr-FR’), it would appear that if the Language Pack is in a folder that contains spaces it will not install.

If you look at the error above you will note that the spaces in my folder name have been replaced by comma’s ‘,’.

Resolution

Remove the spaces in the folder containing the Language Pack

Neil Cruickshanks

You may come across an issue where you need to Migrate Multiple Mailboxes in bulk, we’ve created a Exchange Powershell script which will move all users into there targeted mail stores.

Instructions

Before we run this powershell script  we need to create a csv file with the users display name and there targeted exchange database, to do this see below.

1, open notepad.exe

2, now write the following text on your first line in notepad “user,database” (without quotation marks)

3, Go to the next line and then type a users name  first and then add a comma and finally type the desired store.

4, You should end up with a list like below with all the users you want to import

user,Database
Jovan Davis,Store 3
Daniel Davies,Store 2
Hardeep Bains,Store 1

5, Finally save the file as a csv file and name it “MM.csv” in the following directory “C:MailboxMove””

6, Now open notepad again and copy all the below text into it. Finally save this as a PS1 file and run this via the Exchange management Shell.
_________________________________________________________________________

$Userstodatabase = import-csv C:MailboxMoveMM.csv
foreach ($Record in $Userstodatabase)
{
$users = $record.user
$database = $record.database
New-MoveRequest –identity $users –TargetDatabase “$Database”
}

____________________________________________________________________________

This will now move the mailboxes

If you want to check the status if the moves simply copy the below script into a PS1 file and run it from the exchange shell and it will list the progress of all users mailboxes specified in the CSV.

____________________________________________________________________________

$Userstodatabase = import-csv C:MailboxMoveMM.csv
foreach ($Record in $Userstodatabase)
{
$users = $record.user
Get-MoveRequest –identity $users
}

___________________________________________________________________________ 

Hope this helps

Daniel Davies

Now you may have the issue where the green arrow which means “move request” is by a mailbox you want to move and if you try to move the mailbox you will notice you don’t have the option to move the mailbox.

This is because the mailbox has been moved before and you must clear the previously completed move request to enable you to move the mailbox again.

So if we go to Move request tab and simply clear the move request of the mailbox we want to move, we will then have the option to move the mailbox

Daniel Davies

When migrating a mailbox to Exchange 2010 i came across an issue, where every time i tried to move the specific mailbox i got the below error.

Property Expression “User name” isn’t valid. Valid values are : Strings that includes ‘@’, where ‘@’ cannot be the last character.

Resolution

 The username i was trying to move did not have an @ sign in his name so i didn’t see why this was failing, so this prompted me to look at the users account in AD.

I viewed the properties of the user account and then i checked the account tab, and i spotted there was no domain name specified in the user login name, which would explain why exchange was seeing it as “username@” so i added the domain entry in and then retried the move via exchange and it worked fine

Hope this helps.

Daniel Davies

We came across an error today when we were trying to move a mailbox from Exchange 2003 onto Exchange 2010 which was stopping us moving the mailbox.

Active Directory operation failed on DC. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150A45, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0

1, Open Active Directory Users and Computers and View advanced features

2, Find the user account for the mailbox with the issue and go to the properties of this account

3, Go to the security tab and hit advanced

4, Now check the box that says include inheritable permission and apply this setting.

5, Now rerun the mailbox this move, this will fail but we are just running this to obtaining the CMDLET to cancel our previous move.

6, Run the remove request that you get displayed in the exchange console

Error:
The queue in “Store Name” database already contains a move request for ‘User’, while AD reports the mailbox as not being moved. It is possible that someone created this move request recently, while targeting a different domain controller, and AD replication did not yet occur. You can examine this move request by running ‘Get-MoveRequestStatistics -MoveRequestQueue ‘Store Name’ -MailboxGuid 4b525a83-cdc7-421b-84e1-ea6291cdd6d7 -IncludeReport | fl’. If you believe this to be an abandoned move request, you can remove it by running ‘Remove-MoveRequest -MoveRequestQueue ‘Store 3 Name’ -MailboxGuid 4b525a83-cdc7-421b-84e1-ea6291cdd6d7′.

Elapsed Time: 00:00:00

Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:01

7, Now Re-Run the mailbox move and this will complete

Daniel Davies

You may come across an issue where you need to import multiples PST’s into users mailboxes but you don’t want to do it manually, if that the case you’ve came to the right place

First thing to do is  install outlook 2010 on your exchange server.

Once this is done you can use Rob’s (http://risualblogs.com/blog/author/robb/) Powershell command to automate this.

Follow the below instructions to help you achieve the bulk PST imports you need.

Instructions

Before we run this powershell script we will first need to place all the PST’s locally on the server we are doing the imports on (Mailbox Server) which is simple enough.

And finally before running this script we need to create a csv file, to do this see below.

1, open notepad.exe

2, now write the following text on your first line in notepad “mailbox,pst” (without quotation marks)

3, Go to the next line and then type a users mailbox  first and then add a comma and finally type the name of the users pst.

4, You should end up with a list like below with all the users you want to import

mailbox,pst
Daniel1,Daniel1.pst
Dan,Dan.pst
Daniel,daniel.pst

5, Finally save the file as a csv file and name it “pstlocations.csv”

6, Now open notepad again and copy all the below text into it. Be sure to only change the three values I’ve made bold and you can change the directory they are pointing to, to suit your environment and also you can change what you want to import into the mailbox by altering the IncludeFolders switch (currently only importing Contacts and Calendar items). Finally save this as a PS1 file and run this via the Exchange management Shell.
_________________________________________________________________________

###Script to import calendar and contact items from pst’s to mailboxes

#set this to the path containing the pst files

$pstfolderpath = “c:psts”

$users = import-csv ‘C:pstlocations.csv’

#dont change below this line

foreach ($record in $users)

{

            $filelocation = $pstfolderpath + $record.pst

            $mailbox = $record.mailbox

            Write-Host -foregroundcolor “green” “Importing” $filelocation” to mailbox” $record.mailbox

            $command = “import-mailbox -Identity $mailbox -PSTFolderPath $filelocation -IncludeFolders ‘Contacts’, ‘Calendar’”

            invoke-expression $command

}

____________________________________________________________________________                                                                                             

Hope this Helps

Daniel Davies

We came across an issue recently in Exchange 2010 where i needed to import a user PST into there mailbox, however when we tried to run the command from the Exchange Shell to do this it just came up with the following error code.

Command

Import-mailbox –identity Test –PstFolderPath C:PSTS

Error Code

Error occurred in the step: Approving object

An unknown error had occurred., error code: -2147221219

 Basically our issue was that there was no HOMEMDB attribute set for the System Attendant on each Exchange server.

Resolution

1, Open ADSIEDIT and connect to the configuration partition

2, Now we need to drill down into the AD database, expand configuration.

3, Expand CN=Services and then expand CN=Microsoft Exchange and CN=<Domain name>

4, Expand CN=Administrative Groups and then Exchange Administrative Group(FYDIBOHF23SPDLT)

5,Expand CN=Servers and mailbox server you are trying to import on.

6, Now right click CN=Microsoft System Attendant choose properties and check for the homeMDB Value

7, If the Value is set to <not set> here lies our problem.

8, To Find the value to add into the MDB attribute , simply press CN=Databases which is just above the CN=Servers you located to.

9, Now if you choose any storage group and press properties and then view and copy the value for Distinguished name for this storage group

10, Now place the value you just copied into the HomeMDB attribute  to overwrite the not set value and apply this.

11, Give the domain some time to replicate this change and then restart the mailbox servers Information Service

12, You should now be able to import PST’s into the users mailboxes

13, It would be a good idea to add the distinguished name value you copied into every mailbox servers HOMEMDB attribute.

Hope this Helps You Out

Daniel Davies

Currently at this point in time you will be unable to monitor your Exchange 2010 environments via SCOM R2. If you install the MP you will come across the below errors and if you go install the required KB you will hit a problem as this update has not current been released.

“Critical hotfixes required for reliable operation of the Exchange Server 2010 and other management packs are not installed on this server. Please see the appropriate KB article for more information, and to download the required hotfix.

For Operations Manager 2007 SP1, install KB 971541 (http://go.microsoft.com/fwlink/?LinkID=167911)

For Operations Manager 2007 R2, install KB 974144 (http://go.microsoft.com/fwlink/?LinkID=167912 “ 

This is Due to the KB update for SCOM R2 currently not being released, so for the time being you will not be able to monitor your Exchange 2010 environments via SCOM R2.

After speaking to Microsoft the KB should be released before the new year.

Thank You

Daniel Davies