Skip to main content

How to delete the default database in Exchange 2010

 How to delete the default database in Exchange 2010


You’ll probably want to delete the default database that is created when you build a new Exchange 2010 server. So you’ve moved all the mailboxes that you can see to another database. And then you’ll remove the database.
But if you do try, then you’ll get the following message:

Key Error Messages

The mailbox database ‘Mailbox Database ’ cannot be deleted.
This mailbox database contains one or more mailboxes or arbitration mailboxes.
Cause

This is because there are hidden mailboxes.
Solution

Here’s how to find them, move them and then remove the database.
Find them

You’ll need to use the EMS, The Exchange Management Shell, for this.

  1. Use the Get-Mailbox – Database command as I have in the image below:
  2. You’ll see the SystemMailbox, as listed in the image above. You may see more than one mailbox in your listing.
  3. Copy the mailbox name(s) to notepad.


Move them

Still within the EMS…

  1. Use the New-MoveRequest command as seen in the image below, pasting back in the mailbox name you copied in the Find them steps above.
  2. If you need to move your arbitration\system mailboxes to a specific database, you could instead use the New-MoveRequest command but add the following switch:
    -TargetDatabase “Database_Name” as shown in the image below.
  3. When you do your move-request, Exchange will queue the move. In the background, Exchange 2010 will perform the move, just as it does for a move performed from EMC.
  4. Repeat step 1 or 2 if you have more mailboxes like this to move.
  5. Use Get-MoveRequest to check that the move has worked:

    You could do this within Move Request in the Exchange Management Console GUI, but you wouldn’t be able to confirm which database the mailbox had moved to.

Remove the database

Remove the database in the usual way in the Exchange Management Console.
I hope this has helped you.

Comments

Post a Comment

Popular posts from this blog

Calculate how much data can be transferred in 24 hours based on link speed in data center

  In case you are planning for migration via DIA or IPVPN link and as example you have 200Mb stable speed so you could calculate using the below formula. (( 200Mb /8)x60x60x24) /1024/1024 = 2TB /per day In case you have different speed you could replace the 200Mb by any rate to calculate as example below. (( 5 00Mb /8)x60x60x24) /1024/1024 =  5.15TB  /per day So approximate each 100Mb would allow around 1TB per day.
Post a Comment
Read more

Integration with vCloud Director failing after NSXT upgrade to 4.1.2.0 certificate expired

  Issue Clarification: after upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Issue Verification: after Upgrade from 3.1.3 to 4.1.2.0 observed certificate to be expired related to various internal services.   Root Cause Identification: >>we confirmed the issue to be related to the below KB NSX alarms indicating certificates have expired or are expiring (94898)   Root Cause Justification:   There are two main factors that can contribute to this behaviour: NSX Managers have many certificates for internal services. In version NSX 3.2.1, Cluster Boot Manager (CBM) service certificates were incorrectly given a validity period of 825 days instead of 100 years. This was corrected to 100 years in NSX 3.2.3. However any environment originally installed on NSX 3.2.1 will have the internal CBM Corfu certs expire after 825 regardless of upgrade to the fixed version or not. On NSX-T 3.2.x interna...
Post a Comment
Read more

Recreating a VMFS-3 or VMFS-5 partition table in ESXi 5.x

For this kind of issues you need to engage VMware support on this, following any part of this article could lead to more complex situation if not ran by an expert.   Symptoms Datastore does not mount because of a lost or overwritten partition table.   Purpose When a VMFS partition is created in ESX 3.x or ESX 4.x, it has a Master Boot Record (MBR) partition map. The MBR is written to the first 512 B block (LBA0) and contains the information where the (VMFS) partition starts and ends. ESXi 5.0 introduced VMFS-5, which uses a GUID partition table (GPT) for new datastores. When a VMFS-3 partition is created in ESXi 5.x and is later updated to VMFS-5, the original partition map (MBR) is maintained. If the partition information of a VMFS datastore is deleted or overwritten (for example, by a Windows system with direct access to the same disks), it is impossible to determine if the partition map was GPT or MBR. The only time you can be sure that a GPT partition map was used is if th...
Post a Comment
Read more