To function efficiently, the basic device management service uses a pull model instead of a push model. The target 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 target device to connect to a server for management and application updates.
   
   
2. Periodically, the device management service on the target device connects to the server using HTTP or HTTPS, as configured on the target device, to check if there are any updates.
   
   
3. The target 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 target device is supposed to have, including optional packages. The response may also include requests for specific reports from the target device.
   
   
5. The target 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 target device sends a download instruction request for each package that is needed.
   
   
7. For each requested package, the server responds with an instruction response. The instruction response contains the download instructions for the package.
   
   
8. For each download instruction response received by the target device, the target device schedules a download event. A download event consists of four phases:
   
   
   1. The target device sends a package location request message to the server to get the current download URL. The server responds with a package location response.
      
      
   2. The target device raises a status report that indicates the beginning of the download event.
      
      
   3. The target device raises 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 target device should execute after the package is downloaded.
      
      
   4. The target device raises a status report that indicates the end of the execution of the post install command.
      
      
9. If requested by the server, the target device also sends software inventory reports, machine inventory reports, or file collection reports to the server.
   
   

See Also