Thursday, August 16, 2012

Determine client versions with Lync Server 2010/2013

I've seen several posts on this subject including tools, scripts, and some really great information on how to retrieve client version information out of Lync. Formerly with OCS you used to be able to click the Database tab in the MMC and view client version summary in a nicely displayed table. With Lync Server 2010 this feature doesn't exist ---or does it?

Lync Server 2010 introduced the idea of user registration happening on the front-end servers (in an Enterprise Pool) instead of the pool database back-end. Standard Edition servers also record user registration in a 'front-end' instance of SQL called the "RTCLOCAL" instance. If you look at the Services MMC snap-in for an Enterprise Edition front-end server you'll notice a SQL Server service for the RTCLOCAL instance.

This instance is where user registrations are held, more specifically they are stored in the "rtcdyn" database within this instance.

To obtain client version data we can actually use the Snooper utility which ships with the Lync Server 2010 Resource Kit Tools. This tool can be found under C:\Program Files\Microsoft Lync Server 2010\ResKit\Tracing. Simply run this tool and select "Reports", then "Conferencing and Presence" from the menu.



In the "SQL Backend" text box type the name of one of your front-end servers if you're using Lync Server 2010 Enterprise Edition followed by "\rtclocal". If you're using Standard Edition, type the server name followed by "\rtclocal". For example:

Change the report type to "Diagnostic" and click the "Generate Report" button. Scroll down to the client version summary section to view the results.


To view client version information for other front-ends in the pool, simply change the server name and query them individually.

Good Refernce:

Doug's Blog on retrieving users and versions: http://blogs.technet.com/b/dodeitte/archive/2011/06/15/how-to-get-a-list-of-client-versions-and-the-users-logged-into-them.aspx

3 comments:

  1. Am I mistaken, or the RTCLOCAL instance isn't configured to accept connections via TCP/IP by default? So either a) you have to enable TCP/IP on all RTCLOCAL instances before connecting from snopper remotely, or b) you have to login to each FE and run snooper locally?

    ReplyDelete
  2. You need to run snooper from a remote server to the FE box. You can't connect snooper to the RTCLOCAL instance of the server you're logged in to.

    ReplyDelete
  3. Any update for Lync 2013? When running the above steps, I get this error: The database was not a version we understand. Expected 59, but found 125.

    I have tried using the snooper v5x as well but this doesn't allow for the reporting.

    Thanks in advance :)

    ReplyDelete