10.7 Clients not writing Policy Logs

[Sandy]

HI All,
I am seeing an issue where my small smattering of 10.7 clients are not finishing policies to the point of writing policy logs to the JSS. Consequently they are running some one time startup policies at EVERY startup, and one time policies that have run already are showing up in Self Service.

Other policies specifically scoped to 10.7 do not appear to run at all.

I have some 10.7's that were manually updated from 10.6, some that were out of the box (never imaged) and added with quick-add, and now some imaged. This is impacting all, so far as I can tell.
Also updated to JSS 8.5.2 along the way...
Unfortunately I was pretty well distracted by ipads so not sure when this started.

I am just starting to troubleshoot, but thought I'd see if anyone else had already run into anything similar.
Thanks!
Sandy

[mm2270]

If you run your policy on one of the affected Macs via Terminal like:

sudo jamf policy -id <ID>

do you notice a line at the end stating something like: "Log was not written in the JSS. Will store locally."?

I ask because I have begun to see this myself recently. I'm running into it now, but in my case I do know it has something to do with a script I'm running in the policy. Apparently the JSS does not like some of the output being pumped to stdout and can't submit the log correctly. Over time, the /Library/Application Support/JAMF/logs/ folder starts to get filled up with logs waiting to get submitted, but it can't, and they have to be cleared out.
As you've already noticed, with policies that have this issue, as far as the JSS is concerned the Macs haven't run it and will attempt to run it again next time its time since they stay in the queue.

I wish I had a definitive answer to this one. Best advice I can offer is to try troubleshooting your policy to see what may be causing the logs to fail the submission part.

Also, are any of these Macs running 10.7.4 by any chance? I've actually only started to see this since I upgraded some systems to 10.7.4 but I don't know if its directly related or just coincidence. Its a new policy, not one I've been running for a while so I can't be sure if the client's OS version is related.