Site not updating
It is always possible that a new firmware version does not operate as expected in some environments so if an issue is discovered soon after upgrading to a new version then being able to roll-back the devices to the previous release is critical.Existing phones would have been updated to the 5.0.0 release using some means other than device update service so if the 5.0.0 version is not loaded into the Lync Server prior to approving the 5.0.1 version then it will not be possible to roll-back firmware by using the ) is the same as where other device updates are stored, but instead of being placed under the UCPhone subdirectory these packages as well as device updates from other qualified devices like Snom are stored under the 3PIP sub-directory.
This part is nearly identical to how Lync Phone Edition updates are imported and approved in Lync Server, as documented in this previous article.If a new update is available LPE devices will wait for a certain period of inactivity on the phone and then automatically download, waiting again for more idle time before rebooting itself to complete the process.VVX devices operate in the same way but also offer two important improvements: (1) the inactivity timeout is configurable and (2) when a new update is available the device will prompt the user to install it immediately if desired, or defer if not.If there were any problems connecting to the device update service on the Lync Server (internally or externally) then this status window would report a connection failure.To further validate that this device was successfully connected to the update service the server’s device log can be checked for any entries associated with the device.The phone must also be successfully registered to a Lync Server in order for this capability to function.
The example used in the remainder of this article is a Polycom VVX 410 phone running 126.96.36.19974 firmware, registered externally via an Edge Server to a Lync Server 2013 environment.
(‘3PIP’ is an acronym for Microsoft’s Although the package is now installed on the Lync Server it is not yet available for applicable devices to utilize.
A quick check of the device updates status on the phone at this point would show that there is still no available update.
Although the 5.0.0 release added the ability to leverage the Device Update service it was not yet possible to actually leverage the feature until a new update was published.
Now that the 5.0.1 maintenance release is available then this and all future releases can be handled natively by the Lync server.
The following preparation steps do not need to be performed on any devices but are included to illustrate key behavior in the process as well as verify a functional device update service.