John Yassa's Blog

Home » Posts tagged 'exchange 2010'

Tag Archives: exchange 2010

Litigation Hold vs In Place Hold

In the previous versions of Exchange (Exchange 2010) and Exchange online (Office 365) previous service version , the term litigation hold is introduced

Litigation Hold , is to allow you to immutably preserve mailbox content to meet long term preservation and eDiscovery requirements. When a mailbox is placed on Litigation Hold, mailbox content is preserved indefinitely.

In the new version of Exchange (Exchange 2013) and Exchange online (Office 365) existing service version , a new term has been released which is In Place Hold

In Place Hold, is called query-based and time-based In-Place Hold for the mailbox

After the release of Exchange 2013 and the new Exchange Online, there were some documentation that mentioned that Litigation Hold was being deprecated , this is not true and both terms are available 

Both types are available for use and you should use the hold feature that best meets your needs.  Here are some scenarios to help you choose between the two holds.

 image_050D85EA

 

Source : TechNet Blogs

 

Increasing the amount of concurrent mailbox moves in Exchange 2010

Exchange 2010, by default, allows you to do 2 concurrent mailbox moves.  This is a rather conservative approach, in this age of 10 Gb Ethernet and super-fast SAN storage.  Fortunately Microsoft has provided a mechanism whereby we can increase the amount of concurrent moves allowed.

This can be re configured by editing the MSExchangeMailboReplication.exe.config file, which resides under the C:\Program Files\Microsoft\Exchange Server\V14\Bin\ folder.

Attribute values:

MaxActiveMovesPerSourceMDB: This property indicates the number of mailboxes that can be moved on the source mailbox database at one time. The default value is 5 concurrent moves.

MaxActiveMovesPerTargetMDB: This property indicates the number of mailbox moves that can be moved on the target mailbox database at one time. The default value is 5 concurrent moves.

MaxActiveMovesPerSourceServer : This property specifies the total number of tasks MRS can perform that include the server as a data source. You can specify a value from 0 through 1000. The default value is 50 concurrent moves.

MaxActiveMovesPerTargetServer: This property specifies the total number of tasks MRS can perform that involve the server as a data target. You can specify a value from 0 through 1000. The default value is 5 concurrent moves.

MaxTotalMovesPerMRS: This property specifies the total number of tasks that a single instance of MRS can perform at a time. You can specify a value from 0 through 1000. The default value is 100 concurrent moves.

Don’t forget to restart the Microsoft Exchange Mailbox Replication service and do this configuration change on all your CAS servers

Reference :  http://technet.microsoft.com/en-us/library/ff963524.aspx

Exchange 2010 SP3

The Exchange Team is pleased to announce that in the first quarter of calendar year 2013 we will be releasing Exchange Server 2010 Service Pack 3 (SP3) to our customers. With SP3, the following new features and capabilities will be included:

Coexistence with Exchange 2013: Customers that want to introduce Exchange Server 2013 into their existing Exchange 2010 infrastructure will need the coexistence changes shipping in SP3.

Support for Windows Server 2012: With Service Pack 3, you will have the ability to install and deploy Exchange Server 2010 on machines running Windows Server 2012.

Customer Requested Fixes: All fixes contained within update rollups released prior to Service Pack 3 will also be contained within SP3. Details of our regular Exchange 2010 release rhythm can be found in Exchange 2010 Servicing.

In order to support these newly added features, there will be a requirement for customers to update their Active Directory schema. We are communicating the required changes ahead of the release date in order to assist our customers with planning their upgrade path ahead of time.

We hope these announcements come as welcome news to you. It is our custom to provide ongoing improvements to features, functionality and security of Exchange Server, based largely on customer feedback, and to provide continual innovation on an already great messaging product. We look forward to receiving your comments and announcing more detailed information as we continue to develop the features that will be included in SP3.

To try Exchange 2010 SP3 , follow the below URL
http://www.microsoft.com/en-us/download/details.aspx?id=36768

Enjoy

Get mailboxes with mailboxes grater than 1 GB in size

You can run the below command to get the Display Name and the size of the mailbox only and export them to TXT file named result in the path c:\result.txt
get-mailbox -resultsize unlimited | Get-MailboxStatistics | Where {$_.TotalItemSize -Gt 1GB} | Sort-Object -Property TotalItemSize -Descending | Format-Table DisplayName, TotalItemSize >c:\result.txt

You can run the below command to get all the Mailbox info and export them to TXT file named result in the path c:\result.txt
get-mailbox -resultsize unlimited | Get-MailboxStatistics | Where {$_.TotalItemSize -Gt 1GB} | Sort-Object -Property TotalItemSize -Descending | Fl >c:\result.txt

How to remove default mailbox database in Exchange 2010

Most of us as messaging administrators want to delete the default created mailbox database with any new exchange mailbox server

If you tried to delete this default database in normal way you will face the below error
1

So what to do to delete the default database!!!!!!!

below is the steps needed to delete the default database:

  1. Moving Arbitration Mailboxes (System Mailboxes , FederatedEmail) & Discovery mailbox

Get-Mailbox -Arbitration -Database “Mailbox Database 1973945018”
you will get the below result
getarbitration

Now moving this arbitration mailboxes to another DB (MailboxDB) using the below Command
Get-Mailbox -Arbitration -Database “Mailbox Database 1973945018” | New-MoveRequest -TargetDatabase MailboxDB
movearbitration

Now to move the Discovery mailbox , use the Exchange Mangement Console as below
movediscovery

Once all moves are complete, you can remove the move request from the Exchange management console
removemoverequest

2. Move Mailboxes exist on this Mailbox Database

you can do that by the following command :
Get-Mailbox -Database “Mailbox Database 1973945018” | New-MoveRequest -TargetDatabase MailboxDB
movemailboxes

3. Move any archiving mailboxes exist on this DB

Now get all archiving mailboxes and thier corrosponding DBs
Get-mailbox -archive | fl identity,database

Now move these archiving mailboxes to any other DB
Get-Mailbox -Archive | New-MoveRequest -ArchiveTargetDatabase ‘Mailbox Database’ -ArchiveOnly

4. Now you can delete the default Mailbox Database safely without any problem

Moving bulk mailboxes

How to move bulk mailboxes from one database to another one

There are more than one way to move mailboxes to another database:

1- Move all mailboxes in one database to another database, then you can use the command below, this will move all mailboxes from DB “Source mailbox DB” to “Destination Mailbox DB”

Get-Mailbox –Database ‘Source Mailbox DB’ | New-MoveRequest –TargetDatabase `  ‘Destination Mailbox DB’

2- Move few mailboxes, you can use the below command
$Mailboxes is an array containing the names of three mailbox
Each mailbox is passed into the New-MoveRequest cmdlet for processing not concerning the source mailbox DB

$Mailboxes = ‘john’,’nassan’,’yassa’

ForEach ($SingleMailbox in $Mailboxes) {New-MoveRequest –Identity $SingleMailbox ` –TargetDatabase ‘Destination Mailbox DB’ –BatchName Batch01}

3- Using CSV file, like the below where ID is the column header and use the below command

Import-CSV ./mailboxes.csv | foreach {New-MoveRequest -Identity $_.ID – TargetDatabase “Destination Mailbox DB“}

This will work regardless the source Mailbox DB

mailboxes-csv

Update Rollup 5 version 2 for Exchange Server 2010 Service Pack 2 is now aviliable

Microsoft has released Update Rollup 5 version 2 for Microsoft Exchange Server 2010 Service Pack 2 (SP2). This update is dated December 11, 2012.

Issues that the update rollup resolves

Update Rollup 5 version 2 for Exchange Server 2010 SP2 addresses the vulnerabilities that are described in Microsoft Security Bulletin MS12-080

. This update also resolves the issues that are described in the following Microsoft Knowledge Base (KB) articles:

For more information http://support.microsoft.com/kb/2785908

Find The Total Number Of Mailboxes In Your Domain

How can you quickly find the total number of mailboxes in your Domain? You can do it now by running a shell command.

Get-Mailbox -ResultSize unlimited | Measure-Object

You can further customize the command to your  requirements. Let’s say that you want to find out the mailboxes in one particular database or one particular server. You can find it by adding more switches to the above command. Run the following…

Get-Mailbox –database dbname -ResultSize unlimited | Measure-Object

Get-Mailbox –Server servername -ResultSize unlimited | Measure-Object

550 5.7.1 RESOLVER.RST.AuthRequired; authentication required

When you Send to DL in Exchange 2007 or Exchange 2010 , you recieve the error 550 5.7.1 RESOLVER.RST.AuthRequired; authentication required

Reason:
By default Exchange 2007 or Exchange 2010 requires that a sender be authenticated before being able to successfully send to a distribution list. Consequently external users are unable to send emails to it.

Solution:
1- From the properties of the distribution list in Exchange AD: Exchange General tab, Un-tick From authenticated users only
2- From the properties of the distribution list in Exchange Management Console: Mail-flow settings tab, Message Delivery Restrictions, un-tick Require that all senders are authenticated.

 

Exchange Mangement console shows error “the ws-management service cannot process the request, the system load quota of 1000 request per 2 seconds has been exceeded” when you open it

When you open Exchange Management Console , it refuse to load and shows the following error “The WS-Management service cannot process the request. The user load quota of 1000 requests per Z seconds has been exceeded. Send future requests at a slower rate or raise the quota for this user. The next request from this user will not be approved for at least Z milliseconds”

after search, an IISRESET or IISRESET /NOFORCE just solved my probelm and i could browse the Exchange Management Console normally

 

%d bloggers like this: