What is the first safe action for Kandji macOS Device Not Checking In?

- Device shows stale check-in or offline status in Kandji. - Blueprint changes and compliance updates are not reflected on the device. - Endpoint appears healthy locally but not reporting in admin console.

Does Kandji macOS Device Not Checking In require administrator access?

This runbook includes steps that require administrator access and should be handled by IT support.

When should this issue be escalated?

- Multiple Kandji-managed devices stop checking in at the same time. - Blueprint critical controls (security/compliance) are not applying. - Reenrollment or profile replacement is required under endpoint change control. Admin review or admin rights may be required for this step.

← Back to Corporate Tech Fixes

Designed for Enterprise IT Support & Corporate Environments

macOS

Kandji macOS Device Not Checking In

Troubleshoot Kandji-managed Mac endpoints that stop reporting/checking in by validating MDM enrollment state, local agent health, and network reachability before reenrollment. This troubleshooting guide is mirrored from the Support Portal knowledge base for quick access in Corporate Tech Fixes.

Severity: HighAdmin Required

Estimated Fix Time

20-40 min

Access Level

Admin Required

Total Steps

Author & Verification

Tamem J

IT Solutions Engineer

Last reviewed: March 3, 2026

Runbooks and troubleshooting guides are reviewed for enterprise-safe usage and avoid security bypass patterns.

• Enterprise Microsoft 365 Administration
• Endpoint Management (Intune, Jamf, Kandji)
• Identity & Access (Entra ID, Okta)

Tested on macOS Sequoia 15Tested on macOS Sonoma 14

Reviewed under Editorial Standards.

Trust Signals

No ratings yet

0 total helpfulness votes

• Enterprise Microsoft 365 Administration
• Endpoint Management (Intune, Jamf, Kandji)
• Identity & Access (Entra ID, Okta)

Reference This Page For

Best use cases

This page is meant to be the faster runbook reference when the issue pattern and access requirements align closely with the fix scope.

Use this fix when you need a shorter runbook-style response for Kandji macOS Device Not Checking In.
Best for macos issues where the access level is admin required and the estimated effort is 20-40 min.
Prefer this page when you want concise remediation, tested environments, and explicit escalation guidance without the longer support-portal framing.

Canonical URL

https://tamemj.com/corporate-tech-fixes/kb-kandji-macos-device-not-checking-in/

Editorial standards AI retrieval guide

#kandji#mdm#macos#check-in#enrollment#compliance#apple#support-kb

Note: “Download as PDF” opens the browser print dialog. Choose “Save as PDF” for a printable runbook copy.

Step-by-Step Resolution

Expand each section as needed

1
Symptoms
Info
Recommended validation or troubleshooting step
- Device shows stale check-in or offline status in Kandji. - Blueprint changes and compliance updates are not reflected on the device. - Endpoint appears healthy locally but not reporting in admin console.
2
Likely Causes
Info
Recommended validation or troubleshooting step
- Local MDM enrollment state is degraded or stale. - Kandji agent/service health issue after update or reboot cycle. - Network/proxy path blocks required management endpoints.
3
Confirm scope, user impact, and reproduction
Info
Recommended validation or troubleshooting step
Document whether the issue affects one user, multiple users, or multiple devices. Confirm exact error messages, recent changes (password reset, update, network change), and whether the same issue reproduces in web vs desktop workflows where applicable.
4
Validate prerequisites and application/session state
Info
Recommended validation or troubleshooting step
Confirm the user is signed in with the correct corporate account, system time is accurate, network/VPN connectivity is stable, and the application is not running in offline or limited mode.
5
Run safe diagnostics from the Commands section
Info
Recommended validation or troubleshooting step
Use the command snippets below to collect non-destructive diagnostics. Capture output in the ticket when escalation may be required. Avoid deleting profiles, cached credentials, or managed app data unless the runbook or admin approval explicitly allows it.
6
Apply safe remediation steps
Info
Recommended validation or troubleshooting step
- Confirm user connectivity and collect last known successful check-in time. - Validate MDM enrollment and profile status before any unenroll action. - Collect local process/log evidence and compare against known-good managed device. - Re-sync/repair through approved endpoint workflow; avoid unmanaged reenrollment shortcuts.
7
Escalate when access, policy, or security controls are involved
Warning
Review carefully before proceeding
- Multiple Kandji-managed devices stop checking in at the same time. - Blueprint critical controls (security/compliance) are not applying. - Reenrollment or profile replacement is required under endpoint change control.
Admin review or admin rights may be required for this step.
8
Check enrollment status and MDM profile state
Command
Includes a copyable command block
Command
```
profiles status -type enrollment
profiles show -type enrollment
```

Collect agent/process and MDM client diagnostics

Command

Includes a copyable command block

Command

ps aux | grep -i kandji | grep -v grep
log show --last 30m --predicate 'process == "mdmclient"' --style compact | tail -120

10
When to Escalate to IT / Security
Warning
Review carefully before proceeding
- Multiple Kandji-managed devices stop checking in at the same time. - Blueprint critical controls (security/compliance) are not applying. - Reenrollment or profile replacement is required under endpoint change control.