There’s been an a new Lync Server 2013 CU update release yesterday 13/12/2016 – KB2809243 it seems to have the same KB number as the November 2016 CU and look to be a fix for a detected issue in the November 2016 CU.
It looks like this is a minor CU update and includes an update to resolve an issue with no contacts being resolved on the mobile client after the November 2016 CU as been installed.
Improvements
Link to issue here
Issue Details
You install the November 2016 Cumulative Update for Microsoft Lync Server 2013. When you search for a user by using Lync Mobile, no results are returned. Additionally, an error entry is logged in the Application event log on the Lync Server that contains the following:
Event ID 20003
Source: LS UCWA
Server update screenshot.
Updates to core components and Web Components only from November 2016 update.
Databases
There doesn’t seem to be any database update required after Nov 2016 CU update buts its always worth checking using test-csdatabase.
Post Dec CU Install
| DatabaseName | ExpectedVersion | InstalledVersion |
| rtcxds | 15.13.2 | 15.13.2 |
| rtcshared | 5.0.1 | 5.0.1 |
| rtcab | 62.42.3 | 62.42.3 |
| rgsconfig | 5.5.1 | 5.5.1 |
| rgsdyn | 2.2.1 | 2.2.1 |
| cpsdyn | 1.1.2 | 1.1.2 |
| mgc | 1.42.2 | 1.42.2 |
Also install notes still recommend two steps below so dont forget these. If you have applied Nov 2016 CU already then i dont believe you need to do this but it wont hurt to do it again.
If you haven’t installed Nov 2016 make sure you do !
Step 4: Enable the Mobility service
To enable the Mobility service, run the following cmdlet:
Enable-CsTopology
Step 5: Enable the Unified Communications Web API
To enable the Unified Communications Web API (UCWA), you must run the Bootstrapper.exe tool again on all Lync Server 2013 Director servers, Standard Edition servers, and Enterprise Edition front-end servers on which the web components are installed and updated. The command to run the tool is as follows:
%ProgramFiles%\Microsoft Lync Server 2013\Deployment\Bootstrapper.exe
Martin Boam's Microsoft Blog 