Note: Since authoring this blog, Microsoft Customer Support Services has identified a scenario in which moving a CMS using the cluster tools can leave databases in a dismounted or offline stat...
Updated Jul 01, 2019
Version 2.0
Blog Post
Scott,
I think that you are missing the point. The major issues are these, as I see them:
1. Using EMS does not allow for very granular delegation (please correct me if I am wrong). So, for example, I can't delegate the ability to move the cluster to an operations team without giving them other permissions that are not required for their job and thus violating one of the major principles of the generally accepted security principles.
2. The Exchange team, not the cluster team, failed to provide for proper use of existing tools (i.e. cluadmin and cluster.exe) which do allow for proper delegation.
Exchange Server 2007 is the only product that failed to proper leverage existing tools and processes when it comes to clustering.
I think that you are missing the point. The major issues are these, as I see them:
1. Using EMS does not allow for very granular delegation (please correct me if I am wrong). So, for example, I can't delegate the ability to move the cluster to an operations team without giving them other permissions that are not required for their job and thus violating one of the major principles of the generally accepted security principles.
2. The Exchange team, not the cluster team, failed to provide for proper use of existing tools (i.e. cluadmin and cluster.exe) which do allow for proper delegation.
Exchange Server 2007 is the only product that failed to proper leverage existing tools and processes when it comes to clustering.