Web updating software
In LPE it is not possible to control the update behavior in this manner and it is all automatic.Note that this article is quite lengthy as the entire process is described in detail, accompanied by various log entries and other examples.The only differences are how the updates are packaged and where they are stored on the server.
The example used in the remainder of this article is a Polycom VVX 410 phone running 188.8.131.5274 firmware, registered externally via an Edge Server to a Lync Server 2013 environment.
Yet in practice using the Lync Device Update service for VVX phone updates is identical to the process used by LPE devices.
So when working with a Lync Server already setup for LPE updates then adding VVX updates is as simple as importing and approving the new packages.
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.