指南

Why Use Jamf Device Checker?

The Problem

End users often experience device issues that impact their productivity but don't know how to identify or resolve them:

• Missing or outdated apps versions
• Outdated iOS versions
• Low battery health causing unexpected shutdowns
• Storage capacity issues preventing app installations
• Network connectivity problems affecting productivity
• Device overheating causing performance throttling
• High memory/CPU usage slowing down work

These issues typically result in help desk tickets, lost productivity, and frustrated users.

The Solution

Jamf Device Checker empowers end users to self-diagnose and resolve device readiness issues through a simple, color-coded interface:

• ✅ Green = Device is ready for work
• ⚠️ Yellow = Warnings that should be addressed soon
• 🔴 Red = Critical issues preventing productivity

Key Benefits

For End Users: self-service device readiness checks, clear actionable guidance for fixing issues, reduced wait time for IT support, and proactive notifications before deadlines.

For IT Teams: reduced help desk tickets, compliance enforcement with corporate policies (OS versions, required apps), real-time visibility into device health, and configurable thresholds and monitoring rules.

For Organizations: improved end-user productivity, better device lifecycle management, reduced IT support costs, and compliance tracking and reporting.

Overall Status Display

The app displays a large, color-coded status indicator at the top of the main screen that summarizes the device's overall readiness.

Quick Start

Prerequisites

• Jamf Pro server (JPS)
• Admin access to Jamf Pro
• Jamf Self Service app (required for app installation feature)
• Local user account with wizard privileges (see below)

Required API Privileges

The app uses two distinct sets of privileges:

For Wizard Setup (Local user account — used during initial configuration):

Create a local user in Jamf Pro with these 8 privileges:

API Integration Setup (one-time wizard configuration):

• Read API Integrations
• Create API Integrations
• Update API Integrations
• Read API Roles
• Create API Roles
• Update API Roles

App Config Management (wizard + ongoing updates):

• Read Mobile Device Applications
• Update Mobile Device Applications

This user account authenticates the wizard via Basic Auth to create the API integration, configure roles, link the native app, and save app config XML. After initial setup, this user is only needed for app config updates (requires only the 2 Mobile Device Applications privileges).

For Runtime Operation (OAuth API client — automatically configured by wizard):

The wizard automatically creates a "Jamf Device Checker" API role with these 4 privileges assigned to the linked app integration:

• Send Device Information Command
• View MDM command information in Jamf Pro API
• Read Mobile Devices
• Send MDM command information in Jamf Pro API

These privileges allow the device checker to fetch device details and send MDM commands during normal operation using OAuth authentication. End users never see or use these credentials.

5-Minute Setup

Step 1: Purchase and add the app to Jamf Pro

• Purchase "Jamf Device Checker" and assign to Jamf Pro instance in AxM
• Navigate to Mobile Device Apps in Jamf Pro
• Add "Jamf Device Checker" from Apps Purchased in Volume

Step 2: Run the Setup Wizard

• Install the app on your admin device
• Launch the app and long-press the circular status image to enable Wizard mode
• Authenticate with local user (requires 8 wizard privileges — see Required API Privileges above)
• Follow the wizard to:
  • Configure API role with required privileges
  • Create API integration
  • Link native app to API integration for authentication
  • Generate managed app config and save to JPS

There is no step 3 — just scope to end-user devices.

Full Setup Instructions

Step 1: Add Mobile Device App to Jamf Pro

• Purchase "Jamf Device Checker" and assign to Jamf Pro instance in AxM
• Log into Jamf Pro
• Navigate to Devices > Mobile Device Apps
• Click + New
• Search for "Jamf Device Checker" in Apps Purchased in Volume
• Click Add to add the app record to your Jamf Pro instance

Step 2: Run the Setup Wizard

The wizard handles all the authentication and managed app configuration automatically.

Install App on Admin Device

• Assign the app to a test iOS device
• Launch Jamf Device Checker

Enable Wizard Mode

• On the more tab, long-press the app icon for 3 seconds
• Select Wizard Setup
• Authenticate with the local user credentials created in Prerequisites (requires the 8 wizard privileges)

Complete Wizard Steps

API Role

• Wizard checks for existing "Jamf Device Checker" API role
• If not found, creates role with required privileges:
  • Send Device Information Command
  • View MDM command information in Jamf Pro API
  • Read Mobile Devices
  • Send MDM command information in Jamf Pro API
• Links role to API integration

Native App Authentication

• Wizard links the mobile device app record to the API integration
• Enables OAuth authorization code delivery via Managed App Config

Generate App Config

• Wizard generates complete Managed App Config
• Sends to Jamf Pro

Step 3: Scope to Devices

• In the same app record, click Scope
• Add target device groups, smart groups, or individual devices
• Click Save

Configuration Reference

The app is configured entirely through Jamf Pro's Managed App Config. Below is a complete reference of all available keys.

Required Keys

These keys are automatically populated by Jamf Pro — do not modify or remove them.

Branding & Alerts URL

Example:

<key>device-checker-branding-image-url</key>
<string>https://yourcompany.com/logo.png</string>
<key>device-checker-branding-image-height</key>
<string>60</string>

Share Buttons

Control visibility of status sharing and log export features in the More tab.

Example:

<key>device-checker-send-status-enabled</key>
<string>YES</string>
<key>device-checker-send-logs-enabled</key>
<string>NO</string>

UI Behavior

Control the scrolling behavior of the Status tab.

Example:

<key>device-checker-status-tab-scrollable</key>
<string>NO</string>

When to enable: The default (NO) is best for most deployments — the header and overall readiness status remain visible while scrolling through tiles. Set to YES when you need the entire view to scroll together, or to accommodate longer branding headers on smaller devices.

Operating System Readiness

Monitor OS version requirement with configurable minimum version and deadline.

Example:

<key>device-checker-os-enabled</key>
<string>YES</string>
<key>device-checker-os-min-version</key>
<string>26.2</string>
<key>device-checker-os-deadline</key>
<string>2026-06-30</string>

Status Logic:

✅ Green (Ready) — Current OS version meets minimum requirement

⚠️ Yellow (Warning) — Current OS version below minimum, but deadline has NOT passed (or no deadline configured)

🔴 Red (Not Ready) — Current OS version below minimum AND deadline has passed

App Readiness

Monitor installation status and version requirements for required managed apps.

App List Format:

AppName,bundleID,minVersion,deadline|AppName2,bundleID2,minVersion2,deadline2|...

Example:

<key>device-checker-apps-enabled</key>
<string>YES</string>
<key>device-checker-apps-list</key>
<string>Slack,com.tinyspeck.chatlyio,24.0.0,2026-03-01|Microsoft Teams,com.microsoft.skype.teams,5.0.0,2026-06-01</string>

Status Logic:

✅ Green (Ready) — All apps installed and meet minimum versions

⚠️ Yellow (Warning) — One or more apps need updating, but deadline has NOT passed

🔴 Red (Not Ready) — One or more apps need updating AND deadline has passed

⏳ Pending — App installation in progress (see Self Service integration below)

Self Service Integration:

When apps are missing or outdated, users can tap the "Update Apps" button on the Apps tile to automatically install or update required apps. The workflow is:

1. User taps "Update Apps" button on Apps tile
2. Jamf Self Service app opens automatically with missing/outdated apps queued
3. Device Checker enters "Pending" status and starts a 2-minute auto-refresh timer
4. App automatically refreshes every 2 minutes to check if installations completed
5. Once all apps meet requirements, status returns to green

Requirements: Jamf Self Service must be installed on the device, apps must be available in Self Service and scoped to the device, and apps must have "Display app in Self Service after it is installed" checked in Jamf Pro.

Notes:

• Bundle ID must match exactly (case-sensitive)
• Version comparison uses semantic versioning (e.g., 2.5.0 > 2.4.9)
• Deadline is optional (leave blank if not needed: AppName,bundleID,minVersion,)

Power Source (Battery Level)

Monitor battery charge level with configurable warning and critical thresholds.

Example:

<key>device-checker-power-source-enabled</key>
<string>YES</string>
<key>device-checker-power-source-warning</key>
<string>25</string>
<key>device-checker-power-source-critical</key>
<string>10</string>

Status Logic:

🔴 Red (Critical) — Battery ≤ critical threshold

⚠️ Yellow (Warning) — Battery ≤ warning threshold (but > critical)

✅ Green (Ready) — Battery > warning threshold

⚡ Charging — Device is plugged in (always green when charging)

Storage Capacity

Monitor available storage with configurable warning and critical thresholds (based on percentage used).

Example:

<key>device-checker-storage-enabled</key>
<string>YES</string>
<key>device-checker-storage-warning</key>
<string>75</string>
<key>device-checker-storage-critical</key>
<string>90</string>

Status Logic:

🔴 Red (Critical) — Storage used ≥ critical threshold

⚠️ Yellow (Warning) — Storage used ≥ warning threshold (but < critical)

✅ Green (Ready) — Storage used < warning threshold

Battery Health

Monitor battery health status to identify devices that may need battery replacement. This tile displays battery health status and current charge percentage.

Example:

<key>device-checker-battery-enabled</key>
<string>YES</string>

Status Logic:

✅ Green (Ready) — Battery health is "Normal" or "Unsupported"

🔴 Red (Not Ready) — Battery health is "Service-Recommended" or "Non-Genuine"

⚪ Gray (Unknown) — Battery health is "Unknown" or unable to retrieve battery data

Health Status Values:

• Normal — Battery is functioning properly (Green)
• Service-Recommended — Battery capacity has degraded, replacement recommended (Red)
• Non-Genuine — Non-Apple battery detected, replacement recommended (Red)
• Unsupported — Battery health monitoring not available on this device model (Green, shows charge % only)
• Unknown — Health data not yet available from iOS (Gray, shows charge % only)

Tile Display: The status color and icon are based on battery health. The subtitle shows the battery health issue if present, otherwise shows current charge percentage. The detail view shows charge level, charging state, Low Power Mode, battery health status, and recommendations.

Notes:

• Battery health data comes from Declarative Device Management (DDM)
• New devices may show "Unknown" until iOS calculates health metrics (typically after a few charge cycles)
• Charge percentage is always displayed in the subtitle or detail view
• This tile focuses on battery health; use the Power Source tile for charge level monitoring with thresholds

Thermal State

Monitor device temperature in real-time using local iOS APIs (no MDM calls required).

Example:

<key>device-checker-thermal-enabled</key>
<string>YES</string>

Status Logic:

✅ Green (Nominal) — Normal operating temperature, all features operating normally

⚠️ Yellow (Fair) — Slightly elevated, system defers background work like prefetching/indexing

🔴 Red (Serious) — High temperature, CPU/GPU throttling active, frame rates may drop to 30 FPS

🔴 Red (Critical) — Device critically hot, significant throttling, camera/flash/speaker may disable, risk of shutdown

Use Cases: field devices in hot environments (vehicles, outdoor work), users running intensive apps (video recording, AR), proactive warnings before thermal shutdowns, and understanding performance throttling.

Notes: Real-time monitoring via iOS ProcessInfo API. No API calls or battery drain. Updates instantly when thermal state changes.

Performance (Memory & CPU)

Monitor device memory pressure and CPU usage using local iOS APIs with configurable thresholds.

Example:

<key>device-checker-performance-enabled</key>
<string>YES</string>
<key>device-checker-memory-warning</key>
<string>70</string>
<key>device-checker-memory-critical</key>
<string>85</string>
<key>device-checker-cpu-warning</key>
<string>60</string>
<key>device-checker-cpu-critical</key>
<string>80</string>

Status Logic:

🔴 Red (Critical) — Memory OR CPU ≥ critical threshold

⚠️ Yellow (Warning) — Memory OR CPU ≥ warning threshold (but < critical)

✅ Green (Ready) — Both memory AND CPU < warning thresholds

Notes: Updates every 5 seconds when tile is visible. Monitoring pauses when app is in background (to save battery). No remote API calls required — entirely local monitoring via os_proc_available_memory() for memory and host_statistics() for CPU.

Network Status

Monitor WiFi, Ethernet, and cellular connectivity status.

Example:

<key>device-checker-wifi-enabled</key>
<string>YES</string>
<key>device-checker-cellular-enabled</key>
<string>YES</string>
<key>device-checker-network-speed-enabled</key>
<string>YES</string>

Network Speed Test Details:

The speed test is an on-demand diagnostic tool (~10–15 MB per test, ~15–20 seconds duration) that measures download/upload speeds and latency. A warning is shown before every test on cellular to advise of data usage. Results are informational only and do not affect device readiness status. Use cases include field workers verifying connectivity, troubleshooting slow performance, and validating bandwidth requirements.

Internet Connectivity Test (WiFi, Ethernet, and Cellular)

Lightweight test to verify actual internet reachability vs. just interface connectivity.

Example:

<key>device-checker-internet-connectivity-test-enabled</key>
<string>YES</string>
<key>device-checker-internet-connectivity-test-timeout</key>
<string>5</string>
<key>device-checker-internet-connectivity-test-cache-ttl</key>
<string>60</string>

How It Works: Sends a lightweight HEAD request (~200–500 bytes) to Apple's captive portal endpoint. Tests run automatically when an interface connects or when network detail views are opened (if cache has expired). Results are cached for 30 seconds on WiFi/Ethernet and a minimum of 60 seconds on cellular to minimize data usage. Network tiles show yellow/warning status if connected but no internet is detected.

Status Behavior by Interface:

WiFi — Green: connected with internet verified. Yellow: connected but no internet (captive portal, routing issue). Red: not connected.

Ethernet — Green: connected with internet verified. Yellow: connected but no internet (routing/firewall issue). Red: not connected.

Cellular — Green: enabled with internet verified. Yellow: enabled but no internet (carrier issue, account problem). Red: not available or disabled.

Data Usage: ~200–500 bytes per test (vs ~10–15 MB for speed test). WiFi/Ethernet with 30-second cache: less than 100 KB/day typical usage. Cellular with 60-second cache: less than 50 KB/day typical usage.

Status Logic Without Internet Connectivity Test:

WiFi: ✅ Green (Connected) — Connected to WiFi. 🔴 Red (Not Connected) — Not connected to WiFi.

Cellular: ✅ Green (Ready) — Cellular data available. ⚠️ Yellow (Warning) — Cellular access restricted. 🔴 Red (Error) — Cellular not available.

Jamf Setup Extension Attribute

Display on-duty/off-duty status from a Jamf Pro extension attribute.

Example:

<key>device-checker-jamf-setup-ea-enabled</key>
<string>YES</string>
<key>device-checker-jamf-setup-ea-name</key>
<string>Jamf Setup</string>
<key>device-checker-jamf-setup-ea-on-duty-value</key>
<string>On-duty</string>
<key>device-checker-jamf-setup-ea-off-duty-value</key>
<string>Off-duty</string>

Status Logic:

✅ Green (Ready) — EA value matches on-duty value

⚠️ Yellow (Warning) — EA value matches off-duty value

⚪ Gray (Unknown) — EA not found or value doesn't match either configured value

Notes: Requires a custom extension attribute in Jamf Pro. The extension attribute must be populated by Jamf Setup or another method.

Auto-Refresh Throttling

Control how often the app automatically refreshes when returning from background.

Example:

<key>device-checker-auto-refresh-threshold</key>
<string>300</string>

Behavior:

• Default (300 seconds / 5 minutes): If the user switches apps and returns within 5 minutes, no auto-refresh occurs
• Custom threshold: Set to desired seconds (60–3600)
• Disable throttling: Set to 0 to always refresh when app becomes active

Always refreshes (throttling bypassed): first activation after app launch, when in pending state (auto-refreshes every 2 minutes), manual refresh button taps, and timer expiration during pending state.

Pending State Behavior: When the Apps tile enters "Pending" state (after user taps "Update Apps"), the app automatically checks device status every 2 minutes until all required apps are installed, regardless of the auto-refresh threshold setting.

Configuration Examples

Minimal Configuration (Default Settings)

Perfect for quick testing or basic deployments.

<dict>
  <!-- Required keys (auto-populated) -->
  <key>JPS_URL</key>
  <string>$JPS_URL</string>
  <key>JSSID</key>
  <string>$JSSID</string>
  <key>MANAGEMENTID</key>
  <string>$MANAGEMENTID</string>
  <key>OAUTH_AUTH_CODE</key>
  <string>$OAUTH_AUTH_CODE</string>
  <key>APP_CONFIG_REINSTALL_CODE</key>
  <string>$APP_CONFIG_REINSTALL_CODE</string>
  <key>APPJSSID</key>
  <string>$APPJSSID</string>

  <!-- Enable OS monitoring only -->
  <key>device-checker-os-enabled</key>
  <string>YES</string>
  <key>device-checker-os-min-version</key>
  <string>18.0</string>
</dict>

Full Configuration

Comprehensive setup with branding, multiple device status checks, and custom thresholds.

<dict>
  <!-- Required keys (auto-populated) -->
  <key>JPS_URL</key>
  <string>$JPS_URL</string>
  <key>JSSID</key>
  <string>$JSSID</string>
  <key>MANAGEMENTID</key>
  <string>$MANAGEMENTID</string>
  <key>OAUTH_AUTH_CODE</key>
  <string>$OAUTH_AUTH_CODE</string>
  <key>APP_CONFIG_REINSTALL_CODE</key>
  <string>$APP_CONFIG_REINSTALL_CODE</string>
  <key>APPJSSID</key>
  <string>$APPJSSID</string>

  <!-- Branding -->
  <key>device-checker-branding-image-url</key>
  <string>https://yourcompany.com/logo.png</string>
  <key>device-checker-branding-image-height</key>
  <string>60</string>

  <!-- OS Readiness -->
  <key>device-checker-os-enabled</key>
  <string>YES</string>
  <key>device-checker-os-min-version</key>
  <string>18.0</string>
  <key>device-checker-os-deadline</key>
  <string>2026-12-31</string>

  <!-- App Readiness -->
  <key>device-checker-apps-enabled</key>
  <string>YES</string>
  <key>device-checker-apps-list</key>
  <string>Slack,com.tinyspeck.chatlyio,24.0.0,2026-06-01|Microsoft Teams,com.microsoft.skype.teams,5.0.0,2026-09-01</string>

  <!-- Device Health Tiles -->
  <key>device-checker-power-source-enabled</key>
  <string>YES</string>
  <key>device-checker-power-source-warning</key>
  <string>30</string>
  <key>device-checker-power-source-critical</key>
  <string>15</string>

  <key>device-checker-storage-enabled</key>
  <string>YES</string>
  <key>device-checker-storage-warning</key>
  <string>70</string>
  <key>device-checker-storage-critical</key>
  <string>85</string>

  <key>device-checker-battery-enabled</key>
  <string>YES</string>

  <key>device-checker-thermal-enabled</key>
  <string>YES</string>

  <key>device-checker-performance-enabled</key>
  <string>YES</string>
  <key>device-checker-memory-warning</key>
  <string>75</string>
  <key>device-checker-memory-critical</key>
  <string>90</string>
  <key>device-checker-cpu-warning</key>
  <string>70</string>
  <key>device-checker-cpu-critical</key>
  <string>85</string>

  <key>device-checker-wifi-enabled</key>
  <string>YES</string>
  <key>device-checker-cellular-enabled</key>
  <string>NO</string>

  <!-- Network Speed Test (optional - disabled by default) -->
  <key>device-checker-network-speed-enabled</key>
  <string>NO</string>

  <!-- Internet Connectivity Test (optional - disabled by default) -->
  <key>device-checker-internet-connectivity-test-enabled</key>
  <string>NO</string>
  <key>device-checker-internet-connectivity-test-endpoint</key>
  <string>http://captive.apple.com/hotspot-detect.html</string>
  <key>device-checker-internet-connectivity-test-timeout</key>
  <string>3</string>
  <key>device-checker-internet-connectivity-test-cache-ttl</key>
  <string>30</string>

  <!-- Jamf Setup EA -->
  <key>device-checker-jamf-setup-ea-enabled</key>
  <string>YES</string>
  <key>device-checker-jamf-setup-ea-name</key>
  <string>Device Status</string>
  <key>device-checker-jamf-setup-ea-on-duty-value</key>
  <string>Active</string>
  <key>device-checker-jamf-setup-ea-off-duty-value</key>
  <string>Spare Pool</string>

  <!-- UI Options -->
  <key>device-checker-alerts-url</key>
  <string>https://status.yourcompany.com</string>
  <key>device-checker-send-status-enabled</key>
  <string>YES</string>
  <key>device-checker-send-logs-enabled</key>
  <string>NO</string>
  <key>device-checker-status-tab-scrollable</key>
  <string>NO</string>

  <!-- Auto-Refresh (10 minutes) -->
  <key>device-checker-auto-refresh-threshold</key>
  <string>600</string>
</dict>

Legal

• Use Agreement: Application End User License Agreement
• Privacy Policy: Jamf Privacy Policy