You can see - what is happening at an elementary level by running the policy update command manually…
On a Client Type in Terminal:
sudo /usr/sbin/jamf policy
It will then - immediately - look for and execute any policies
And you can see in terminal – which one it's applying – and any issues with them
The advantages of this method -- for Testing --
is that:
-- the effect takes place immediatly - no waiting
-- and you can see exactly what policies are being applied --
-- and what their results are -- from the client end --
Hi again
I forgot to say -- That command will generally look for the "any" policy
Although since no policy trigger is specified there, it may look for others too… ?
i think you misunderstood tom's question. he was (in 2008) looking for documentation on what commands are run when the jamf binary is used to perform certain tasks.
for reference, you can do a number of things to gain insight here.
run `strings` on the jamf binary itself to see a bunch of commands embedded in plain text.
use `dtruss` (uses dtrace) to watch spawned processes as you run the jamf binary. you could do something like `sudo dtruss jamf manage -verbose` to start.
likewise, using `dtrace` to follow what /usr/sbin/jamf does when running will be informative. in addition to the man page, here's a good reference: http://www.dtracebook.com
Not cool. So I'm interested in checking out this strings command, right? It started with an innocent search on google for "man strings".
Awful - just awful.
