This March update takes the server to 5.0.8308.987 from January’s 5.0.8308.984. Only two components need updating this time ’round.
- Kb 4016533 OAuth authentication fails in Lync Server 2013 that has the January 2017 cumulative update installed
Nothing apparently. I can confirm no new PowerShell Commandlets materialised following its installation.
Here’s the “before” view of it going on to my Standard Edition Front-End:
After you’ve run the installer & updated the databases (if required), don’t overlook the final few steps:
- Enable-CSTopology – which will fail if you have SfB2015 co-existing, so don’t be frightened by the error “Command execution failed: “1” error categories reported in topology document.”
- Fire off the bootstrapper: %ProgramFiles%\Microsoft Lync Server 2013\Deployment\Bootstrapper.exe
- And if you’ve skipped an update or two, best run Update-CsAdminRole after you’re done to make sure the new commandlets added in previous updates are accessible when PS Remoting.
No, one was not required.
19th March : This is the initial release.
25th March : Added details of the issue fixed in this update. (Thanks Soder).
Only an Oauth bug was fixed: