What triggers a Restricted Software record on a client system?

New Contributor III

When a Restricted Software record is created or updated, what triggers the newly created or updated record to be available on a targeted system. Specifically, on the client system does; jamf policy, or jamf manage, or jamf recon, or any other jamf command have to be run? Or does the client system get the record at the time of the recurring checkin?
JSS 9.65, Mac OS x 10.6 - 10.11 clients.
Thank you,
John McNair


Legendary Contributor III

I haven't tested it now in some time, but when I did, I believe it was the jamf manage command that pulled down the new Restricted Software settings. In other words, it was applying the management framework that got the new settings. It may have changed since I looked at that though.

Valued Contributor

I was playing around with this last week, it's sudo jamf manage.

Esteemed Contributor III

+1 to @Abdiaziz

$ jamf help manage

Usage:   jamf manage 

Notes:   This verb enforces the entire management framework from the JSS, 
     including scheduled tasks, the restricted applications, and the Global Management settings, such as the startup 
     script and login/logout hooks.

Contributor II

+1 to @Abdiaziz We use sudo jamf manage a good amount (students find the oddest games)