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.
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.
) 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.
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.
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.
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.
It is important to understand what the three version fields represent in the device update configuration.