This issue is very strange, and since I am uploading packages through Jamf Sync, it seems related to Jamf Sync.
I have a new package I uploaded through Jamf Sync, and the package is on my policy with a custom trigger:
But on some computers, running the custom trigger does not install anything:
Running the command through terminal says it's running the policy, and then submits the log to Jamf and doesn't reach out to our distribution point, or the JCDP, which I have as a fallback.
Last week when this happened, I opened Jamf Admin and the package worked fine after that. Now that we are on Jamf 11.6.1, Jamf Admin does not connect anymore.
This seems more like some kind of database issue, but wanted to bring it to your attention. The Jamf case number is CS1186671, which I have some logs uploaded that support requested.
Please let me know if you need anything else from me.
Hello,
This issue is very strange, and since I am uploading packages through Jamf Sync, it seems related to Jamf Sync.
I have a new package I uploaded through Jamf Sync, and the package is on my policy with a custom trigger:
But on some computers, running the custom trigger does not install anything:
Running the command through terminal says it's running the policy, and then submits the log to Jamf and doesn't reach out to our distribution point, or the JCDP, which I have as a fallback.
Last week when this happened, I opened Jamf Admin and the package worked fine after that. Now that we are on Jamf 11.6.1, Jamf Admin does not connect anymore.
This seems more like some kind of database issue, but wanted to bring it to your attention. The Jamf case number is CS1186671, which I have some logs uploaded that support requested.
Please let me know if you need anything else from me.
Thanks.