Trio Family Conference Phones – HD Voice. Polycom Trio 8. 80. Polycom Trio 8. 80. Marrying our legendary voice quality with the additional capabilities of personal content sharing and business- class videoconferencing, Trio can be flexibly deployed anywhere, from huddle rooms to boardrooms. The Microsoft Lync 2. Server Databases. June 7th, 2. 01. 2 Update: Microsoft SQL 2. NOT supported for all Microsoft Lync 2. The Microsoft KB article “SQL Server 2. Lync Server 2. 01. Lync 2. 01. 0 server roles are not supported. While investigating a recent Lync issue, I had to reacquaint myself with the main databases used in a Lync deployment. In this blog post, I have documented my experiences for the benefit of others. The Types and Uses of Databases in Lync. Microsoft Lync Server 2. Microsoft SQL. The two flavors of the core Front- End Lync Server role requires SQL: Lync 2. Server Standard Edition ships with, installs, and uses Microsoft SQL Server 2. Express Edition (6. Lync 2. 01. 0 Server Enterprise Edition requires Microsoft SQL Server 2. SP1 or 2. 00. 5 SP3 (6. As of April 2. 0, 2. Microsoft SQL Server 2. R2. The 3. 2- bit versions of SQL are not supported. You can read more about the supported Database Software prerequisites here: Microsoft Lync 2. Database Software and Clustering Support. Lync Server 2. 01. SQL databases: 1) Central Management Store (CMS)The CMS store is used by the Central Management Service to maintain a current Lync Server 2. Topology for the entire Lync deployment (Topology, Policies, Voice Routes, etc…). ![]() Here is what you need to know about the CMS: The database used for this purpose is called “Xds”; it maintains the Lync configuration as published by the Topology Builder. There is only one master copy of CMS database which is automatically installed on the first instance of a Standard or Enterprise Edition Lync pool. For Enterprise Edition pools this first instance will reside on the SQL back- end database for the pool. Every subsequent Lync server in the topology gets a read- only copy of it. A topology change on the master is replicated to each read- only copy on each Lync server. This is a key element to Lync Server’s survivability feature set – if the network connection between a Lync Edge server goes down for example, the Edge server still knows about the topology and can keep functioning. Changes are replicated to all Lync server roles except the Lync Edge using the Windows file copy SMB protocol on port 4. Changes are replicated to the Edge role via HTTPS on port 4. The Windows service “Lync server replica replicator agent” is responsible for receiving the snapshot and uploading the local copies of the databases. It then sends a status update to the Master Replicator (also a windows service) running on the CMS. Pool Configuration Store. The pool back- end database is the heart of Lync functionality. The Registrar, User Services, and the Address Book use this database for registration, routing, presence information & conferences, replicating user information, in- band provisioning, and address book functionality. This is commonly referred to the Lync “back- end” database, and one exists for each Lync pool. The following 3 important databases are used for the core feature set of Lync: Rtc: stores persistent user data such as user contact lists, scheduled conferences, and access control lists. As an IT manager, your Lync phones must meet the varying demands of end-users. Your Lync phones must be easy to deploy, manage and support. Polycom phones. There are scenarios when we don't want Lync Status to change to Inactive or Away. Lets see how can we change this setting and always appear Active on Lync. Edit: I updated this in “The ten reasons I still hate Microsoft Lync” in October 2014. I’m stuck with no Microsoft Lync connectivity again, and in my. Rtcdyn: stores dynamic Lync user data such as presence information. Rtcab & Rtcab. Lync address book information (i. AD). The Lync Address Book server alternates use of these databases: one of them is used to service address book queries while the other is being updated. Once the updates are done, they switch roles. Theses databases contain a table called Ab. Attribute which specifies which AD fields will be used in the Lync Address Book (database and ultimately the Lync address book files). If you are having permission issues with either of these databases, see Access to the Lync Server Address Book Databases. ![]() This isn’t a software development problem per se, but it was a technical problem I had with Lync that does not appear to have been documented, based on my searches. Application Store. Lync server uses the following databases for the Call Park and Response Group applications: Cpsdyn: stores dynamic system information for the Call Park application. Rgsdyn: stores dynamic runtime operational information for the Call Park application. Rgsconfig: stores persistent configuration data for the Response Group application. Archiving and Monitoring Store. This store is used by the Lync Archiving Server Role and the Monitoring Server Role. There are 3 separate databases used: Lcs. Log: stores Instant Messaging and Conferencing data for archiving purposes (used by the Archiving Role). Lcs. Cdr: stores the Call Details Records (used by the Monitoring Role)Qo. EMetrics: stores the Quality of Experience data (used by the Monitoring Role)5) Location Store. Lync server uses this database (named “lis”) to hold a network ‘wiremap’ that maps network elements (e. WAP’s, routers) to real civic addresses to provide the new Location and Emergency Services Support (E9- 1- 1) features. All of the individual SQL databases used for each Lync purpose is listed here: SQL Server Data and Log File Placement.“RTC” – A Source of Confusion. A common source of confusion when trying to understand the Lync databases is the presence of multiple Lync SQL instances and databases which share the name “RTC”. Here is a breakdown: An. SQL instance named “RTC” is used to store the back- end pool databases, including the master CMS database. This is installed on the first Front- End server or back- end pool that was installed in the Lync Organization. RTC is the default name for this instance – it can be changed or removed (to use the base SQL instance). Another SQL instance named “RTCLOCAL” which is a SQL Express Instance present on each Lync Front- End server which is used to hold a replica of the CMS database, and the databases necessary for registration and routing. The presence of an SQL database named “rtc” which holds the persistent configuration information for the pool (such as user contact lists, scheduled conferences, etc…). The diagram below illustrates these Lync SQL instances and databases in an example Lync organization with 2 pools and 3 front- end servers. In this organization, the Standard Edition Pool and associated Front- End server was the first to be installed in this organization. Remember, there is only one master copy of CMS database which is automatically installed on the first instance of a Standard Edition or Enterprise Edition Lync pool. This database is shown in red (“xds”). The other “xds” databases shaded in gray are read- only copies replicated to the other 2 Enterprise Edition Front- End servers. Putting It All Together. Power. Shell. One the great features introduced with Lync server is Power. Shell access to almost everything in the Lync system. You can install, install, and configure the various Lync databases from Power. Shell. See Database and Management Server Cmdlets for a list of Lync Management Server cmdlets. One of the more useful cmdlet’s is the Get- Cs. Configuration. Store. Location cmdlet. This cmdlet will tell you the location of the Active Directory Service Control Point (SCP) for the Central Management Store. This AD location allows Lync server to locate the Lync CMS SQL database (server + instance) – a crucial setting to the operation of Lync. Note: the default AD location for the CMS SCP object is “CN=Topology Settings, CN=RTC Service, DC=< example. The ms. RTCSIP- Back. End. Server attribute contains the SQL server and instance name of the master CMS copy. The back- end pool database is crucial for Lync login and function. The back- end for any pool can be viewed in the Lync Topology builder, or you can retrieve the SQL serverand instance name for any back- end pool database using the following Power. Shell cmdlets: 1. Get- Cs. Service - Registrar - Pool Fqdn < pool. Fqdn> (pool. Fqdn = Fqdn of the pool you want)2. Get- Cs. Service - User. Server –Pool. Fqdn < pool. Fqdn> (note the “User. Database” property for step #3)3. Get- Cs. Service - User. Database –Pool. Fqdn < use the User. Database property from step #2> The SQL user database for the pool is the Sql. Server property appended with the \Sql. Instance property. You can also be able to do this with the Get- Cs. Topology cmdlet but it is not as straightforward. To check the status of the local CMS replica on each Lync role, use the Get- Cs. Management. Store. Replication. Status cmdlet. To force the replication services to replicate the CMS database to a specified Lync server, use the Invoke- Cs. Management. Store. Replication cmdlet. In addition to the CMS replication and usage, a Lync Front- End server communicates with the back- end pool database using an SQL connection.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |