As most of us had been waiting for the release of Lync Server 2013 CU1’s release, it was officially available for download on February (close to a month back). Some may have updated the system and some may be still puzzling what would be the correct method, I’ve compile a step-by-step guide (for reference purposes only) to update CU1 on a Enterprise Edition Pool (EE) Server:

Step 1: Download the updates where you may refer from here. I suggest that to download the entire installer and let Lync Server 2013 detects the requires updates. If your Lync Server doesn’t allow direct Internet access, then you’ll need to download the components based on the server roles that has been deployed. In this guide, it is assumed that the Lync Server 2013 that will be deploying the CU1 has Internet access.

Step 2: Starting from the Pool Server, execute the CU1 Installer and click on the Install Updates


Wait for the Installer to execute and updates the Lync System


When prompt for reboot, click on Yes


Step 3: Once the system is back online, it is time to update the backend database. As I do not have any mirrored database configured within my environment, the only command that needs to be execute are as follows:

Install-CsDatabase -ConfiguredDatabases -SqlServerFqdn -Verbose

Step 4: Update the CMS Server by running the cmdlet:

Install-CsDatabase -CentralManagementDatabase -SqlServerFqdn -SqlInstanceName InstanceName -Verbose

Step 5: Commit the changes to the Topology builder:


Step 6: Once the Topology has been updated and publish. Run the following command to ensure that the changes are propagated across all of the server roles:

Get-CSManagementStoreReplicationStatus -CentralManagementStoreStatus


Repeat Step 1 – Step 5 applying CU1 on the other server roles as well:

Under the Access Edge Server, run the same CU Server Update Installer and select Install Updates

CU1_Access Edge

Upon completion, the Access Edge services will be automatically restarted

CU1_Access Edge Updating