Skip to main content
Question

Custom trigger/could not connect to the JSS errors

  • August 17, 2017
  • 1 reply
  • 1 view

Forum|alt.badge.img+12
  • Contributor
  • 288 replies

As of this morning, there were 3 machines that are failing to connect to the jss and running a custom trigger. The last successful that was ran by a user was at 7:30 PM last night.

<br/>Checking for policies triggered by "OfficeUpdate"...<br/>Could not connect to the JSS. Looking for cached policies

On my own machine, I tried sudo jamf policy - trigger OfficeUpdate and it works as expected. Any idea why some machines would work, and others wouldn't?

1 reply

stephanpeterson
Forum|alt.badge.img+11

@bbot Did you ever get anywhere with this? I'm seeing a similar issue, but a different context.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings