IT Support Portal

ServiceNow-style demo portal

Affiliate Disclosure

Some recommendations may include affiliate links. If you purchase through these links, the site may earn a commission at no additional cost to you. Recommendations are still selected for fit, safety, and support relevance.

Kandji macOS Device Not Checking In

If you are seeing "your admin has configured the application to block users", use this IT support runbook to validate symptoms, isolate likely causes, apply safe resolution steps, and escalate correctly in macOS enterprise environments.

Estimated time

20-40 min

Overview

This troubleshooting guide is aligned to the exact query "your admin has configured the application to block users" and focuses on enterprise-safe remediation for Kandji (macOS).

Severity: HighAdmin RequiredEnv: macOSAppleKandji (macOS)

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 designed to be the narrow, issue-specific reference when the support query, product, and environment closely match.

  • Use this page when the issue is closest to the exact query “your admin has configured the application to block users.”
  • Best for Apple / Kandji (macOS) troubleshooting in macOS enterprise environments.
  • Prefer this ticket when you need enterprise-safe steps, escalation criteria, and commands tied to this specific issue.

Symptoms of your admin has configured the application to block users

  • 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.

Likely Causes of your admin has configured the application to block users

  • 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.

Interactive Decision Tree

ITIL-style triage path powered by state machine logic.

How to Fix: your admin has configured the application to block users

Accordion runbook sections

  1. 1

    Confirm scope, user impact, and reproduction

    Info
    v

    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.

  2. 2

    Validate prerequisites and application/session state

    Info
    v

    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.

  3. 3

    Run safe diagnostics from the Commands section

    Command
    v

    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.

  4. 4

    Apply safe remediation steps

    Info
    v
    • 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.
  5. 5

    Escalate when access, policy, or security controls are involved

    WarningAdmin required
    v
    • 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.

Commands

Copyable diagnostic or remediation commands (2 snippets).

Check enrollment status and MDM profile state

Terminal

profiles status -type enrollment
profiles show -type enrollment

Collect agent/process and MDM client diagnostics

Terminal

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

When to Contact IT / Security

  • 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.

Recommended Partners for This Topic

Selected from your affiliate registry based on this article's category, product family, and tags.

  • Apple Services

    Apple Services Performance PartnersApple Services Performance Partners

    Apple services partner program for approved promotional placements and campaigns.

    Applied
  • Malwarebytes

    Malwarebytes AffiliatePartnerize

    Endpoint protection and remediation tools for malware and threat cleanup workflows.

    Applied
  • Amazon IT Gear Picks

    Amazon AssociatesAmazon Associates

    Recommended keyboards, docks, adapters, and accessories for enterprise support and productivity setups.

    Active

Disclosure: Active partner links may generate commission with no additional user cost.

Was this helpful?

Your response is stored locally in this browser for demo analytics.

Continue With Related Resources

Move from the troubleshooting article into related downloads, broader fix libraries, and pillar guides without restarting your search.