Skip to main content
Question

Make App Only Available In Self Service

  • November 5, 2015
  • 1 reply
  • 5 views
B
Forum|alt.badge.img+5

Hi all,

Wanting to make an app only available in self service, and not to be pushed to the machines. So is my thinking correct here -

Under General - If I leave all triggers blank and then set the scope to all suers and all computers this will NOT push the app? Then when I go to history they should all be say on Pending until the policy has been run from SS? It will defiantly not send to all as there is no trigger to send it?

Just craped myself when I set the scope and it went to all computers to pending, so i turned it off. Then thought that's right? I just don't want to push out a huge app over the wireless. So if this will defiantly work then I will go for it!

Thanks
Simon

    1 reply

    A
    Forum|alt.badge.img+13
    • andrew_nicholas
    • Honored Contributor
    • November 5, 2015

    That is correct. If you do not set a trigger the policy will not be run on the machine without action on the client (either trigger via SS or manually call the policy ID within terminal). If this is the route you're going you may want to invest a little time in correctly creating two smart groups: machines to see the policy and machines that ran the policy. Leaving everything as run once does not account for environmental failures or unforeseen issues. It is typically very helpful to set the Execution Frequency to ongoing and then set the scope to the target group of machines to get the policy, and the exclusion to the smart group for machines that ran the policy. You'll want to include an inventory update or a script that calls recon to ensure the second group is updated correctly.

    I have to say I also advise not scoping things to All Machines as a general rule. Better to have a smart group for the correct target as All Machines doesn't differentiate between Clients/Servers/VIPs/Squeaky Wheels/etc..

    Terms & ConditionsCookie settingsAccessibility statement