Article ID: 2809243 - View products that this article applies to.
This article lists the available updates for Microsoft Lync Server 2013 and specifies the applicability of the updates for each server role.
Updates that are released for Lync Server 2013
To install updates for a Lync Server 2013 installation that has had any of the following previous cumulative updates installed, you must perform step 1 and step 2.
To install updates for Lync Server 2013 RTM (5.0.8308.0) you must perform steps 1-5.
Important Do not shut down or restart all Front End servers at the same time. This may cause issues when you start the services.
Step 1: Install the cumulative updatesImportant To maintain a functional Lync Server 2013 Enterprise Edition pool, you must make sure that Ready is returned for the State value of the pool when you run the Get-CsPoolUpgradeReadinessStatecmdlet and that you have the appropriate number of Lync Server 2013 front-end servers that are running. Please see the "Upgrade or Update Front End Servers" and "Planning for the Management of Front End Pools" section of the following TechNet topic to determine the State value of the pool before you apply the cumulative update.
Upgrade or Update Front End Servers
Topologies and Components for Front End Servers, Instant Messaging, and PresenceThe 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 PoolsThe front-end servers in an Enterprise Edition pool are organized into upgrade domains. These upgrade domains are subsets of front-end servers in the pool. Upgrade domains are created automatically by Topology Builder.
You must upgrade one upgrade domain at a time, and you must upgrade each front-end server in each upgrade domain. To do this, take one server in an upgrade domain offline, upgrade the server, and then restart it. Then, repeat this process for each server in the upgrade domain. Make sure that you record which upgrade domain and servers that you have upgraded.
Upgrade or Update Front End ServersTo upgrade front-end servers, you must follow these steps:
Lync Server 2013 Standard Edition and other Roles
Step 2: Apply the back-end database updatesAfter you install the update for the Core Components server role on a Lync Server 2013 Enterprise Edition front-end server or on a Lync Server 2013 Standard Edition server, the updated SQL database files are dropped to the computer that has the Core Components server role installed. To apply the database changes, you have to run the applicable cmdlets run the applicable cmdlets that are described in step 2.
Note The -Update parameter is not required when you run the Install-CsDatabase cmdlet to update the Lync Server 2013 databases.
Lync Server 2013 Standard Edition
Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn SE.FQDN -Verbose
Note You must run the cmdlet on the Lync Server 2013 Standard Edition server.
Lync Server 2013 Enterprise EditionYou must perform several configuration operations, depending on the kind of Lync Server 2013 Enterprise Edition back-end servers that you are using.
Note If Persistent Chat is collocated (Persistent Chat front-end service and back-end database are running on the same server), you must run the following command together with the ExcludeCollocatedStoresparameter.
Note If database mirroring is enabled for the back-end databases, we strongly recommended that you use the Invoke-CsDatabaseFailover -NewPrincipal Primary command, and then verify that the primary server is principal for all databases before you run the Install-CsDatabase cmdlet.
Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn FEBE.FQDN -Verbose
Lync Server 2013 Persistent Chat DatabasesWhen Persistent Chat Services are collocated with the SQL BE Databases, run the following command:
Install-CsDatabase -DatabaseType PersistentChat -SqlServerFqdn PChatBE.fqdn -SqlInstanceName DBInstance -Verbose
Lync Server 2013 Monitoring/Archiving/Persistent Chat DatabasesWhen Lync Server 2013 Monitoring/Archiving/Persistent Chat databases are deployed on stand-alone SQL databases, run the following command:
Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn SQLServer.FQDN -Verbose
Step 3: Apply the Central Management Database updateNote You do not have to update the Central Management Database in the following instances:
Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn CMS.FQDN -SqlInstanceName DBInstanceName -Verbose
Note 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, do not run the Install-CsDatabase -CentralManagementDatabase command. If you later move the Central Management Service to a Lync Server 2013 pool, you have to run the Install-CsDatabase -CentralManagementDatabase command to apply the changes.
Step 4: Enable the Mobility serviceTo enable the Mobility service, run the following cmdlet:
Step 5: Enable the Unified Communications Web APITo 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
List of server roles and the updates that apply to them
Lync Server 2013 - Standard Edition server
Lync Server 2013 - Enterprise Edition - Front End server and Back End server
Lync Server 2013 - Edge server
Lync Server 2013 - stand-alone Mediation server
Lync Server 2013 - Director server
Lync Server 2013 - Persistent Chat Front End server
Lync Server 2013 - Administration Tools
See the general information about the standard terminology that is used to describe Microsoft software updates