Share via

Device Management Service Design

  • Article

To function efficiently, the basic service is designed as a pull model rather than a push-based model. The device periodically polls a server for new application offerings or packages. The user or administrator controls the frequency and the conditions of the polling.

The following process describes how the device management service works:

  1. The user or administrator configures the device to connect to a server for management and application updates.
  2. Periodically, the device management service on the device connects to the server using HTTP or HTTPS, as configured on the device, to check if there are any updates.
  3. The device posts its identification information to the server.
  4. The server sends back an https or http response with package list information about all the packages the device is supposed to have, including optional packages. The response may also include requests for specific reports from the device.
  5. The device compares the package list with its internal package database and computes all the packages it should have to conform to the list received. It also removes those packages that it already has that do not conform to the list.
  6. If packages are required, the device sends a download instruction request session for each package that is needed.
  7. The server responds with an instruction response. The instruction response contains the download instructions for the package.
  8. When the device receives the download instruction response, it schedules a download event. A download event consists of four phases:
    • The device sends a package location request message to the server to get the current download URL. The server responds with a Package Location Response.
    • The device sends a status report that indicates the beginning of the download event.
    • The device sends a status report that indicates the end of the download event. When the download is successful, it triggers the execution of the post install command. This is the command the device should execute after the package is downloaded.
    • The device sends a status report that indicates the end of execution of the post install command.
  9. If requested by the server, the device also sends software inventory reports, machine inventory reports, or file collection reports to the server.

See Also

Device Management Operation

 Last updated on Thursday, April 08, 2004

© 1992-2003 Microsoft Corporation. All rights reserved.