Verbose: Parsing Policy Reboot Notification (4371). Verbose: Removing any cached policies for this trigger. Verbose: The Management Framework Settings are up to date. Verbose: Active ethernet connection found. Verbose: Checking for active ethernet connection. Verbose: Checking for an existing instance of this application.Ĭhecking for policies triggered by "recurring check-in". (I'd pay no attention to the obvious bug in Casper Remote, in checking for a binary that is no longer there).īut it's almost more like the script isn't being copied to tmp when I look at a verbose output from a policy update: ThisMac:JAMF yellow$ sudo jamf policy -verbose I'm seeing this more and more and it's becoming a problem. Īnd I do have a tmp folder in my JAMF Application Support folder. Run as a trigger: ThisMac:Source yellow$ sudo jamf policy -trigger "runRebootNotification"Ĭhecking for policies triggered by "runRebootNotification".Įxecuting Policy Reboot Notification.
Running it from command line as a -trigger worked ONCE. Verifying /Library/Preferences/.Įxecuting Policy at 1:18 PM | yellow | 1 Computer. usr/local/jamf/bin/jamf is current (9.81) Running it via Casper Remote gives me: Sending Wake On LAN command.
Script result: /bin/sh: /Library/Application Support/JAMF/tmp/RebootNotification_v1.0.sh: No such file or directory Running script RebootNotification_v1.0.sh. Note, the script continues no reference to the jamf binary.
How is a sh file recognized by os x for launching upgrade#
This is a script that worked fine prior to 9.8 upgrade (we are running 9.8.1). a perfectly good script, meaning it will run locally from the command line, will not run as a policy. This has been happening off and on and I'm not entirely sure why.
0 kommentar(er)
