Check for Updates
Topic Last Modified: 2012-05-21
Devices check for updates when they are restarted. If restarting does not start an update check, devices check for updates after logon. Updates are extracted to the Device Update file store on Web Services. The device sends its current version information to the Device Update Web service, which checks if there is a newer update for that device type. If so, the Device Update Web service sends the path to the update. The device then downloads the update from that location and waits five minutes before applying it. For details about where to find the device logs, see Updating Devices.
Issue 1: Device Cannot Connect to the Device Update Web service
Issue: Device displays an error indicating that it cannot connect to the Device Update Web service and that an update must be downloaded.
Resolution: Verify that the Device Update Web service is available by opening a web browser and typing the Device Update Web service path: http://ucupdates-R2.<SIP domain>:443/RequestHandler/ucdevice. If you cannot connect, there is a problem on the Internet Information Services (IIS) web server that hosts the Device Update Web service and it needs to be resolved. You can also verify which address the device is trying by uploading the device’s log files to the Device Update Web service log file store and reviewing the log file.
If you are able to connect, verify that the Device Update Web service address is correctly published in the Domain Name System (DNS). To do this, open a command prompt on a computer running Windows, and type the following: nslookup <Device Update Web service path>. If this is unsuccessful, the record is not available in DNS. Check the organization’s DNS setup.
Issue 2: Device Cannot Locate Device Update at Path Provided
Issue: The device is unable to download the update from the location provided by the Device Update Web service.
Resolution: Verify which path the device is trying, by uploading the device’s log files to the Device Update Web service log file store, and reviewing the log file. Type the pate in a web browser and determine whether this resolves the issue. If not, go to the Device Update Web service and remove the updates using the Lync Server Management Shell, and then import them again. This should resolve any problem with the file or folder structure on the Device Update Web service.