July 2022 cumulative update for Lync Server 2013, Core components (KB5016590)

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 domain at a time, and you must upgrade each Front End Server in each 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 domains and servers were 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 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 Learn 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 the parameters that you can use together 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.

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

• 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

You must do several configuration operations, depending on the kind of Lync Server 2013 Enterprise Edition back-end servers that you're 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 ExcludeCollocatedStores parameter.

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-CsDatabasecmdlet.
  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 collocated with the SQL BE databases, run the following command:
  Install-CsDatabase -DatabaseType PersistentChat -SqlServerFqdn <PChatBE.FQDN> -SqlInstanceName <DBInstance> -Verbose
Note 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
Note In this command, <SQLServer.FQDN> is a placeholder for the appropriate value.