Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Policy scope and limitations #32

Open
neilv54 opened this issue Sep 15, 2024 · 1 comment
Open

Policy scope and limitations #32

neilv54 opened this issue Sep 15, 2024 · 1 comment

Comments

@neilv54
Copy link

neilv54 commented Sep 15, 2024

You define a trigger in the configuration profile, the trigger is scoped to a smart group or to a security group in the limitation and the computer is not part of that scoping.
The icon app will show as successful, even though nothing was delivered.
Is there a way to define scoping?

@scriptingosx
Copy link
Collaborator

No, scoping is defined in Jamf Pro and Setup Manager cannot influence this. All Setup Manager can report is that the command that triggered the custom policy ran successfully. There is no way to judge on-device whether the device should have been in scope or not.

There seems to be an issue with 11.9 (and possibly earlier versions) where a computer drops out of scope of smart groups while they are recalculating (i.e. right after a recon) which seems to affect some Setup Manager workflows. I have no way to determine whether this is affecting you, but I would recommend testing with 11.9.1?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants