November 2014 Cumulative Update 5.0.8308.834 for Lync Server 2013 core components

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.

• 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 updates (5.0.8308.420)
• February 2013 cumulative updates (5.0.8308.291)

To install updates for Lync Server 2013 RTM (5.0.8308.0), you must follow 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 updates

Important 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-CsPoolUpgradeReadinessState cmdlet and that you have the appropriate number of Lync Server 2013 front-end servers 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.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

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, you must 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 for at least three consecutive times after you wait 10 minutes in between every time that you try, or if you see any result of InsufficientActiveFrontEnds for the State value of the pool, there is an issue with 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 failure recovery topology, you must fail the pool over 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:
   How to fail over a pool
   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:
3. 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 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 

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

   
   Notes 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.
2. Restart the server if it is required by the installation wizard.

Step 2: Apply the back-end database updates

After 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 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 Edition

You 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 ExcludeCollocatedStores parameter.

Note If database mirroring is enabled for your back-end databases, we strongly recommended that you use the Invoke-CsDatabaseFailover -NewPrincipal Primary cmdlet and 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 Databases

When 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 Databases

When 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 update

Note You do not have to update the Central Management Database in the following instances:

• If the Central Management Store is homed on a Lync Server 2010 Standard Edition Server or Enterprise pool, do not run the Install-CsDatabase -CentralManagementDatabase cmdlets.
• If the Central Management Store is homed on a Lync Server 2013 Standard Edition Server or Enterprise pool that was previously updated with the Lync Server 2013 February 2013 cumulative updates, do not run the Install-CsDatabase -CentralManagementDatabase cmdlets.

After the Lync Server 2013 Enterprise Edition front-end server or the Lync Server 2013 Standard Edition Server back ends are updated, run the following cmdlet to update the Central Management Store:

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

Note In a coexistence environment that contains both Lync Server 2010 and Lync Server 2013 in which the Central Management Service is located on a Lync Server 2010 pool, do not run the Install-CsDatabase -CentralManagementDatabase cmdlet. If you later move the Central Management Service to a Lync Server 2013 pool, you have to run the Install-CsDatabase -CentralManagementDatabase cmdlet to apply the changes.

Step 4: Enable the Mobility service

To enable the Mobility service, run the following cmdlet:

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 

Prerequisites

There are no prerequisites for installing this cumulative update.

Registry information

To use one of the cumulative updates in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this cumulative update.

Update replacement information

This cumulative update replaces the cumulative update 5.0.8308.831 for Lync Server 2013 core components.

Update package installation information

To apply this cumulative update, run the OcsCore.msp on computers that are the following server roles:

• Lync Server 2013 - Standard Edition Server
• Lync Server 2013 - Enterprise Edition - Front End server
• Lync Server 2013 - Director
• Lync Server 2013 - Edge Server
• Lync Server 2013 - Stand-Alone Mediation Server
• Lync Server 2013 - Monitoring Server
• Lync Server 2013 - Archiving Server
• Lync Server 2013 - Administration Tools
• Lync Server 2013 - Persistent Chat Server
• Lync Server 2013 - Trusted Application Server