September 2019 cumulative update 5.0.8308.1101 for Lync Server 2013, Core Components

To install updates for a Lync Server 2013 installation that has any of the following cumulative updates installed, do steps 1 and 2.

• September 2019 cumulative update (5.0.8308.1101)
• July 2018 cumulative update (5.0.8308.1001)
• July 2017 cumulative update (5.0.8308.992)
• March 2017 cumulative update (5.0.8308.987)
• January 2017 cumulative update (5.0.8308.984)
• November 2016 cumulative update (5.0.8308.974)
• April 2016 cumulative update (5.0.8308.956)
• January 2016 cumulative update (5.0.8308.945)
• December 2015 cumulative update (5.0.8308.941)
• September 2015 cumulative update (5.0.8308.933)
• July 2015 cumulative update (5.0.8308.920)
• May 2015 cumulative update (5.0.8308.887)
• February 2015 cumulative update (5.0.8308.871)
• December 31, 2014 cumulative update (5.0.8308.866)
• December 2014 cumulative update (5.0.8308.857)
• November 2014 cumulative update (5.0.8308.834)
• October 2014 cumulative update (5.0.8308.831)
• September 2014 cumulative update (5.0.8308.815)
• August 2014 cumulative update (5.0.8308.738)
• January 2014 cumulative update (5.0.8308.577)
• October 2013 cumulative update (5.0.8308.556)
• July 2013 cumulative update (5.0.8308.420)
• February 2013 cumulative update (5.0.8308.291)

To install updates for Lync Server 2013 RTM (5.0.8308.0), follow steps 1–5. 

Step 1: Install the cumulative updates

The Cumulative Server Update Installer applies all updates for the appropriate server role in one operation. To use the Cumulative Server Update Installer, follow these steps.

Note If User Account Control (UAC) is turned on, you must start the Cumulative Server Update Installer by using elevated permissions to make sure that all updates are installed correctly.

Download the Cumulative Server Update Installer.

Lync Server 2013 Enterprise pools

Upgrade or update Front End servers

1. On a front-end server in a pool, run the following cmdlet:
   
   Get-CsPoolUpgradeReadinessState
   
   If the State value of the pool is Busy, wait 10 minutes, and then try to run the Get-CsPoolUpgradeReadinessState cmdlet again. If you see Busy at least three consecutive times after you wait 10 minutes between attempts, or if you see a result of InsufficientActiveFrontEnds for the State value of the pool, there's an issue that's affecting the pool. If you can't resolve the issue, you may have to contact Microsoft Support. If this pool is paired with another front-end pool in a failure recovery topology, you must fail over the pool to the backup pool and then update these servers in that pool. For more information about how to fail over a pool, see the following Microsoft Docs article:  
   Failing over a pool in Lync Server 2013
   If the State value of the pool is Ready, go to step 2.
2. The Get-CsPoolUpgradeReadinessState cmdlet also returns information about the upgrade domains in the pool, and about which front-end servers are in each upgrade domain. If the ReadyforUpgrade value for the upgrade domain that contains the server that you want to upgrade is True, you can upgrade the server.
3. To do this, follow these steps:
    
   1. Stop new connections to the front-end servers by using the Stop-CsWindowsServices -Graceful cmdlet.
   2. Run the Cumulative Server Update Installer by using the UI or a command to upgrade the front-end servers that are associated with an upgrade domain.
      
      Note If you upgrade or update front-end servers during scheduled server downtime, you can run the cmdlet in step 2 without the -Graceful parameter. More specifically, run the cmdlet as Stop-CsWindowsService. This action immediately shuts down services, and the server doesn't wait until each existing service request is fulfilled.
      
      Note The UI provides a clear indication of which updates are installed when you click Install Updates.
      
      To run the Installer, run the following command:

      LyncServerUpdateInstaller.exe 

      
      Note The following bullet points describe parameters that you can use with the LyncServerUpdateInstaller.exe command:
       
      • The /silentmode switch applies all applicable updates in the background.
      • The /silentmode /forcereboot switches when used together apply all applicable updates in the background, and then automatically restart the server at the end of the installation process, if it's necessary.
      • The /extractall switch extracts the updates from the installer, and then it saves the updates in a subfolder that's named Extracted in the folder from which you ran the command.
   3. Restart the server, and make sure that it's accepting new connections.

Lync Server 2013 Standard Edition and other roles

1. Run the Cumulative Server Update Installer by using the UI or by running a command line to upgrade the front-end servers that are associated with an upgrade domain.
   
   Note The UI provides a clear indication of which updates are installed when you click Install Updates.
   
   To run the Installer, run the following command:
    

   LyncServerUpdateInstaller.exe 

   
   Note The following bullet points describe parameters that you can use with the LyncServerUpdateInstaller.exe command:
    
   • The /silentmode switch applies all applicable updates in the background.
   • The /silentmode /forcereboot switch applies all applicable updates in the background, and then automatically restarts the server at the end of the installation process if this is necessary.
   • The /extractall switch extracts the updates from the installer and saves the updates in a subfolder that's named "Extracted" in the folder in which you ran the command.
2. Restart the server if it's required by the installation wizard.
    

Step 2: Apply the back-end database updates

Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn
<SE.FQDN>
-Verbose 

• In this command, <SE.FQDN> is a placeholder for the appropriate value.
• You must run this cmdlet on the Lync Server 2013 Standard Edition server.

Lync Server 2013 Enterprise Edition

Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn <FEBE.FQDN> -Verbose 

Lync Server 2013 Persistent Chat databases

Install-CsDatabase -DatabaseType PersistentChat -SqlServerFqdn <PChatBE.FQDN> -SqlInstanceName <DBInstance> -Verbose 

Lync Server 2013 Monitoring/Archiving/Persistent Chat databases

Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn <SQLServer.FQDN> -Verbose 

Step 3: Apply the Central Management Database update

• If the Central Management Store is hosted on a Lync Server 2010 Standard Edition Server or Enterprise pool, don't run the Install-CsDatabase -CentralManagementDatabase command.
• If the Central Management Store is hosted on a Lync Server 2013 Standard Edition Server or Enterprise pool that was previously updated with the Lync Server 2013 February 2013 cumulative updates, don't run the Install-CsDatabase -CentralManagementDatabase command.

Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn <CMS.FQDN> -SqlInstanceName <DBInstanceName> -Verbose 

• In this command, <CMS.FQDN> and <DBInstanceName> are placeholders for the appropriate values.
• In a coexistence environment that contains both Lync Server 2010 and Lync Server 2013 and in which the Central Management Service is located on a Lync Server 2010 pool, don't run the Install-CsDatabase -CentralManagementDatabase command. If you later move the Central Management Service to a Lync Server 2013 pool, you must run the Install-CsDatabase -CentralManagementDatabase command to apply the changes.
   

Step 4: Enable the Mobility service

Step 5: Enable the Unified Communications Web API

%ProgramFiles%\Microsoft Lync Server 2013\Deployment\Bootstrapper.exe