TIP: Force database Copy movement between Exchange DAG nodes

When the small version number of the Exchange backend server MBX is inconsistent, such as the version of Exchange SP3 RU8, but the minor version number is inconsistent, when we run a script that balances the distribution of the Exchange DAG, The DAG database above the lower version server may not be able to properly transfer to the preferred node, which will report errors that could not mount the database.

We can manually mount the database on the highest priority node using commands.

Use:-skipclientexperiencechecks parameter

The specific command is:move-activemailboxdatabase database name –activateonserver server name –skipclientexperiencechecks

If you are not familiar with how this command is used, we can open the PowerShell tool for Exchange and enter the following command to view the Help information for that command:

1) get-help Move-activemailboxdatabase–full

2) Get-help Move-activemailboxdatabase–examples

You can also view the online Help file for this command:

Move-activemailboxdatabase:exchange Help
https://technet.microsoft.com/en-us/library/dd298068 (v=exchg.141). aspx

Move-activemailboxdatabase:exchange Help
Https://technet.microsoft.com/en-us/library/dd298068.aspx

This article from "Zeng Hung Xin Technical column" blog, declined to reprint!

TIP: Force database Copy movement between Exchange DAG nodes