No way to validate planned changes before they take effect
Out of sync – policies, configuration. </li></ul>With Central Management in CS 14:<br /><ul><li>Schematized definition (Xml docs) of deployment topology, configuration of CS components & Policies.
All documents managed by central store (SQL database)
All writes (changes) happen against central store data. Eliminate “out of sync” problems.
Read-only copies of data are replicated to all topology nodes (including Edge).
Validation happens before changes are “published”. Eliminate misconfiguration.</li></li></ul><li>Central Management Store (CMS)<br />Configuration Change - Workflow<br />CMS<br />CS 14 server1<br />2<br />4<br />1<br />3<br />5<br />Administrator makes changes through CS PowerShell/UI Interfaces.<br />Master Replicator generates a snapshot of the new configuration.<br />File Transfer Agent replicates the snapshot to all computers in the deployment .<br />Local Replicator Agent notified of new snapshot available. Loads it into the database and reports back status.<br />Status is transferred back to master and replication status is updated.<br />
Topology Model<br /><ul><li>Global CS Deployment: is a collection of Sites
Communications Server Control Panel (CSCP): What is it?<br />A web-based, scenario-driven management GUI<br />Based on Silverlight 4 and PowerShell<br />Targeted to expose most relevant PowerShell delivered features / settings<br />GUI tool includes <br />Easy Navigation<br />Easy searches (Save & reuse queries)<br />Effective policy view<br />Voice Routing support built-in <br />No cascading property sheets<br />Role based access support<br />And more…<br />Replaces MMC-based snap-in used in previous releases<br />