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
So what to do to delete the default database!!!!!!!
below is the steps needed to delete the default database:
- Moving Arbitration Mailboxes (System Mailboxes , FederatedEmail) & Discovery mailbox
Get-Mailbox -Arbitration -Database “Mailbox Database 1973945018”
you will get the below result
Now moving this arbitration mailboxes to another DB (MailboxDB) using the below Command
Get-Mailbox -Arbitration -Database “Mailbox Database 1973945018” | New-MoveRequest -TargetDatabase MailboxDB
Now to move the Discovery mailbox , use the Exchange Mangement Console as below
Once all moves are complete, you can remove the move request from the Exchange management console
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
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
How to recover a crashed Exchange 2010 Server
Let us assume the functional exchange 2010 server got crashed due to hardware failure, here are the steps that need to build the server again. Showing up this in a demo will take long time and the steps mentioned will guide you to recover a crashed server.
- Arrange a new Server with the same operating system as like the failed server and assign the same drive letter for the databases and the log files directory
- Reset the Active Directory Account for failed server
- Install and configure the perquisites that are needed to install Exchange Server 2010
- Ensure the network connectivity and configure the new computer with the correct IP address same like the crashed one
- Join the new computer with the domain controller with the same computer name as a failed server
- Run the setup Mode:recoverserver
- Restore databases on the location of the new Disks, if needed replay the transaction logs
- If it is non mailbox servers, restore the configuration files from backup or from other servers like transport server customized configuration for Hub and External and Internal access URLs for Client Access Server etc.
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
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:
-
2707146
IRM-protected messages cannot be returned in search results if the messages are recorded and sent to an external contact in an Exchange Server 2010 environment
-
2710975
Some MAPI property objects in an ANSI .pst file contain unreadable characters if you import the file by using the “New-MailboxImportRequest” cmdlet
-
2712001
ExTRA.exe does not collect data if you select a scheduled task for a data collection in an Exchange Server 2010 environment
-
2712595
Microsoft Exchange RPC Client Access service crashes when you run the New-MailboxExportRequest cmdlet in an Exchange Server 2010 environment
-
2716145
Store.exe crashes on an Exchange Server 2010 mailbox server if a VSAPI based antivirus software is used
-
2717522
Microsoft Exchange System Attendant service crashes on an Exchange Server 2010 server when you update the OAB that contains a DBCS address list
-
2720017
An RBAC role assignee can unexpectedly change a DAG that is outside the management role group scope in an Exchange Server 2010 environment
-
2727802
Microsoft Exchange Replication service crashes intermittently when you try to move mailboxes from an Exchange Server 2003 server to an Exchange Server 2010 server
-
2733415
Event ID 1 is logged on the Exchange Server 2010 Client Access server in a mixed Exchange Server 2010 and Exchange Server 2003 environment
-
2733609
Email message and NDR message are not delivered if an email message contains unsupported character sets in an Exchange Server 2010 environment
-
2743761
DAG loses quorum if a router or switch issue occurs in an Exchange Server 2010 environment
-
2748766
Retention policy information does not show “expiration suspended” in Outlook Web App when the mailbox is set to retention hold in an Exchange Server 2010 environment
-
2748767
You receive an NDR message that incorrectly contains recipients of successful message delivery in an Exchange Server 2010 environment
-
2748879
You cannot access a mailbox by using an EWS application in an Exchange Server 2010 environment
-
2749075
A copy of an archived item remains in the Recoverable Items folder of a primary mailbox in an Exchange Server 2010 environment
-
2749593
Outlook logging file lists all the accepted and internal relay domains in the Exchange Server 2010 organization when you enable troubleshooting logging
-
2750293
Items remain in the “Recoverable Items\Deletions” folder after the retention age limit is reached in an Exchange Server 2010 environment
-
2750847
An Exchange Server 2010 user unexpectedly uses a public folder server that is located far away or on a slow network
-
2763886
“The operation failed” error in the Outlook client when you open a saved message from the Drafts folder and then try to send it in an Exchange Server 2010 environment
- Assume that you apply the Update Rollup 4 version 2 for Exchange Server 2010 SP2 (KB2756485), and then you apply the Update Rollup 5 version 1 (KB2719800). In this situation, when you try to run the Get-DatabaseAvailabilityGroup cmdlet, you receive the following error message:
WARNING: An unexpected error has occurred and a Watson dump is being generated: Could not load type ‘Microsoft.Exchange.Rpc.ActiveManager.AmDeferredRecoveryEntry’ from assembly ‘Microsoft.Exchange.Rpc, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’.
For more information http://support.microsoft.com/kb/2785908
