On your computer, go to the Applications folder and then go to the Utilities folder.
Check if a package is deployed
- Adobe Enterprise & Teams: Administration guide
- Plan your deployment
- Basic concepts
- Deployment Guides
- Deploy Creative Cloud for education
- Set up your organization
- Identity types | Overview
- Set up identity | Overview
- Set up organization with Enterprise ID
- Setup Azure AD federation and sync
- Set up Google Federation and sync
- Set up organization with Microsoft ADFS
- Set up organization for District Portals and LMS
- Set up organization with other Identity providers
- SSO common questions and troubleshooting
- Manage your organization setup
- Manage products and entitlements
- Manage users
- Administrative roles
- User management techniques
- Change user's identity type
- Manage user groups
- Manage directory users
- Manage developers
- Migrate existing users to the Adobe Admin Console
- Migrate user management to the Adobe Admin Console
- Manage products and product profiles
- Manage products
- Manage product profiles for enterprise users
- Manage automatic assignment rules
- Review product requests
- Manage self-service policies
- Manage app integrations
- Manage product permissions in the Admin Console
- Enable/disable services for a product profile
- Single App | Creative Cloud for enterprise
- Optional services
- Manage Shared Device licenses
- Manage users
- Manage storage and assets
- Asset migration
- Reclaim assets from a user
- Student asset migration | EDU only
- Manage services
- Adobe Stock
- Custom fonts
- Adobe Asset Link
- Adobe Acrobat Sign
- Creative Cloud for enterprise - free membership
- Deploy apps and updates
- Create packages
- Customize packages
- Deploy Packages
- Manage updates
- Adobe Update Server Setup Tool (AUSST)
- Adobe Remote Update Manager (RUM)
- Create packages using Creative Cloud Packager (CC 2018 or earlier apps)
- About Creative Cloud Packager
- Creative Cloud Packager release notes
- Application packaging
- Create packages using Creative Cloud Packager
- Create named license packages
- Create packages with device licenses
- Create a license package
- Create packages with serial number licenses
- Packager automation
- Package non-Creative Cloud products
- Edit and save configurations
- Set locale at system level
- Manage your account
- Manage your Teams account
- Assign licenses to a Teams user
- Add products and licenses
- Automated expiration stages for ETLA contracts
- Switching contract types within an existing Adobe Admin Console
- Purchase Request compliance
- Value Incentive Plan (VIP) in China
- VIP Select help
- Reports & logs
- Get help
A package ID uniquely identifies a package.
This document details to steps to check if a given package (using the package ID) is deployed on specific client machines.
To determine which versions of Adobe applications are installed on a computer, see this document.
Get package ID
Before checking client machines for a deployed package (using the package ID), you must obtain the package ID.
Package IDs are available for packages created (or updated) in Creative Cloud Packager 1.8 and later versions.
The procedures detailed in this document do not apply to packages created in version 1.7 or earlier.
You can get the package ID from the package details panel in the Admin Console. In the Admin Console, go to the Packages tab and click any package to open the package details panel.
Query client machines
Open the terminal.
Run the following command to query for the installed packages:
pkgutil --packages --volume / | grep <PackageID>
To open the Windows Registry Editor, press the Start button on your keyboard, type regedit and press Enter.
If you are prompted with a User Access Control dialog, click Yes.
In the Registry Editor, click Edit > Find.
In the Find dialog, enter the package ID and click Find Next.
If the package ID exists on the client machine, it is returned under the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
Using Microsoft SCCM
If you are using Microsoft SCCM, you can also remotely query the clients for the package IDs in two ways:
- By extending the hardware inventory schema to gather registry key values
- By using Desired Configuration Manager (DCM) to map the number of clients with this registry key and package ID
We recommend that you use the MSI to uninstall a package and not use the product code present in the registry entry.