Move Exchange Mailboxes

Lots of reasons for moving, often because you want to delete one of the mailbox databases.

User Mailboxes

new-moverequest "joe bloggs" -TargetDatabase "Mailbox Database"
Get-MoveRequest | Get-MoveRequestStatistics

Arbitration Mailboxes

Get-Mailbox -Arbitration | New-MoveRequest -TargetDatabase "Mailbox Database"
Get-MoveRequest | Get-MoveRequestStatistics

Remove the completed Move Requests

Get-MoveRequest -MoveStatus Completed | Remove-MoveRequest

or if you have lots to do

Get-MoveRequest -MoveStatus Completed | Remove-MoveRequest -Confirm:$false


Additional Moves

You may also have to:

Get-Mailbox –RecipientTypeDetails DiscoveryMailbox | Format-Table Name

Get-Mailbox -RecipientTypeDetails DiscoveryMailbox | New-MoveRequest -TargetDatabase @Mailbox Database"

Get-MoveRequest | Get-MoveRequestStatistics

Get-MoveRequest -MoveStatus Completed | Remove-MoveRequest

To get a list of all Audit mailboxes in this database, run the command

Get-Mailbox -Database <Database ID> -AuditLog

To disable a Audit mailbox so that you can delete the mailbox database, run the command

Get-Mailbox -Database "Mailbox Database 2138967441"  -Auditlog | Disable-Mailbox



Once all moved, old DB can be removed. If you have created a new mailbox database, you will need to add new AV exclusions asper MS’s recommendations.

Installing ESXi 8 on old CPUs

Boot from USB in normal way.

At the initial ESXi Boot menu, press SHIFT-O (letter o)

Type: <space>allowlegacycpu=true and hit enter

Now, although you’ll be prompted during the install that the CPU is unsupported, it will let you continue.

Note – ESXi 8.0.2 will fail to install if your CPU is from pre 2012 era.

VMware: Failed to leave the domain . The user or group named ‘\esx^admins’ does not exist.

Sometimes when ESXi loses its trust relationship with Active Directory, you cannot log in with your AD account, and attempts to remove the ESXi server from AD result in an error:

Failed to leave the domain <Domain Name>. The user or group named ‘<AD>\esx^admins’ does not exist.


Create a local group called esx^admins:

/usr/lib/vmware/busybox/bin/busybox addgroup DOMAIN\\esx^admins

(Change DOMAIN to be Netbios name of AD, and note the double \)

Repeat for any other AD based group names you have assigned permission to within the ESXi host.

Remove from the domain, either via ESXi or vCenter (preferred)

Remove the temporary local group(s):

/usr/lib/vmware/busybox/bin/busybox delgroup DOMAIN\\esx^admins

Add the ESXi Host back into the domain via ESXi or vCenter (preferred).

If it fails to rejoin after a long delay, delete the Computer object for the ESXi Host from AD.