#Skype4B : Install cumulative updates on Skype for Business Part II


This post is a continuation of my preceding post which describes Lync/SfB CU installation process. In this part, I’ll follow the steps which are mentioned in my preceding post and will update my SfB Enterprise Edition pool.

To begin with the CU installation process, download SfB cumulative update and copy it to all the SfB servers.

Open SfB management shell on one of the FE server.

Run Get-CsPoolUpgradeReadinessState to verify the pool readiness state. State should be Ready for the pool and IsReadyForUpgarde should be True for all the upgrade domains with in the same pool.

Run Invoke-CsComputerFailover -NoStop -ComputerName <Computer.FQDN> to failing over the FE server which needs to be updated.

The above cmdlet will disable all the SfB services.

Now, stop all the services by running Stop-CsWindowsService -Graceful

Cross verify the services state through services.msc

Note: Run SkypeServerUpdateInstaller.exe, it will verify all the SfB services state if services are running it will show you all the services which are running or in paused state. Stop all the services and run again.

Once everything is fine, update installer will come up and you can click on Install Update tab to start the installation.

Command prompt will show you the progress.

After successful installation server will reboot.

After reboot you can verify the services, you will find all the services are still in disabled state.

Now, you need to run Invoke-CsComputerFailback -ComputerName <Computer.FQDN> to failback the computer.

Once failback will complete, you can see the message “Machine <FE.fqdn> successfully failed back.

And you can verify all the services.

Now, follow the same process for all the SfB servers except Back End database servers.

Part III of this post will cover the Back End and CMS update process.

1 thought on “#Skype4B : Install cumulative updates on Skype for Business Part II

  1. Baasky

    One suggestion, instead of running Invoke-CsComputerFailover -NoStop -ComputerName and then Stop-CsWindowsService -Graceful, Run Invoke-CsComputerFailover -ComputerName this will do both.

    Like

    Reply

Leave a comment