Device Update Service is automatically installed with Office Communications Server 2007 R2. Prior to installation, however, there are additional deployment steps you must take, including creating a file storage location and configuring the environment so that UC devices can discover and connect to Device Update Service. These additional steps are described in .
Following deployment, you can check to make sure Device Update Service is functioning properly by verifying that a test device can connect to it, and then by verifying that the service is accessible to external devices. You can also use these procedures to check any time you are concerned that the service is not functioning properly. After using these procedures, if you find that Device Update Service is not functioning properly, ensure that you have taken the required additional deployment steps, take any omitted steps, and perform the verification steps again.
|In previous releases of Office Communications Server, UC devices operating outside the firewall connected to the update service by using anonymous access. In this release, to enhance security, UC devices by default must use NTLM authentication. This means that a user must be logged on to the device with a valid user account in order for an external device to connect to Device Update Service and receive updates. For details on deployment requirements for external device access, see .|
To verify Device Update Service functionality
Add a test device to Device Update Service Management Console, as described in Adding Test Devices.
Turn off the test device and then turn it back on, so that it connects to Device Update Service and checks for updates.
Check the audit logs in the imageUpdates folder to verify that the device sent an update request to Device Update Service and received a response. For details, see Auditing Update Requests.
Check the device System Informationscreen to verify that it has the expected firmware version.
If your deployment is configured to allow access to external devices, verify that the external URL is available outside of your organization’s firewall by connecting the test device to an external network, logging on to the device with a valid user account, and repeating steps 2, 3, and 4.