Skip to main content

I'm sure i know the answer already, but I'll run this by everyone.

I want to provide Application 'foo-1.2.3' to Group A and Group B

Group A require via Self Service
Group B require by startup

I've been trying to work out something 'clever' that would mean you could do this under one policy, but I don't think its possible.

Reason its there isn't just one 'foo-1.2.3' application, there are lots, so i'd rather not have to update 2 x the policies when foo is updated to 'foo-1.2.4'

I had thought about 3 policies, one for self service, once for the group then tied to the app policy.. more paint to start, but then only have to update the app policies..

Thoughts?

Thanks,

Jon

Hi.
As you already guessed, while its possible to set up a single policy to have multiple triggers, like both Startup and enabled for Self Service, its not possible to do what you're looking for to my knowledge. Once a policy is enabled for Self Service, any Macs in scope will see it inside the Self Service application. You can exclude systems from seeing it by way of Smart Groups or LDAP groups, but that would mean the other trigger(s) also would not apply to any Macs in the exclusion list. So the Startup trigger also would not get applied to them.

I think you'll just need to manage different policies and update them as needed unfortunately.