<HTML>
<HEAD>
<TITLE>Re: [Casper] Smart Computer Group that does not have JAMF ver 6.01</TITLE>
</HEAD>
<BODY>
<FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>If your goal is to get all systems up to current release just create a policy for all systems to run at ANY or perhaps your 30 minute interval that use the ‘Update Command Line Applications’ option on the general tab of a policy. It will update anything that is checking in properly and ignore those that don’t need it.<BR>
<BR>
We’ve actually had a policy in our system forever called Update_JAMF_Binary that I just flush each time a new version comes out and clients just update themselves...if I’m confident the binary won’t break anything. =)<BR>
<BR>
Craig<BR>
<BR>
<BR>
On 9/2/08 12:31 PM, "Jason Halvorson" <<a href="Halvorson.Jason@mayo.edu">Halvorson.Jason@mayo.edu</a>> wrote:<BR>
<BR>
</SPAN></FONT><BLOCKQUOTE><FONT FACE="Calibri, Verdana, Helvetica, Arial"><SPAN STYLE='font-size:11pt'>How does a person create a Smart Computer Group that determines which<BR>
computers do not have JAMF version 6.01 installed yet?<BR>
<BR>
I can't find any criteria that look for the version of JAMF installed.<BR>
<BR>
My goal is to target an update to all managed systems that are not currently<BR>
running version 6.01.<BR>
<BR>
Jason Halvorson<BR>
<BR>
<BR>
_______________________________________________<BR>
Casper mailing list<BR>
<a href="Casper@list.jamfsoftware.com">Casper@list.jamfsoftware.com</a><BR>
<a href="http://list.jamfsoftware.com/mailman/listinfo/casper">http://list.jamfsoftware.com/mailman/listinfo/casper</a><BR>
<BR>
</SPAN></FONT></BLOCKQUOTE>
</BODY>
</HTML>