Polycom ip phone updating initial configuration
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.
As this example environment does not yet have any device update packages for VVX phones imported into the Lync Server then the phone should report that there is currently no update available.
The only differences are how the updates are packaged and where they are stored on the server.
As important as upgrading the firmware is, having a way to reverse the update is just as imperative.
) as that information is important when approving any pending updates.
The example used in the remainder of this article is a Polycom VVX 410 phone running 184.108.40.20674 firmware, registered externally via an Edge Server to a Lync Server 2013 environment.
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.
The experienced Lync administrator can skip to the last section entitled “Lync Pro Guide” for the abbreviated steps.
The following table lists Lync-qualified UCS releases which support native device updates and will continue to be updated as future releases are posted online, including links to both Release Notes and the software packages.