[Casper] Update /usr/sbin/jamf version: 5.11 to 6.01

[Ernst, Craig S.]

Hi Ben,

Have you checked /var/logs/jamf.log to see if there is anything there about the policy you are running? I know that you said it was successful, but if you hadn't looked there I still would.

If you are on a machine that reports 5.11 in the JSS and you get to a terminal window on one of those machines and do a: /usr/sbin/jamf version

Does it agree with the JSS version still being at 5.11?

And finally I'd do a manual upgrade on one of these machines as well if the version is out of date to see if you can see something go wrong there. Again terminal at the machine: sudo /usr/sbin/jamf upgrade

See what happens. I know that I still have machines that have a BLANK for the /usr/sbin/jamf version in the JSS...=) Just haven't gotten around to that little issue either.

Craig E


On 9/16/08 8:14 PM, "Ben Greiner" <forgetcomputers at mac.com> wrote:

I've created a policy to update the Command Line Applications...

        This policy is set to Once Per Computer
        This policy is triggered by everyHour
        This policy is assigned to Workstations - 10.5 Leo
        This policy is assigned to EXAMPLE
        Update Command Line Applications
        Run Recon

But it doesn't seem to work as expected. Most clients after
successfully running this policy continue to report 5.11.
How can I force my clients to update to 6.01 of the jamf binary?

Thanks,

Ben Greiner
Forget Computers
312 602.5345
ben at forgetcomputers.com

_______________________________________________
Casper mailing list
Casper at list.jamfsoftware.com
http://list.jamfsoftware.com/mailman/listinfo/casper

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.jamfsoftware.com/pipermail/casper/attachments/20080916/80bab23a/attachment.html