haircut / better-jamf-policy-deferral Goto Github PK

Hi, Justt ried the better-jamf-policy-deferral script you have made and it works fine - also on mojave. However, when I set the deferrel to 5 minutes and shut down the mac. And then restart 10 minutes later, it does not startup the update ?. Is that how it has to be or ?

Is it in any way possible to set dynamic deferral limits in the script, maybe at "GUI_DEFER_OPTIONS"?
At our company we'd like to enforce certain policies at the end of the month, the JSS built-in version gives you the option to set a date as the deferral limit in Policies -> User Interaction in JAMF.

Describe the bug

Script result: Traceback (most recent call last):
  File "/Library/Application Support/JAMF/tmp/Defer Software Updates", line 29, in <module>
    from AppKit import NSWorkspace
ModuleNotFoundError: No module named 'AppKit'

Python 3

Note: Issues opened without specifying one of the following options will be ignored.

• I am using the macadmins Python distribution that I installed on the affected Mac.
• I am using a Python 3 runtime I installed myself, and I updated the script's shebang to point to the that python3 binary.

To Reproduce
Steps to reproduce the behavior:
I run the prompt policy that calls the script. Get the following error:

Script result: Traceback (most recent call last):
  File "/Library/Application Support/JAMF/tmp/Defer Software Updates", line 29, in <module>
    from AppKit import NSWorkspace
ModuleNotFoundError: No module named 'AppKit'

What am I missing? running macOS 12.3.1

Hey there - looking at implementing this. What's the behavior when a blocking app is closed? I've found a good way to differentiate between "I have Zoom running" and "I'm actually in a zoom meeting", and I'd like to be able to use the Blocking App function to wait for someone to be out of a meeting.

First time trying BJPD. It mostly worked, installed the updates after a 30 min deferral as expected, but then error'ed out during the cleanup, which left the LD in tact which causes future policy prompts to fail.

Anything standout with the following traceback?

Script result: Traceback (most recent call last): File "/Library/Application Support/JAMF/tmp/better-jamf-policy-deferral.py", line 29, in from AppKit import NSWorkspace File "/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC/AppKit/__init__.py", line 12, in from AppKit._inlines import _inline_list_ ImportError: dlopen(/System/Library/Frameworks/Python.framework/Versions/2.7/Extras/lib/python/PyObjC/AppKit/_inlines.so, 2): Symbol not found: __dyld_process_info_notify_main Referenced from: /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication Expected in: /usr/lib/libSystem.B.dylib in /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication

Describe the bug
Choosing the 'Start Now' option results in an error message.

Python 3

Note: Issues opened without specifying one of the following options will be ignored.

• I am using the macadmins Python distribution that I installed on the affected Mac.
• I am using a Python 3 runtime I installed myself, and I updated the script's shebang to point to the that python3 binary.

To Reproduce
Steps to reproduce the behavior:

1. Run the 'Prompt' policy
2. Select Start Now, click ok
3. Get error baked into the script 'A problem occurred processing your request. Please contact your administrator for assistance'

Expected behavior
To run the 'Execution' policy

Error output
'A problem occurred processing your request. Please contact your administrator for assistance'

Just to add, if the execution policy is deferred, it runs fine at the specified deferred time.

From the readme, only the Prompt policy is scoped. However, I was unable to execute the Execution Policy unless I scoped that policy as well. Is that expected?