Deploy packages using Munki

Create a package on the Admin Console. Sign in to the Adobe Admin Console, go to the Packages tab, and select Create package.

Import the package into the Munki repo. In the terminal, run the following command:

munkiimport <path of downloaded package>

Add an appropriate response when you are prompted for information about the package:

Use existing item as a template? [y/N]

• Select Y if you have previously imported an Admin Console package and want to use the existing template and press Return.
• If this is the first package you're importing or if you're using a new template:
  • Enter N and press Return.
  • Press Return to use the default item name.
  • Enter a Display name and Description.
  • Press Return to use the version and the catalogs.
  • Enter the category and developer and press Return.

To edit the newly created pkginfo file:

• Press Y to review or edit the file.
• Press N to proceed without making changes to the file.

Create client manifest. Rebuild catalogs to complete import functionality.
The package has been successfully moved to Munki. Create a client manifest so that Munki knows what to install on a given machine.

Use the manifestutil tool to create a manifest and add the package to it.

Run the following commands:

• manifestutil --new-manifest site_default
• manifestutil --add-catalog <Catalog name> --manifest site_default
• manifestutil --add-pkg <Package name> --manifest site_default

Run the install package on the client machine. If you have specified unattended_install as:

• True: The package gets installed automatically when the Munki agent runs next on the client machine.
• False: To initiate a manual install, execute the following command on the client machine:
  sudo /usr/local/munki/managedsoftwareupdate --installonly

Alternatively, launch managed software center tools and trigger the installation.

Download the package from the Admin Console. Sign in to the Adobe Admin Console and select the Packages tab.

Locate and download the same package version originally used for installation on the users’ machines. Use the _Uninstall.pkg file for the uninstall process.

Import the package into the Munki repo. Run munkiimport <path of downloaded package> in the terminal.
Specify the uninstall file path.

Add an appropriate response when you are prompted with the message:
Use existing item as a template? [y/N]

• If you have previously imported an Admin Console package, and you want to use the existing template, enter Y and press Return.
• If this is the first package you're importing or if you're using a new template:
  • Enter N and press Return.
  • Press Return to use the default item name.
  • Enter a Display name and Description.
  • Press Return to use the version and the catalogs.
  • Enter the category and developer and press Return.

Create client manifest. Rebuild catalogs to complete the package import into the Munki repository. Next, you need to create a client manifest so that Munki knows what to install on a given machine.

Use the manifestutil tool to create a manifest and add the package to it.

Run the following commands to create a new manifest:

• manifestutil --new-manifest site_default
• manifestutil --add-catalog testing --manifest site_default
• manifestutil --add-pkg <PackageName> --manifest site_default

The package is ready to be uninstalled.

Run the Uninstall package on the client machine. If you have specified the unattended_install value as:

• True: The package gets uninstalled automatically when the Munki agent runs next on the client machine.
• False: To initiate a manual install, execute the following command on the client machine:
  sudo /usr/local/munki/managedsoftwareupdate --installonly

Alternatively, launch managed software center tools and trigger the installation.