Updates for Lync Server 2013 (KB2809243)

Lync Server 2013 Enterprise Pools

The 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 servers

To upgrade Front End servers, follow these steps:

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 for 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 in between each attempt, or if you see any result of InsufficientActiveFrontEnds for the State value of the pool, there is an issue that affects the pool. If you cannot resolve this issue, you may have to contact Microsoft Support. If this pool is paired with another front-end pool in a disaster recovery topology, you must fail over the pool to the backup pool, and then update these servers in this pool. For more information about how to fail over a pool, go to the following Microsoft website:

   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. To do this, you must follow these steps:

   1. Stop new connections to the front-end servers by using the Stop-CsWindowsService -Graceful cmdlet.

   2. Run the Cumulative Server Update Installer by using the UI or by using 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 does not 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 

      The following text describes parameters that you can use together 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 is named "Extracted" in the folder in which you ran the command.

   3. Restart the server, and make sure that it is 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 command 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 

   You can run the following parameters together with the LyncServerUpdateInstaller.exe command:

   • The /silentmode/silentmode switch applies all applicable updates in the background.

   • The /silentmode/silentmode 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 is named "Extracted" in the folder in which you ran the command.

2. Restart the server if it is required by the installation wizard.

Lync Server 2013 Standard Edition

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

Notes

• In this command, <SE.FQDN> is a placeholder for the appropriate value.

• You must run the cmdlet on the Lync Server 2013 Standard Edition server.

Lync Server 2013 Enterprise Edition

You must do several configuration operations, depending on the kind of Lync Server 2013 Enterprise Edition back-end servers that you are using.

Notes

• If Persistent Chat is co-located (Persistent Chat front-end service and back-end database are running on the same server), you must run the following command together with the ExcludeCollocatedStores parameter.

• 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 

Note In this command, <FEBE.FQDN> is a placeholder for the appropriate value.

Lync Server 2013 Persistent Chat Databases

If Persistent Chat Services are located together with the SQL BE Databases, run the following command:

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

In this command, <PChatBE.FQDN> and <DBInstance> are placeholders for the appropriate values.

Lync Server 2013 Monitoring/Archiving/Persistent Chat Databases

If Lync Server 2013 Monitoring/Archiving/Persistent Chat databases are deployed on standalone SQL databases, run the following command:

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

In this command, <SQLServer.FQDN> is a placeholder for the appropriate value.

Lync Server 2013 - Standard Edition server

• Update for Core Components: KB 5006895

• Update for Unified Communications Managed API 4.0, Core Runtime 64-bit: KB 4501392

• Update for Front End Server and Edge Server (Standard or Enterprise edition server): KB 4458772

• Update for Conferencing Server: KB 4295706

• Update for Web Components Server: KB 4518344

• Update for Web Conferencing Server: KB 4295711

• Update for Mediation Server: KB 4019182

• Update for Call Park Service: KB 3070396

• Update for Backup Service: KB 3070403

• Update for Central Management Server: KB 3070402

• Update for Windows Fabric: KB 2967486

• Update for Bandwidth Policy Service: KB 3070398

• Update for Conferencing Attendant: KB 3070393

• Update for Response Group Service: KB 4295707

• Update for Conferencing Announcement: KB 3213741

• Update for Administrative Tools: KB 3070381

• Update for Unified Communications Managed API (UCMA) 3.0 Workflow APIs: KB 3070378

• Update for Persistent Chat: KB 4019178

• Update for XMPP Gateway: KB 3070408

• Update for Application Host: KB 3070405

• Update for Audio Test service: KB 3070388

Lync Server 2013 - Enterprise Edition - Front End server and Back End server

• Update for Core Components: KB 5006895

• Update for Unified Communications Managed API 4.0, Core Runtime 64-bit: KB 4501392

• Update for Front End Server and Edge Server (Standard or Enterprise edition server): KB 4458772

• Update for Conferencing Server: KB 4295706

• Update for Web Components Server: KB 4518344

• Update for Web Conferencing Server: KB 4295711

• Update for Mediation Server: KB 4019182

• Update for Call Park Service: KB 3070396

• Update for Backup Service: KB 3070403

• Update for Central Management Server: KB 3070402

• Update for Windows Fabric: KB 2967486

• Update for Bandwidth Policy Service: KB 3070398

• Update for Conferencing Attendant: KB 3070393

• Update for Response Group Service: KB 4295707

• Update for Conferencing Announcement: KB 3213741

• Update for Administrative Tools: KB 3070381

• Update for Unified Communications Managed API (UCMA) 3.0 Workflow APIs: KB 3070378

• Update for Persistent Chat: KB 4019178

• Update for XMPP Gateway: KB 3070408

• Update for Application Host: KB 3070405

• Update for Audio Test service: KB 3070388

Lync Server 2013 - Edge server

• Update for Core Components: KB 5006895

• Update for Unified Communications Managed API 4.0, Core Runtime 64-bit: KB 4501392

• Update for Front End Server and Edge Server (Standard or Enterprise edition server): KB 4458772

• Update for Windows Fabric: KB 2967486

• Update for Administrative Tools: KB 3070381

• Update for Unified Communications Managed API (UCMA) 3.0 Workflow APIs: KB 3070378

• Update for XMPP Proxy: KB 3070407

• Update for Audio Test service: KB 3070388

Lync Server 2013 - standalone Mediation server

• Update for Core Components: KB 5006895

• Update for Unified Communications Managed API 4.0, Core Runtime 64-bit: KB 4501392

• Update for Mediation Server: KB 4019182

Lync Server 2013 - Director server

• Update for Core Components: KB 5006895

• Update for Unified Communications Managed API 4.0, Core Runtime 64-bit: KB 4501392

• Update for Front End Server and Edge Server (Standard or Enterprise edition server): KB 4458772

• Update for Web Components Server: KB 4518344

• Update for Windows Fabric: KB 2967486

Lync Server 2013 - Persistent Chat Front End server

• Update for Core Components: KB 5006895

• Update for Unified Communications Managed API 4.0, Core Runtime 64-bit: KB 4501392

Lync Server 2013 - Administration Tools

• Update for Core Components: KB 5006895