What is Central Management Store in Lync Server 2010?
CMS stand for Central Management Store.
Microsoft Office Communications Server stored configuration data within Active Directory, like SIP address, AV configuration data, Telephony configuration etc. Microsoft SQL Server, and Windows Management Instrumentation (WMI). One impact of this design is that making even a small setting change requires changing the schema in Active Directory. This is not a process undertaken lightly, particularly in large organizations.
CMS Storage:
Lync Server 2010, all topology, policy, and configuration data are stored in the CMS. The CMS database provides storage for all data about servers, services, and users in the system. CMS validates the data to ensure configuration consistency.
Read-only copies are then replicated to all servers in your deployment by the CMS, which runs on one Front End pool or one Standard Edition server in your deployment.
This replication eliminates the “out-of-sync” errors that would sometimes occur with the Edge servers, and adds system-wide resiliency in the event of CMS outage.
Administering CMS:
To administer and manage the servers, services, and user policies stored within CMS, you can use Lync Server Management Shell or Lync Server Control Panel, which then makes the setting changes in CMS.
Lync Server 2010 is available in two editions:
Standard
Enterprise
The Enterprise Edition server requires a minimum of two servers in the deployment �C a Front End and a Back End server.
The Front End server is the core server role and the Back End server provides the database. The Standard Edition server combines the Front End and Back End roles onto a single server. This topology is easy to deploy, and it enables IM, presence, conferencing, and Enterprise Voice for smaller organizations that do not require a high-availability solution.
Front End Pools:
A Front End pool is a set of Front End servers, configured identically, that work together to provide services for a common group of users, with full scalability and failover capabilities. A Front End server (or Front End pool) provides the following functionality:
1.User authentication and registration
2.Presence information and contact card exchange
3.Address book services and distribution list expansion
4.IM functionality, including multi-party IM conferences
5.Web conferencing and application sharing (if deployed)
6.Application hosting services
7.Application services for application hosting and host applications (for example, Response Group Application)
8.Additionally, one Front End pool in the deployment also runs the CMS
Back End Servers:
The Back End servers are database servers running Microsoft SQL Server that provide the database services for the Front End pool. You can have a single Back End server, or a cluster for failover. Back End servers do not run any Lync Server 2010 software. If you already have a SQL Server cluster that you reusing for other applications, you can also use this cluster for Lync Server 2010, if performance allows. Information stored in the Back End server databases includes presence information, users’ contact lists, conferencing data (including persistent data about the state of all current conferences), and conference scheduling data. The following are three reference topologies to help you envision the different scenarios where a Standard Edition versus an Enterprise Edition should be deployed.
From:http://cc.bingj.com/cache.aspx?q=lync+server+Center+administration+store&d=4564490743451625&mkt=zh-CN&setlang=zh-CN&w=OTZWLBrKJuwbsNKPNhlgrXjANsc_22E7