The Office Communications Server 2007 R2 Device Update Service is implemented in a different method from the Software Update Server in Office Communications Server 2007. Because Device Update Service is a Web component of the Front End Server, rather than a SharePoint site, the only migration option is to do the following:

  1. Install and configure the new Device Update Service.

  2. Use DNS to point the hardware devices to the new service. DNS requirements for the Device Update Service are similar to those for the Software Update Server: a DNS A record is created that points the hardware device to the pool that is hosting the Device Update Service. For details, see DNS Requirements for Serversin the Planning and Architecture documentation.

  3. deactivate and remove the Office Communications Server 2007 Software Update Server. For details, see Device Update Servicein the Planning and Architecture documentation.

You may have existing Office Communications Server 2007 hardware client devices, including Microsoft Office Communicator Phone Edition and the Microsoft RoundTable conferencing device, running a build older than 522.103. If you do, then follow these steps to update these devices to be fully compatible with Office Communications Server 2007 R2.

  1. Update the device to the 1.0.522.103 version. The 1.0.522.103 update is built in to the Office Communications Server 2007 R2 Device Update Service.

  2. Have the device’s user calibrate the screen, and then log in to the device.

  3. Once logged in, the user should reboot the device to trigger an request to update to the R2 version of the device software. Otherwise the device will wait 24 hours before updating to R2.

For details about installing these updates, see Using Device Update Service Management Consoleand Administering Device Update Service, which are both in the Administering Office Communications Server 2007 R2 documentation.

For information on updating clients located outside your organization’s firewalls, see Migrating Clients Outside the Firewall.

For details about user experience during this phase, see User Experience During Phase 9.