Share via


Reports to the Server (Windows Embedded CE 6.0)

1/6/2010

Reporting is an important part of the feedback loop when the target device is receiving updates from servers such as Systems Management Server. The following list shows the three types of reports that the target device can post to the server are:

Currently all reports will be sent only to the server that is configured in the registry. You cannot schedule report tasks to any other server by using scripts. For more information about specifying a server name in the registry, see Device Management Client Registry Settings.

The following steps show how all reports are generated and posted to the server in a similar way.

  1. In addition to a package list, the Server Response to the Device Poll also contains information that specifies the type of reports the server needs, and the frequency at which they should be reported in case they are recurring reports.
  2. The target device then posts the reports required by the server at the specified times.

The X-Device-Action header allows the server to determine that this is a status response.

All failures on part of the target device to post the required reports to the server are recovered as defined by the FailureRetryCount and FailureRetryInterval element settings in the Server Response to Device Poll message. Default values for these elements are determined from the device management client registry settings.

See Also

Concepts

Device Management Operation

Other Resources

Device Management Client Application Development