This July update takes the server to 5.0.8308.992 from March’s 5.0.8308.987. This time ’round 6 components receive an update – and its mysteries have me VERY curious…
- Kb 4034279 Enables the “Move-CsMeetingRoom” cmdlet to move a meeting room from on-premises to Online in Lync Server 2013
- Kb 4023333 Peer to peer application sharing is available in Skype for Business on Mac in a Lync Server 2013 environment
- Kb 4023332 Delegate can pick up Peer to Peer call on behalf of delegator now in a Lync server 2013 environment
- Kb 4023331 Improves Contact Management in Skype for Business on Mac in a Lync server 2013 environment
- Kb 4023330 Enables you to manage delegates and set up simultaneous ring feature in a Lync Server 2013 environment
- Kb 4023329 Enables you to subscribe presence for contacts in contact lists in Lync Server 2013
- Kb 4023328 Introduces new Application Programming Interface (API) to manage contacts and groups on Mac in Lync server 2013
- Kb 4023327 Adds “CsHybridApplicationEndpoint” cmdlets to manage cloud voice or bot applications in Lync Server 2013
- Kb 4023326 PSTN call is dropped when it’s put on hold by a PSTN callee in Lync Server 2013
- Kb 4023323 Event ID 20003 is logged and UCWA may crash in Lync Server 2013
- Kb 4023322 Event ID 53106 “Unable to save message” is logged in Lync Server 2013 Persistent Chat Compliance Server
- Kb 4023320 “Your chatroom access may be limited due to an outage” error when you add or remove users in Lync Server 2013
- Kb 4023319 Incorrect caller ID is sent when admin makes an outgoing call on behalf of a manager in Lync Server 2013
There are a few bits of interest here. Firstly, one new P$ commandlet and the expected verb variations:
(We saw these appear in SfB CU5 back in May so it’s no great surprise to see them back-ported to Lync now).
This one particularly took my fancy so I thought I’d experiment some more:
Kb 4023332 Delegate can pick up Peer to Peer call on behalf of delegator now in a Lync server 2013 environment
Unfortunately my tinkering here amounted to nought, so I’ve polled my MS contacts and MVP peers to see if anyone knows what’s going on. Stay tuned…
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.
Yes, the installer prompted me to reboot.
13th July : This is the initial release.