Shared Config Database

[centrekin]

We are in the process of completing a merger (technically), and also upgrading an outer office to Exch. 2010. In this process we're going to be upgrading both BES Environments.

Office 1 has it's own BES and Config Database

Office 2 has it own BES and Config Database

Would there be a significant advantage to use a Single Config database when we upgrade our BES Servers, or should we keep them separate?

The database(s) will be SQL with mirroring across our WANs (Latency is not an issue on them).

Would having one Config DB make moving users easier between BES Servers? If so how?

Also, both BES servers will use the same BESAdmin account as well.

[knottyrope]

A shared database is better. But with transporter you should be able to move users if you have separate databases.

You should be able to move users to diff BES in BAS with shared database.

[cyclmpc]

To expand knottyrope's reply...

Depending on what failover tools you have, the options of having one DB with your environment will allow you to move users over from one BES to another. If you have an issue, you can move a group or specific users from a failing BES to a healthy one to minimize down time.