The xds-master folder is where all the magic happens, this folder is located in \\Lync fileshare\CentralMgmt folder\CMS FileStore\ Inside the file store you can find the “Central Mgmt” folder that is used by the Master CMS to replicate data. CMS Directory Structureīefore explaining how does the CMS replication works, I will explain the structure of the CMS directory, but first you need to know that CMS operate in a Single master / multiple replica (another word: Copies) system, we will talk more about that later in this article, but this mean that any Lync deployment has ONE and Only ONE master CMS stored in the Lync file store defined in the Lync Topology.
dll file has too many validation rules to check if what you trying to do is supported by Lync core design, then when it find that it is valid, it writes the new data to the CMS. So to modify data in CMS, you must use one of those Lync Management tools. dll file (programming library) called “”, the following Lync server tool are using this file:
The answer for this question is “You cannot”, access to the CMS is limited by only a.
If you have good experience with SQL, you can check the “Document” table in the xds database and you will notice that each xml document end with a “scope” and only one file exist by scope Data Scopeĭata stored in CMS can be stored with four different scope levels:įor each of those scope, there will be only one xml document, so if you have in your Lync deployment a site Dial plan in addition to the Global dial plan, there will be two XML document in your CMS, one for the Global dial plan and one for the site dial plan. NOTE: Lync still save some user object information in Active directory to maintain “Backward Compatibility” with OCS.
In previous versions as in OCS and OCS 2007 R2, those kind of data were stored in the Active directory, Windows Management Instrumentation (WMI) and also SQL database, if you had worked with OCS you will remember that you needed to extend the Active Directory Schema to add a new features or functions and wait for replication across your AD infrastructure to complete, with Lync CMS it became way much easier as all data are stored in one location. Those kind of data are stored as XML documents in the database, and CMS services replicate those data to the required servers. dial plans, client policies, meeting policies)
Configuration (contain all Lync’s different settings e.g.Topology (contain all data and information created by the Topology Builder).Lync Central Management store (CMS), is a Microsoft SQL database (will be under the name xds in the SQL server) that is used by Lync to store the following data: So less words and more diagrams to make it understandable, instead of 5 pages of words I decided to write a “Simple Lync CMS Explanation” article, the difference with this article is that I decided to use easy words not big words as much as I can, to make it easier for Engineers with little SQL experience to understand Lync Database and how does it work, replicate…etc.