Cumulative Updates for Lync Phone Edition: April 2013


Microsoft Support released the following cumulative update packages for Microsoft Lync Phone Edition for Aastra 6721ip, Aastra 6725ip, HP 4110, and HP 4120, and Polycom CX500, Polycom CX600, Polycom CX3000, Polycom CX700, and LG-Nortel IP Phone 8540 telephones.

Author: Angela Corman, Microsoft Program Manager

Editor: Susan S. Bradley

Published: April 19, 2013

Product version: Microsoft Lync Phone Edition

Microsoft Support released the following cumulative update packages for Microsoft Lync Phone Edition for Aastra 6721ip, Aastra 6725ip, HP 4110, and HP 4120, and Polycom CX500, Polycom CX600, Polycom CX3000, Polycom CX700, and LG-Nortel IP Phone 8540 telephones.

Cumulative Updates

Release Highlights

About the Author

Angela Corman is a Program Manager on the Sustained Engineering Team for Lync. She has worked for Microsoft for 9 years. She is passionate about customer communications,  both from a technology standpoint and an information standpoint. Keeping our customers informed about updates and releases for our products is her personal mission.

 

Lync Server Resources

We Want to Hear from You

Keywords: cumulative update, Lync Phone Edition

Comments (8)
  1. cormanang@hotmail.com says:

    Petri:

    We don’t have UI controls in Lync Control Panel to select when the updates goes active.  However, updates can be approved using the PowerShell cmdlet Approve-CsDeviceUpdateRule.  With that, you have multiple options-

    1- Log into the Lync Server and approve the update only when they are ready for the update to start rolling out.

    2- Script the approval and create a scheduled task to execute automatically when the customer wants the updates to start.  That way, nobody has to stay up until 3AM Saturday if that is the desired time for an update to start rolling out.

  2. Petri X says:

    Angela,

    Thank you for your reply, but I'm speaking about the device update schedules. Last time I approved the latest firmware update and I could saw from the device update log that first device got update almost right away and the last device got it after 24 hours. All other were between those.

    Even the update does not take longer than some minutes and it will be not applied in middle of the call. But making the update in middle of day without any other control sounds a pretty bad for enterprise companies. It would be great if we can have "device update policy" and we can define: apply updates during night between 2 AM and 5 AM if updates are available. How do you see this?

  3. Hamish says:

    Has anyone had trouble with this update? After loading onto test devices, the backslash has now become a w, and I can't sign in at all on a CX3000

Comments are closed.