Package and Policy Naming Conventions and Global Availability

Table of Contents

When uploading packages and policies to Jamf, use the following naming convention:
[SITE | 'GLOBAL'] - [CATEGORY] - [DESCRIPTION]

Where

SITE is your site name or GLOBAL

CATEGORY - the category and/or subcategory of the package/policy/script

Jamf Documentation: https://docs.jamf.com/10.35.0/jamf-pro/documentation/Categories.html

DESCRIPTION - a short description of the function, or name of the package

EXAMPLES:

CNS - AstroLab - Anaconda3-2020.11-MacOSX-x86_64.pkg
CNS - AstroLab - Anaconda3-5.2.0.pkg
CNS - PhyLab - Capstone.pkg
GLOBAL - Software - Firefox.pkg
GLOBAL - Software - GoogleChrome.pkg
LAITS - Labs - ZoomInstallerIT.pkg
LAITS - Self Service - Teams_osx.pkg

To add a package to Jamf Admin, the file must be in one of the following formats:

Disk Image (.dmg)
Installer Package (.pkg)
Metapackage (.mpkg)
Compressed archive (.zip)
Application (.app)

Globally available policies and packages

AUP Policies - GLOBAL - UTexas Acceptable Use Policy Banner
Screensaver Profiles - GLOBAL-Default LoginWindow & Screen Saver Settings.
Nessus - GLOBAL - Nessus agent install/link
Code42 -
- script: GLOBAL-code42-install-mac
- template policies (must be cloned to your site and enabled):
  - TEMPLATE - install code42 - machine account
  - TEMPLATE - install code42 - user account
Defender (TBD)

Section Content