![]() ![]() Once you have all the EAs you want, you can create a single smart group (or inventory report, your choice) with the criteria of Extension Attribute 'a' IS NOT OR Extension Attribute 'b' IS NOT, etc. ![]() Rinse and repeat for each baseline item you want to check. You would make that into an EA, populated by script. Say one is java version has to be 1.7.0_11 for the Mac to be considered compliant (yes, I know 1.7.0_11 is super ancient, gimme a break it's just an example ) ). You might want to think about creating an EA for each area of the baseline you want to compare a mac to. I think EAs would be the way to go here, because then you could at least output the result of each EA in the single report that a Mac would fall into if "it wasn't compliant." Otherwise I don't think a singular report would help very much without a HUGE amount of coding, but then we're back to the EA portion of it. What sort of information would you be looking to get? Just that the computer isn't compliant against the baseline? That it's missing X, Y, and Z? Maybe a starting point Im not the best coder but hopefully this may turn a light bulb on to someone who can script :D Its just a really dirty way to do things. The whole idea behind this is looking for specific software against an answer file. ![]() It won't do anything even if I do it recursively. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |