) 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.
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.
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.Using this option may, however, lead to broken references in the project.In such cases, you may need to reinstall those other packages.Initial release with support for Lync Device Update services in both Lync Server 2010 and Lync Server 2013.Also includes support for the following new features: * Boss/Admin (Shared Line Appearances) – Phase 1 * Better Together Over Ethernet (BTOE) – Phase 1 * Lync Address Book Web Query (ABWQ) * Call Park and Retrieval * Peer-to-Peer Video Calling (Lync 2010 only)Major release including Lync Qualification, hotfixes and the following new features: * Improved Lync Contact Card support with Call to and Transfer to Voicemail * Improved Boss/Admin transferring behavior * PIN Authentication support from web UI * Color Expansion Module support for Lync (previously only available in 4.x firmware)Maintenance release including hotfixes and the following enhancements: * Addressed bandwidth issues seen on some VVX models with CAC * Added new parameters to control various physical and display options Major release including hotfixes and the following new Lync features: * Enhanced BTo E 3.0.0 client with Audio playback support * Centralized Conference Control Protocol (CCCP) support * Exchange Autodiscover Support * Safe Transfer for Boss/Admin scenarios * Music On Hold Updated support for Skype for Business 2015 Server environments * Registration for Skype for Business Online tenants in Office 365 * Improved first time user sign-in experience including Time Zone selection Major release including hotfixes and the following new features: * Skype for Business themed UI for VVX 500/600 models * New Web Sign-In authentication method * Call Transfer UI improvements and support for distribution list expansion * * Updated Sf B User Interface on VVX 4xx, 5xx, 6xx series phone models * Join button available for Skype Meeting created by external parties * Device Lock screen redesigned with various improvements and contact photo support * Multi-Factor Authentication support added for some third parties like Ping Federate and Okta * Web Proxy Auto discovery (WPAD) Support * Support for the SILK audio codec * Hotdesking support for Lync/Sf B Server deployments * Manual network-based BTo E pairing without the need for physical Ethernet uplink In order to successfully download the UCS firmware package from the Lync Server to a VVX phone the device must first be running at least version 220.127.116.1174 which was the first officially released version to support the Lync Device Update service.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 18.104.22.16874 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.Force uninstall even if there are dependencies on it: when selected, uninstalls a package even if it's still being referenced in the project.This is typically used in combination with Remove dependencies to remove a package and whatever dependencies it installed.