Friday, 22 January 2016

UNABLE TO REMOVE LAST MAILBOX IN EXCHANGE 2010


We are planning to remove our Microsoft Exchange 2010, mailbox server. During the installation process, we get the error below:

Error:
This mailbox database contains one or more mailboxes, mailbox plans, archive mailboxes, or arbitration mailboxes. To get a list of all mailboxes in this database, run the command Get-Mailbox -Database <Database ID>. To get a list of all mailbox plans in this database, run the command Get-MailboxPlan. To get a list of archive mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Archive. To get a list of all arbitration mailboxes in this database, run the command Get-Mailbox -Database <Database ID> -Arbitration. To disable a non-arbitration mailbox so that you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID>. To disable an archive mailbox so you can delete the mailbox database, run the command Disable-Mailbox <Mailbox ID> -Archive. Arbitration mailboxes should be moved to another server; to do this, run the command New-MoveRequest <parameters>. If this is the last server in the organization, run the command Disable-Mailbox <Mailbox ID> -Arbitration -DisableLastArbitrationMailboxAllowed to disable the arbitration mailbox. Mailbox plans should be moved to another server; to do this, run the command Set-MailboxPlan <MailboxPlan ID> -Database <Database ID>.


Based on our experience during removing/clean up all the mailbox users and this is the last database that we unable to remove, so it's may because of the mailbox arbitration. To verify, just run the command as below:

Get-Mailbox -Arbitration -Database <databasename>

 

After verified, run the command to disable last arbitration mailbox, as below:

Get-Mailbox -Arbitration | Disable-Mailbox -Arbitration -DisableLastArbitrationMailboxAllowed



To confirm choose A to Yes to all.  After that we can manually remove the last mailbox and uninstall the mailbox server.

Thursday, 18 June 2015

EXPORT LIST ALL COMPUTERs IN ACTIVE DIRECTORY WITH STATUS LAST LOGON DATE

1.  Go to Administrative Tools > and select the Active Directory Module for Windows PowerShell.
2.  On the Active Directory Module for Windows PowerShell run the command syntax as below;
Get-ADComputer -Filter * -Properties * | FT Name, LastLogonDate –Autosize
3.  We will get the result as screen capture as below;
Name     LastLogonDate
----     -------------
MHI-DC01 6/12/2015 4:03:07 PM
MHI-CM07 6/12/2015 4:12:52 PM

Sunday, 14 June 2015

RESTORE DELETED OBJECT USING ADRESTORE TOOL

In my situation, I accidentally delete the OU in Active Directory in Windows Server 2008 R2 with Windows Server 2003 for Domain functional Level.

1. Download and extract the ADRestore file from Microsoft Sysinternal to Domain Controller.  May download from this URL https://technet.microsoft.com/en-us/sysinternals/bb963906.aspx 
2. At Domain Controller server run CMD adrestore /r
3. Verify the attribute to restore, press Y to restore and Done.

Friday, 8 May 2015

EXCHANGE 2010 PERFORMANCE SLOW WITH CPU UTILIZATION 100% [SOLVED]

I was facing this issue for the last two days ago, one of my customer complained one of their exchange mailbox server performance slow and the CPU utilization is 100%. Our customer is using VMware and all the VMs server running on top of the VMware.

When checking on the server that has performance issue, I found out all the services running as usual, the fail-over cluster up and running, but the connectivity to this server seems very slow.  When open the EMC we got this error below;

Processing data for a remote command failed with the following error message: The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exception for Windows Remote Management service is enabled. For more information, see the about_Remote_Troubleshooting Help topic.

After deeply checking with the VMware team, we found out that both exchange mailbox servers require to perform Disk Consolidation. It is because their backup for VMware has a problem and too many "VM snapshot" created for these two servers and its impact to server performance. After the VMware team finished performing the disk consolidation, the issue has resolved and the mailbox server back to normal.