Understand OS Patch Management Policy Reports

Determining which policies are applied to your devices and their current status is critical to making your job easier. The OS Patch Management Policy Report provides OS Patch Management Policy data in a single view and demonstrates organizational OS patch compliance.

IT Admins use the OS Patch Management Policy Report to perform these tasks:

  • Meet compliance requirements for OS patch management.
  • Troubleshoot issues with their devices.
  • Find outliers to current OS patch management policies in place, which helps find other devices that can potentially have the same issue.

Choosing Report Data Fields

The OS Patch Management Report contains these fields for each record:

  • policy_name – The OS Patch Management Policy that’s deployed on the device.
  • host_name – The host name as reported by the device via the JumpCloud agent.
  • display_name – The name or identifier as assigned by the administrator.
  • os_family – The specific OS running on the device.
  • os_version – The latest OS version running on the device as reported by the agent.
  • last_contact_timestamp – The timestamp for the last time that the JumpCloud agent reported back.
  • Note: If the device is currently in the process of updating, this field will display within the last 10 minutes.
  • policy_status – The current policy status as reported back via the JumpCloud agent.
  • exit_code – The digital representation of the policy_status.
  • exit_message_detail, exit_message_stderr, exit_message_stdout – The details reported back from the device as a result of the policy being applied.
  • Note: See Exit Message Data Section below.
  • device_created_timestamp – The timestamp for when the device was created on the JumpCloud platform.
  • device_object_id – The unique identifier for the device on the JumpCloud platform.

Understanding Report Behavior

The OS Patch Management Policy Report shows every device to which an OS Patch Management Policy has been deployed. Each individual record in the report displays the current status of the deployed policy on that device.


For devices where an OS Patch Management Policy has been deployed but the device hasn’t responded, the status for that device displays AWAITING DEVICE CHECK IN and the rest of the response fields will be null. After that device comes back online and receives the policy, the status and response fields are updated.

Running a Report

The OS Patch Management report can be requested from the report dropdown on the Reports tab. For instructions on how to run this report, see JumpCloud Reports.

Exit Message Detail

Because this report includes all operating systems, several different exit_message fields are provided to reflect as much detail as possible across each of the operating systems in scope. The exit message detail isn’t parsed, so as much forensic data as possible is provided to you for troubleshooting purposes. Don't expect all three of the exit message fields to be populated for each operating system.

Back to Top

Still Have Questions?

If you cannot find an answer to your question in our FAQ, you can always contact us.

Submit a Case