Jamf-Client-Communications-Doctor

KO | EN

gitlite — search

#javascript #hacktoberfest #react #deep-learning #nodejs #windows #cli #kubernetes #vue #pytorch #mcp #ios #openai #open-source

Jamf-Client-Communications-Doctor

(★ 29)

Daemon that sets a TTL on Jamf Policies and EAs to ensure clients communicate with Jamf

Jamf-Client-Communications-Doctor Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Jamf Client Communications Doctor

Jamf Pro doesn’t have guard rails in place for when it runs policies or inventory updates to ensure communications remain stable. Of primary concern is the jamf process doesn’t place time limits on how long a policy or extension attribute is allowed to run. In addition to this all tasks are run sequentially. If a single process hangs this will cause all other pending tasks to wait indefinitely for it to complete, which may never happen. In the Jamf Pro Server console this may reflect computers not properly having inventory updated or will only run some policies on an infrequent basis.  Additionally, Jamf may still list the computer as “checking in,” however there may usually be little to no policy logs.

Some common examples of objects that will cause a hang:
* A script that waits for user input.
* A script that implements JamfHelper or osascript without the timeout flag.
* A script that runs a child process which subsequently hangs.
* An installer package waits for input or external data.
* The computer goes to sleep during the check-in process.

The Jamf Client Communications Doctor aims to fix this by doing the following:

* Sets a TTL on Policy child processes (default of 14.1 hours per child)
* Sets a TTL on Extension Attribute processes (default of 60 minutes per EA)
* Sets a TTL on Jamf check-ins to 2 days
* Prevents  the computer from system sleeping for the duration of the check-in process
** Display sleep and screen lock are allowed!

# How to Install
Add the script to your Jamf instance and scope to computers in a policy.  The Doctor will self install/update locally on the computer as needed.

# How to Uninstall
sudo launchctl bootout system "/Library/LaunchDaemons/com.mann.JamfClientCommunicationsDoctor.plist"

sudo rm "/Library/LaunchDaemons/com.mann.JamfClientCommunicationsDoctor.plist"

sudo rm "/Library/Application Support/Mann/Scripts/Jamf Client Communications Doctor.sh"

# Documentation
Documentation available at https://docs.google.com/document/d/1p0OT3AFrYdS-H6Nio1caa81C-Vug5ZKcRLgKTzUv6zU

Jamf-Client-Communications-Doctor

Jamf-Client-Communications-Doctor Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Jamf-Client-Communications-Doctor

Jamf-Client-Communications-Doctor Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README