2 Scoping questions

I would recommend creating a smart group with conditions of "Total RAM more than .9 GB"; scope your policy off that.

Scoping to HFS+ volumes would probably best be handled by creating a custom script-fed extension attribute scoped smart group. (Phew, what a mouthful.) Something like diskutil list | grep "HFS" It's not going to be bullet-proof, but it's a start.

Hope this gets the gears turnin'!

Let me know if you get stuck & Happy Friday,
Kerry

None of this works properly. When you try and use GB in the criteria. Try more than anything like, say 4 GB and you wont see anything with 10 GB or more!

You want to use numbers in the MB range, but it is the actual size, so to scope 8GB or more, scope

more than: 8191

to scope 4GB,

is: 4096

so you should be looking for more than: 1023

Sean

Don,
if you want to include 1GB, then drop back a bit on the number. Instead of list 1 GB as 1024 put in a value of 1000.
This would include the 1GB systems as well as anything above that value.

-Lance

--
Lance Ogletree
JAMF Software
Systems Engineer
Mobile: (972) 342-5990
Direct: (972) 547-9566
lance.ogletree at jamfsoftware.com<mailto:lance.ogletree at jamfsoftware.com>

Sorry, I should have been more verbose, Yes, casper wants memory quantities in mebibytes, or "old" megabytes.... or "megabytes", depending on the context. What a mess! :) Gigabytes, or tenths of gigabytes, will not produce desired results.

Here is a screenshot:

Or, do as Lance has suggested and make it 1000. :)

Good Luck,
Kerry


Ah,

Forgot to mention your part 2.

You can look for format in system_profiler and put that to an Extended Attribute and then smart group them.

Have a look at this:

system_profiler SPSerialATADataType | sed -n '/Volumes/,/Intel/p' | egrep "^ {12}[A-Z,a-z]|File System"

and adapt appropriately.

Sean