How to Verify if Lync Server 2013 Database Updates Completed Successfully
Update 7/9/18 - Added database versions for July 2018 Cumulative Update.
You can find the Skype for Business 2015 database versions here.
After downloading and installing Lync Server 2013 updates from KB2809243, it is important to remember to go back and apply the back end database updates. The steps to apply the back end database updates are listed in the KB article. After applying the back end database updates, you can use the Test-CsDatabase cmdlet to make sure that the databases are up-to-date.
The cmdlet will show you the expected version and the installed version, as well as whether or not the database is up-to-date:
The tables below list the back end database versions for RTM as well as each cumulative update:
| Cumulative Update | Back End Databases | ||||||||||
| rtcxds | rtcshared | rtcab | rgsconfig | rgsdyn | cpsdyn | LcsLog | LcsCDR | QoEMetrics | xds | lis | |
| RTM | 15.13.1 | 5.0.1 | 62.42.0 | 5.5.1 | 2.2.1 | 1.1.1 | 24.40.0 | 39.82.0 | 62.90.0 | 10.13.1 | 3.1.1 |
| February 2013 | 15.13.1 | 5.0.1 | 62.42.1 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.1 | 62.90.1 | 10.13.2 | 3.1.1 |
| July 2013 | 15.13.1 | 5.0.1 | 62.42.2 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.2 | 62.90.1 | 10.13.2 | 3.1.1 |
| October 2013 | 15.13.1 | 5.0.1 | 62.42.2 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.2 | 62.90.1 | 10.13.2 | 3.1.1 |
| January 2014 | 15.13.1 | 5.0.1 | 62.42.2 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.2 | 62.90.1 | 10.13.2 | 3.1.1 |
| August 2014 | 15.13.1 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.2 | 62.90.1 | 10.13.2 | 3.1.1 |
| September 2014 | 15.13.2 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.2 | 62.90.1 | 10.13.2 | 3.1.1 |
| October 2014 | 15.13.2 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.2 | 62.90.1 | 10.13.2 | 3.1.1 |
| November 2014 | 15.13.2 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.3 | 62.90.1 | 10.13.2 | 3.1.1 |
| December 2014 | 15.13.2 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.3 | 62.90.1 | 10.13.2 | 3.1.1 |
| February 2015 | 15.13.2 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.3 | 62.90.2 | 10.13.3 | 3.1.1 |
| May 2015 | 15.13.2 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.4 | 62.90.2 | 10.13.3 | 3.1.1 |
| July 2015 | 15.13.2 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.5 | 62.90.2 | 10.13.3 | 3.1.1 |
| September 2015 | 15.13.2 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.5 | 62.90.2 | 10.13.3 | 3.1.1 |
| December 2015 | 15.13.2 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.5 | 62.90.2 | 10.13.3 | 3.1.1 |
| January 2016 | 15.13.2 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.5 | 62.90.2 | 10.13.3 | 3.1.1 |
| April 2016 | 15.13.2 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.5 | 62.90.2 | 10.13.3 | 3.1.1 |
| May 2016 | 15.13.2 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.5 | 62.90.2 | 10.13.3 | 3.1.1 |
| August 2016 | 15.13.2 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.5 | 62.90.2 | 10.13.3 | 3.1.1 |
| November 2016 | 15.13.2 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.5 | 62.90.2 | 10.13.3 | 3.1.1 |
| December 2016 | 15.13.2 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.5 | 62.90.2 | 10.13.3 | 3.1.1 |
| January 2017 | 15.13.2 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.5 | 62.90.2 | 10.13.3 | 3.1.1 |
| March 2017 | 15.13.2 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.5 | 62.90.2 | 10.13.3 | 3.1.1 |
| July 2017 | 15.13.2 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.5 | 62.90.2 | 10.13.3 | 3.1.1 |
| July 2018 | 15.13.2 | 5.0.1 | 62.42.3 | 5.5.1 | 2.2.1 | 1.1.2 | 24.40.0 | 39.82.5 | 62.90.2 | 10.13.3 | 3.1.1 |
| Cumulative Update | Back End Databases | |
| mgc | mgccomp | |
| RTM | 1.42.0 | 1.7.0 |
| February 2013 | 1.42.0 | 1.7.0 |
| July 2013 | 1.42.1 | 1.7.0 |
| October 2013 | 1.42.1 | 1.7.0 |
| January 2014 | 1.42.1 | 1.7.0 |
| August 2014 | 1.42.2 | 1.7.0 |
| September 2014 | 1.42.2 | 1.7.0 |
| October 2014 | 1.42.2 | 1.7.0 |
| November 2014 | 1.42.2 | 1.7.0 |
| December 2014 | 1.42.2 | 1.7.0 |
| February 2015 | 1.42.2 | 1.7.0 |
| May 2015 | 1.42.2 | 1.7.0 |
| July 2015 | 1.42.2 | 1.7.0 |
| September 2015 | 1.42.2 | 1.7.0 |
| December 2015 | 1.42.2 | 1.7.0 |
| January 2016 | 1.42.2 | 1.7.0 |
| April 2016 | 1.42.2 | 1.7.0 |
| May 2016 | 1.42.2 | 1.7.0 |
| August 2016 | 1.42.2 | 1.7.0 |
| November 2016 | 1.42.2 | 1.7.0 |
| December 2016 | 1.42.2 | 1.7.0 |
| January 2017 | 1.42.2 | 1.7.0 |
| March 2017 | 1.42.2 | 1.7.0 |
| July 2017 | 1.42.2 | 1.7.0 |
| July 2018 | 1.42.2 | 1.7.0 |
Comments
Anonymous
January 01, 2003
No need to even hardcode the SQL server in many environments. Test-CsDatabase -ConfiguredDatabases -SqlServerFqdn (Get-CSService -UserDatabase).PoolFqdn | Select-Object DatabaseName,Installed*,Expected*Anonymous
January 01, 2003
very useful, thanks.Anonymous
January 01, 2003
@Russell
Yep. I just updated the post with information on mgccomp.- Anonymous
February 09, 2017
The comment has been removed- Anonymous
February 10, 2017
I take that statement in the KB to mean that if the Standard Edition Server or Enterprise pool was already running the February 2015 CU when you installed the CMS on that server, then there is no need to run the Install-CsDatabase cmdlet, as the database would have been created using the latest version and is already up-to-date. More than likely, at some point, you'd want to move to a pure Skype for Business environment, which would mean moving the CMS to the Skype for Business pool anyways. In either case, if you have concerns, the best option would be to open a support case with Microsoft Support in order to make sure that you're making the best decision for your environment.- Anonymous
February 14, 2017
Thank you very much for the response and suggestion. We will approach MS for the recommended approach.
- Anonymous
- Anonymous
- Anonymous
Anonymous
January 01, 2003
Hi Doug
how about September 2014 security CU just released. i cannot seem to spot any difference in DB version although KB state to run database upgrade even for systems on August 2014 CU. thanks.Anonymous
January 01, 2003
@Jan Pettersson
If you run a Test-CsDatabase after applying the February CU, you'll see that the ExpectedVersion for the xds database is 10.13.3. Step 3 in the KB probably hasn't been updated yet.Anonymous
January 01, 2003
Ok, search and ye shall find - http://blogs.technet.com/b/dodeitte/archive/2015/05/10/how-to-verify-if-skype-for-business-server-2015-database-updates-completed-successfully.aspx.
I had this page bookmarked, so will bookmark the new page too.Anonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
@Rose
That is expected behavior when you have SQL mirroring setup. It is because the databases on the mirror are in the mirror state. If you run a Get-CsDatabaseMirrorState you should see that the MirroringStatusonMirror parameter is set to Mirror for all of the databases. If you were to make some/all of the databases active on the mirror by running the Invoke-CsDatabaseFailover cmdlet and then run the Test-CsDatabase cmdlet for the mirror, it would return the InstalledVersion.Anonymous
September 11, 2013
Awesome info. Thanks for the post it has been most helpful.Anonymous
October 14, 2013
Thanks Doug, really helpful. For Easy Reading of current version: Test-CsDatabase -ConfiguredDatabases -SqlServerFqdn sql01.tomuc.int | Select-Object databasename,installedversionAnonymous
November 01, 2013
Thanks for the update when each CU is published. Very nice :)Anonymous
November 21, 2013
hello, after update lync 2013 rtm to cu3, i see that xds installed version is 10.13.1. why?Anonymous
November 21, 2013
1 vm deployment, Lync 2013 standard with sql express 2012Anonymous
November 21, 2013
@Nick Make sure that you also ran Step 3 from KB2809243 to apply any updates to the CMS.Anonymous
November 22, 2013
@dodeitte thx man, after get-csmanagementconnection and Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn CMS.FQDN -SqlInstanceName DBInstanceName -Verbose working fine and xds version is 10.13.2.Anonymous
January 08, 2014
Pingback from … and I thought I saw a 2 » Blog Archive » Lync Server 2013 CU4 – January 2014Anonymous
January 08, 2014
Pingback from … and I thought I saw a 2 » Blog Archive » Lync Server 2013 CU4 – January 2014Anonymous
January 09, 2014
Pingback from How to Verify if Lync Server 2013 Database Updates Completed Successfully – Doug Deitterick’s Blog – Site Home – TechNet Blogs | JC's Blog-O-GibberishAnonymous
March 08, 2014
After running the database updates Lync Mobile stopped working on iPhones.Anonymous
April 02, 2014
Do you have the mgccomp database details for Installed Versions of the different Cumulative Updates?Anonymous
February 08, 2015
October 2013 CU's for Lync Server 2013/2010, Lync 2013/2010, Lync Mobile 2013 and Lync Phone EditionAnonymous
February 08, 2015
Microsoft has released CU January 2014 for Lync Server 2010/2013Anonymous
April 01, 2015
February CU states a newer version of XDS-database: 10.13.3
But the instructions for installations does not talk about updating the CMS-database?Anonymous
April 26, 2015
We have two SQL Database ( Principle and mirror), principle shows that update successfully installed and are up to dated. but when I run the command and target the mirror server, the installed version shows blank and does not meet the expected version. Kindly adviceAnonymous
May 18, 2015
You can find the Lync Server 2013 database versions here .
KB2809243 , it is important to rememberAnonymous
October 08, 2015
Hi, Can you update with 927 (Sept Security Update) and 933 (Sept/October CU).
ThanksAnonymous
October 20, 2015
Tobie Fysh, run Test-CsDatabaseAnonymous
October 21, 2015
@Tobie Fysh
I've updated the tables with the September 2015 CU database versions.Anonymous
December 08, 2015
Excellent source of information - easy to follow and helped me prove my db's were up to date in about 2 minutes.
ThanksAnonymous
December 23, 2015
@dodeitte
How about the December 2015 CU?Anonymous
December 28, 2015
@Michael
I've updated the table with the December 2015 CU information.Anonymous
January 16, 2016
Microsoft states that If the Central Management Store is homed on a Lync Server 2013 Standard Edition Server or Enterprise pool that was previously updated with the Lync Server 2013 February 2015 cumulative updates, do not run the Install-CsDatabase -CentralManagementDatabase command. Is this true as February 2015 CU also brought DB updates?Anonymous
January 28, 2016
Doesn't look like the January 2016 update had any DB updates, just wanted to clarify.Anonymous
February 03, 2016
@Glenn
I've updated the table with the January 2016 CU information.Anonymous
April 06, 2016
I have a question. We have 2013 Standard with pool mirroring. I can run this command off of the "main" pool and works but not on the other pool. With Standard is there an SQL database for both pools or is it just housed on the "main" pool.Anonymous
September 08, 2016
If you add OGV to the end of the PowerShell command make its much easier to read and compare.Test-CsDatabase -ConfiguredDatabases -SqlServerFqdn DBNAME | ogvAnonymous
January 06, 2017
Ready to patch up to Nov 2016 CU today, but when I run the test-csdatabase, xds is at 10.13.1 (RTM), while all others have been updated to latest on Sept 2015 CU. How is that possible? I would have thought that running the Install-CSdatabase previously would have updated it. Do I still need to do Install-CSDatabase today if Lync services are running fine?- Anonymous
January 17, 2017
You probably need to run Install-CsDatabase with the -CentralManagementDatabase parameter.
- Anonymous
Anonymous
July 15, 2017
can we get this updated for the July updates- Anonymous
July 16, 2017
I updated the tables.
- Anonymous
Anonymous
February 12, 2019
As per SfBS 2015 can this be updated for completeness (no changes for Jan 2019 afaict)