![]() ![]() I'm going to try and also craft a report that will output group names and list what policies are using them. This will finally let me delete packages with confidence that nothing is using it. ::Light from above and angels singing "ahhhhhhhhh":: I can't believe I didn't do this earlier. This will quickly and easily tell you what policies are using it. You can take the same data and filter down on package name. You can customize which fields you want in the report by plunking down the right ones between "select" and "from." You'll just need to do a select * on the tables involved here (policies and packages – policy_packages just links the two together) to see which ones you want. You can then easily export this info to CSV and open it with Excel where if you sort by policy id and then priority, you have a wonderful audit of a good chunk of your JSS and you can make informed decisions about what policies are safe to delete by using filters in Excel. ![]() Join packages on policy_packages.package_id = packages.package_idīasically, the sql query joins 3 tables together and then displays the policy id, policy name, package names included in the policy, their priorities and the filename of the package. Join policy_packages on policies.policy_id = policy_packages.policy_id Select policies.policy_id, policies.name, package_name, priority, file_name from `jamfsoftware. The query is attached and you can use something like MySQL Workbench to connect to the database and execute it. If you've opened up your JSS to read only database access () it's a fairly simple SQL query. I just saved a whole boat load of copy/paste. For each package, what policies are set to distribute it, what configurations use it, and when was the last time it was distributed. Then, "audit on package" would be most useful. It would list the policy, when it was last used, what packages it uses and what groups it's scoped to. A graphical representation would be fantastic and likely most easily used but a regular report would be fantastic to. It would be a WONDERFUL feature if your JSS could be audited and the report could give you an idea of what packages are linked to what policies, what groups are linked to what policies, what policies have not been used lately etc. ![]() We're going through an audit right now of our entire JSS to weed out old policies, packages, configurations, scripts etc. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |