Why is it that when you create a policy that is set to be triggered on startup, that the policy is very rarely actually triggered? I have noticed this on several policies I have created so far. Usually the way it goes is that I creat the startup-triggered policy, make sure my test computer is in scope, and then go reboot the test computer. When I check the policy logs in the jamf pro portal I see that the test computer just says 'pending'. This will continue to be the case no matter how many times I reboot the computer. Then, in order to actually get the policy to run I need to issue the command: 'sudo jamf policy -id 7'.
Is there some other step I am missing?
