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.
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.
With the recent release of UCS 5.0 for Polycom VVX Phones automatic firmware updates are now supported directly from the Lync Device Update service.
This is the same functionality which Lync Phone Edition devices have always used for firmware updates and now eliminates the need for a separate provisioning server in most Lync environments leveraging VVX Phones.
The Restore Version is initially blank and will be populated when this process is performed again with another newer update.
When approving a newer update the previously approved version will be moved to the Restore Version field which can then be used to easily roll-back devices to that older version.
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.The ) to indicate a newer version, in addition to the last four digits being incremented.As these letter codes come from engineering pre-release builds then whichever package makes it to general availability is the code that is used, so that is why they simply aren’t contiguous (e.g.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 update behavior of the VVX phones is very similar to that of Lync Phone Edition, yet is even more flexible.For LPE devices the update service is queried immediately after the initial registration and then again after a hard-coded period of time.) as that information is important when approving any pending updates.This part is nearly identical to how Lync Phone Edition updates are imported and approved in Lync Server, as documented in this previous article.That cmdlet basically puts the software into a staging area which does nothing until an administrator either approves or cancels the pending update.The Approved Version is exactly as it sounds: the version of software which the administrator has most recently approved for a given device mode.