Open System Preferences on each target system.
-
Setup and onboarding
- Explore Adobe Admin Console
- Sign-in and access
-
Licensing
- Licensing overview
- Licensing types
-
Identity and SSO
- Set up identity
- Integrate with Microsoft Entra
- Integrate with Google Sync
- Integrate with other SSO providers
- Troubleshoot
-
Directories, domains, and access
-
Directories and domains
- Create a directory for SAML identity providers
- Verify domain ownership
- Set up domains for directory authentication
- Move domains across directories
- Encrypted and trusted directory domain transfers
- Move directories between Admin Consoles
- Delete directories and domains
- Automatic account creation overview
- Enable automatic account creation
- Automatic federated account creation FAQ
- Domain enforcement
- Directory trusting
-
Directories and domains
-
Settings
- Asset settings
- Manage encryption
-
User management
- Understand user management
- Manage users and groups
- Manage admins
- Manage user roles
- Migrate users
-
Products and entitlements
- Manage products
- Manage product profiles
- Special programs plans
- Manage entitlements
- Manage automatic assignment
- Manage product access
- Manage self-service policies
- Manage app integrations
- Frame.io integration
- Manage product permissions
- Manage storage and assets
-
Manage services
- Configure services
- Adobe Stock
- Custom fonts
- Adobe Asset Link
-
Deploy apps and updates
- Prepare for deployment
- Manage pre-generated packages
- Create packages
- Customize end-user experience
- Deploy packages
- Use third-party deployment tools
-
Manage Shared Device Licensing (SDL)
- Shared Device Licensing overview
- Deploy Shared Device Licensing
- Manage SDL profiles and user access
- Activate shared device licenses
- Use the Shared Device Licensing toolkit
- Recover shared device licenses
- Shared Device Licensing identity FAQ
- Shared Device Licensing deployment FAQ
- Shared Device Licensing access FAQ
- Known issues in Shared Device Licensing
- Adobe Update Server Setup Tool (AUSST)
- Adobe Remote Update Manager (RUM)
- Troubleshoot
- Contracts and renewals
- Reports and logs
-
Get started with Global Admin Console
- Get started
- Manage your organization
- Reports audit
-
Get help
- Support options
-
General troubleshooting
- Microsoft Purview Information Protection support in Acrobat
- Use the Creative Cloud Cleaner tool to fix installation issues
- Fix app launch errors on Shared Device Licensing machines
- Technical support boundaries for virtualized or server-based environments
- Resolve trial and license expired errors
- Migrating to OAuth Server-to-Server Credentials
- Manage device authentication for Creative Cloud and Acrobat Pro
ARD package deployment fails
Resolve common Apple Remote Desktop deployment failures on macOS.
Apple Remote Desktop (ARD) package deployment can fail due to improper system preparation, incorrect configuration, or user state changes during installation. Understanding the requirements and deployment methods helps ensure successful Adobe package deployment.
If you selected Specify directory during deployment when creating the package, ensure you specify the custom installation location before deploying.
Remote Management isn't properly configured
Remote Management isn't properly configured on target systems, preventing ARD from communicating with client machines.
Select Sharing from the preferences pane.
Select Remote Management in the left pane.
Verify that Copy Items and Delete and Replace Items are selected in the Remote Management permissions.
Verify that the target machines appear in the ARD window.
User state changes during deployment
When the user state changes during deployment, such as user login, logout, or user switching, the installation process is interrupted.
Verify all target machines are in a quiet state with no active users.
Ensure machines remain active to receive commands, but users are logged out.
Redeploy the package if the initial deployment fails.
If deploying using Copy Items and the Send UNIX Command method, specify only the folder name in the plist, and you'll pass the volume name with the installer command.