Extension attributes are custom fields that allow you to collect almost any piece of attribute data from a computer.
Find out more about extension attributes on the extension attributes page.
Displays Name, Version and ID of installed Google Chrome Extensions for current or last user. By default, data is displayed as: Name: Extension Name Version: Extension Version ID: Extension ID. However, if further data analysis is needed, an alternate output is available: Name;Version;ID The default output looks much prettier in the JSS, but the alternative output may be more useful. To use the alternate output, simply comment out line: echo -e "Name: $reportedName \nVersion: $version \nID: $extID \n" And uncomment line: echo -e "$reportedName;$version;$extID"
Chrome_Extensions_(1).xml (3.25 KB)
This will determine the HomePage set in the Last User's preference file.
Browser_Chrome_HomePage.xml (1.47 KB)
Package manifests allow Composer to build packages from software that is already installed without taking snapshots.
Find out more about package manifests on the package manifests page.
Licensed software records in Jamf Pro let you store information about the software licensed to your organization.
Find out more about licensed software templates on the licensed software templates page.
Scripts can be executed on managed computers using a Policy or Jamf Remote. Most scripts also work with other management tools.
Find out more about scripts on the scripts page.
Managed Preference (MCX) manifests allow you to enforce settings on managed computers with Jamf Pro. These files also work with Workgroup Manager.
Find out more about managed preference manifests on the managed preference manifests page.