Sunday, August 19, 2018
Lync Server 2013 patching guide
Lync Server 2013 patching guide
Lync Server 2013 Patching Guide
This Post will describe you the process to update Lync servers to latest cumulative updates.Phase 1 Front-End and director Servers
1.0 Checking The Server
Check each Lync server in Enterprise Pool for Below points.
1.1 Verify Event viewer and Pending Reboots
Event ID 1029 will be logged in the application log if an application has been installed that requires a restart.
Run Below Commands in Powershell to view if there is pending reboot on Server
$rebootreqevents = get-eventlog -log application |where {$_.instanceID -eq "1029"}
$rebootreqevents
Check the first entries date and time. In this case it is Jan 11 20:32
Now run the following commands from powershell
$lastboot = Get-WmiObject -Class Win32_OperatingSystem
write-host "Last Server Reboot:`t" $lastboot.ConvertToDateTime($lastboot.LastBootUpTime)
You will get the following output
Please make sure Server is rebooted after last pending Reboot date.
1.2 Copy Lync Update Installer on local drive.
Copy the patches that have been downloaded to each server to be patched.
The core reason for this logic is that then during each install a set of logs per server will get generated when applying the patch, if the installer is run from a central share the logs will be overwritten each time and will make it difficult to troubleshoot.
1.3 Please Refer Below Flowchart for Upgrade Process
2.0 Preparing server for Upgrade
Step 1.
On a Front End Server in the pool, run the following cmdlet:
Get-CsPoolUpgradeReadinessState
Sample Output: -
If the State value of the pool is Busy, wait for 10 minutes, Run command again.
If you see Busy for 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 with the pool.
Do Not Proceed with patching in this case.
If the State value of the pool is Ready, go to step 2.
Step 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 ISReadyforUpgrade value for the upgrade domain that contains the server that you want to upgrade is True, you can upgrade the server. Go to step 3
Step 3.
Run Following command to check windows fabric.
Get-CsPoolFabricState -PoolFqdn "<name of the pool>"
Make sure all members of pool are mentioned in each service viz. MCU factory; Conference Directory; Routing; Lync 2015 Storage Service.
And make sure all of the routing groups have a primary and at least one secondary.
Step 4
Stopping Lync Services (Draining Server)
The follow are the steps required to take to drain a Lync server before any patching cycle begins
Draining a server is a good way to minimize disruptions but it must be noted that some disruption will occur, Server draining only allows calls that are currently active to stay up and running until they terminate. This does not apply for other areas in the lync client. The client will after a small period of time log back into another server and operate as normally. But you can imagine doing a patch cycle on all servers and moving users from one server to another (if it happens to be round robin) could lead to disruption for the user.
Run Following Command in PowerShell (run as Admin).
stop-cswindowsservice �graceful
Check If all services have been stopped by running following command:
Get-CsWindowsservice
PS: Once a server is patched and rebooted it will automatically start the services again.
3.0 Patching Server
3.1 Installing Lync update on Server
Navigate to the local copy of the patch and double click Lync update installer
In our case, Lync update installer have been placed in D:Lync Updates. (IN Geo)
Run Installer, following screen should appear
link download
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.