User Guide Cancel

Deploy Adobe packages with SCCM

Search
Enterprise

Enterprise

Admin Console
  1. Adobe Enterprise & Teams: Administration guide
  2. Plan your deployment
    1. Basic concepts
      1. Licensing
      2. Identity
      3. User management
      4. App deployment
      5. Admin Console overview
      6. Admin roles
    2. Deployment Guides
      1. Named User deployment guide
      2. SDL deployment guide
      3. Deploy Adobe Acrobat 
    3. Deploy Creative Cloud for education
      1. Deployment home
      2. K-12 Onboarding Wizard
      3. Simple setup
      4. Syncing Users
      5. Roster Sync K-12 (US)
      6. Key licensing concepts
      7. Deployment options
      8. Quick tips
      9. Approve Adobe apps in Google Admin Console
      10. Enable Adobe Express in Google Classroom
      11. Integration with Canvas LMS
      12. Integration with Blackboard Learn
      13. Configuring SSO for District Portals and LMSs
      14. Add users through Roster Sync
      15. Kivuto FAQ
      16. Primary and Secondary institution eligibility guidelines
  3. Set up your organization
    1. Identity types | Overview
    2. Set up identity | Overview
    3. Set up organization with Enterprise ID
    4. Setup Azure AD federation and sync
      1. Set up SSO with Microsoft via Azure OIDC
      2. Add Azure Sync to your directory
      3. Role sync for Education
      4. Azure Connector FAQ
    5. Set up Google Federation and sync
      1. Set up SSO with Google Federation
      2. Add Google Sync to your directory
      3. Google federation FAQ
    6. Set up organization with Microsoft ADFS
    7. Set up organization for District Portals and LMS
    8. Set up organization with other Identity providers
      1. Create a directory
      2. Verify ownership of a domain
      3. Add domains to directories
    9. SSO common questions and troubleshooting
      1. SSO Common questions
      2. SSO Troubleshooting
      3. Education common questions
  4. Manage your organization setup
    1. Manage existing domains and directories
    2. Enable automatic account creation
    3. Set up organization via directory trust
    4. Migrate to a new authentication provider 
    5. Asset settings
    6. Authentication settings
    7. Privacy and security contacts
    8. Console settings
    9. Manage encryption  
  5. Manage users
    1. Overview
    2. Administrative roles
    3. User management strategies
      1. Manage users individually   
      2. Manage multiple users (Bulk CSV)
      3. User Sync tool (UST)
      4. Microsoft Azure Sync
      5. Google Federation Sync
    4. Assign licenses to a Teams user
    5. In-app user management for teams
      1. Manage your team in Adobe Express
      2. Manage your team in Adobe Acrobat
    6. Add users with matching email domains
    7. Change user's identity type
    8. Manage user groups
    9. Manage directory users
    10. Manage developers
    11. Migrate existing users to the Adobe Admin Console
    12. Migrate user management to the Adobe Admin Console
  6. Manage products and entitlements
    1. Manage products and product profiles
      1. Manage products
      2. Buy products and licenses
      3. Manage product profiles for enterprise users
      4. Manage automatic assignment rules
      5. Entitle users to train Firefly custom models
      6. Review product requests
      7. Manage self-service policies
      8. Manage app integrations
      9. Manage product permissions in the Admin Console  
      10. Enable/disable services for a product profile
      11. Single App | Creative Cloud for enterprise
      12. Optional services
    2. Manage Shared Device licenses
      1. What's new
      2. Deployment guide
      3. Create packages
      4. Recover licenses
      5. Manage profiles
      6. Licensing toolkit
      7. Shared Device Licensing FAQ
  7. Get started with Global Admin Console
    1. Adopt global administration
    2. Select your organization
    3. Manage organization hierarchy
    4. Manage product profiles
    5. Manage administrators
    6. Manage user groups
    7. Update organization policies
    8. Manage policy templates
    9. Allocate products to child organizations
    10. Execute pending jobs
    11. Explore insights
    12. Export or import organization structure
  8. Manage storage and assets
    1. Storage
      1. Manage enterprise storage
      2. Adobe Creative Cloud: Update to storage
      3. Manage Adobe storage
    2. Asset migration
      1. Automated Asset Migration
      2. Automated Asset Migration FAQ  
      3. Manage transferred assets
    3. Reclaim assets from a user
    4. Student asset migration | EDU only
      1. Automatic student asset migration
      2. Migrate your assets
  9. Manage services
    1. Adobe Stock
      1. Adobe Stock credit packs for teams
      2. Adobe Stock for enterprise
      3. Use Adobe Stock for enterprise
      4. Adobe Stock License Approval
    2. Custom fonts
    3. Adobe Asset Link
      1. Overview
      2. Create user group
      3. Configure Adobe Experience Manager Assets
      4. Configure and install Adobe Asset Link
      5. Manage assets
      6. Adobe Asset Link for XD
    4. Adobe Acrobat Sign
      1. Set up Adobe Acrobat Sign for enterprise or teams
      2. Adobe Acrobat Sign - Team feature Administrator
      3. Manage Adobe Acrobat Sign on the Admin Console
    5. Creative Cloud for enterprise - free membership
      1. Overview
  10. Deploy apps and updates
    1. Overview
      1. Deploy and deliver apps and updates
      2. Plan to deploy
      3. Prepare to deploy
    2. Create packages
      1. Package apps via the Admin Console
      2. Create Named User Licensing Packages
      3. Manage pre-generated packages
        1. Manage Adobe templates
        2. Manage Single-app packages
      4. Manage packages
      5. Manage device licenses
      6. Serial number licensing
    3. Customize packages
      1. Customize the Creative Cloud desktop app
      2. Include extensions in your package
    4. Deploy Packages 
      1. Deploy packages
      2. Deploy Adobe packages using Microsoft Intune
      3. Deploy Adobe packages with SCCM
      4. Deploy Adobe packages with ARD
      5. Install products in the Exceptions folder
      6. Uninstall Creative Cloud products
      7. Use Adobe provisioning toolkit enterprise edition
    5. Manage updates
      1. Change management for Adobe enterprise and teams customers
      2. Deploy updates
    6. Adobe Update Server Setup Tool (AUSST)
      1. AUSST Overview
      2. Set up the internal update server
      3. Maintain the internal update server
      4. Common use cases of AUSST   
      5. Troubleshoot the internal update server
    7. Adobe Remote Update Manager (RUM)
      1. Release notes
      2. Use Adobe Remote Update Manager
    8. Troubleshoot
      1. Troubleshoot Creative Cloud apps installation and uninstallation errors
      2. Query client machines to check if a package is deployed
  11. Manage your Teams account
    1. Overview
    2. Update payment details
    3. Manage invoices
    4. Change contract owner
    5. Change your plan
    6. Change reseller
    7. Cancel your plan
    8. Purchase Request compliance
  12. Renewals
    1. Teams membership: Renewals
    2. Enterprise in VIP: Renewals and compliance
  13. Manage contracts
    1. Automated expiration stages for ETLA contracts
    2. Switching contract types within an existing Adobe Admin Console
    3. Value Incentive Plan (VIP) in China
    4. VIP Select help
  14. Reports & logs
    1. Audit Log
    2. Assignment reports
    3. Content Logs
  15. Get help
    1. Contact Adobe Customer Care
    2. Support options for teams accounts
    3. Support options for enterprise accounts
    4. Support options for Experience Cloud
Note:

Flash Player's end of life is December 31st, 2020. Please see the Flash Player EOL Enterprise Information page for details.

This article guides you through the process of creating an SCCM package to deploy an Adobe deployment package. Because both Adobe and Microsoft use the term package and because there are currently two versions of the Microsoft software in use, we use the following naming conventions for clarity in this article:

  • When referring to a package created with SCCM, we say SCCM package unless the context is very clear, when we may say just package.
  • When referring to a package created on the Adobe Admin Console, we say Adobe deployment package or Adobe package. We never use the term package alone to mean an Adobe package.

Preparation

SCCM is designed for a great variety of network configurations. The best choice of deployment configuration for the Adobe package and its product install folder is the TS option, where the Adobe package and its product install folder are placed together on the same distribution server or servers.

When you create a package for deployment in Windows, two folders are created in your specified Save to location, Exceptions and Build.

The Exceptions folder contains folders with installers of various kinds (EXE, AIR, MSI) that cannot be deployed using the main MSI installer (because it cannot contain an embedded installer). You must create separate SCCM installers for each of these, using instructions in the ExceptionInfo.txt file at the top level of the Exceptions folder. The folder can be empty if your package has no dependencies on other installers.

The Build folder contains an MSI file whose filename uses the Package Name that you specified, and a subfolder named Setup. The subfolders are required to run the MSI file and install the product successfully.

Create an SCCM package

Creating an SCCM package is a two-step process. First create a new SCCM package, then create install and uninstall programs.

Create a new SCCM package

  1. Open the New Package wizard.

    • Open the SCCM console.
    • Navigate to Computer Management > Software Distribution > Packages.
    • Right-click Packages, choose New, then click Package.

  2. In the New Package Wizard, name the new SCCM package.

    On the General tab:

    • Enter the name of the new SCCM package in the Name field. This field is required.
    • You can also enter values for the optional Version, Manufacturer, Language, and Comment fields.
    • Click Next.

  3. Specify the data source for the SCCM package.

    On the Data Source tab:

    • Select This Package Contains Source Files.
    • Click Set to the right of the Source Directory field. In the Set Source Directory dialog, select the type of path you want to use (UNC or local) and browse for or type in the path to the Build folder that contains the .msi file and supporting folders. Click OK.
    • On the Data Source tab, the path you just selected will show in the Source Directory field. Below that field, select Always obtain files from the source directory.
      Set the other choices as appropriate, then click Next.

  4. Specify where the SCCM package will be stored on distribution points.

    On the Data Access tab, select Access the distribution folder through common ConfigMgr package share, and then click Next.

  5. Specify distribution settings.

    • On the Distribution Settings tab, choose a sending priority. Select the Preferred Sender, if desired. Select other settings as appropriate, then click Next.
    • On the Reporting tab, select settings as appropriate, then click Next.
    • On the Security tab, select settings as appropriate, then click Next.

  6. View the new SCCM package summary.

    • Review all the settings for the new SCCM package. If you need to change anything, use the Previous buttons to do so and then the Next buttons to get back to this screen.
    • Click Next. The Confirmation tab is displayed.
    • Click Close to terminate package creation.

Create install and uninstall programs for the SCCM package

A package generates a single MSI file in the Build folder, which you use for both installation and uninstallation of the product or suite. (Uninstall is not available for update packages, only for installation packages.)

If you want, you can create two separate SCCM programs for an installation package: one for installation and another for uninstallation. Name these programs to make it obvious to the users on the target systems who choose what the commands will do.

  1. Open the New Program wizard.

    • From the SCCM console, navigate to Computer Management > Software Distribution > Packages.
    • Select the SCCM package you just created.
    • Under it, select Programs > New > Program.

  2. In the New Program wizard, specify the command line for the program.

    On the General tab:

    Enter a descriptive name (such as install_PS_1 or uninstall_PS_1) in the Name field, and an explanatory comment that describes what the program does.

    Click Browse. In the Open File dialog, choose the file type All Files (*.*), then browse to and select the MSI/EXE file. The details of this step vary for each command you create.

    For the install package, browse to your .exe file.

    When you return to the New Program wizard, append appropriate flags or options to the command after the filename in the Command Line text box.

    You must use the silent parameter for unattended installation. 

    Syntax:

    setup [--silent] [--ADOBEINSTALLDIR=] [--INSTALLLANGUAGE=]

    Example:

    setup.exe --silent --ADOBEINSTALLDIR="C:\InstallDir" --INSTALLLANGUAGE=fr_CA

    For more details on using this command, see Deploy using command line on Windows machines.

    For the uninstall package, browse to your .MSI file.

    For the uninstall package, use the msiexec command with the /uninstall parameter.

    Example:

    msiexec.exe /uninstall PS_1.msi /quiet

  3. On the Environment tab:

    • In the Program Can Run field, select Whether or not a user is logged in.
    • In the Run mode section, select Run with administrative rights. Be sure Allow users to interact with this program is turned OFF.

    Note: If you do not choose to run with administrative rights, the Application Manager writes its log file to a different location. See “Installation logs.”

  4. Set fields on the Advanced, Windows Installer, and MOM Maintenance tabs as appropriate, and click Next.

  5. Review the information on the summary screen. If you need to change anything, do so now. Then, from this screen, click Next. The Wizard Completed screen will appear. Click Close to terminate program creation.

Creating installers and uninstallers for Exceptions components

To create install and uninstall programs for the MSI, EXE, or AIR installers that are present in the Exceptions folder, use the commands described in the ExceptionInfo.txt file at the top level of the Exceptions folder.

For example, to create an SCCM install package for an MSI installer such as Adobe Flash Player 10, use this command:

msiexec.exe /i AdobeFlashPlayer10_plRel_mul.msi /qn

To create the uninstaller, use /uninstall instead of /i

msiexec.exe /uninstall AdobeFlashPlayer10_plRel_mul.msi /qn

Warning: For AIR-based installers, you can create a silent installer the same way, using the command listed in the ExceptionInfo.txt file. For these components, however, you cannot create a silent uninstaller. When uninstalling, you may need to uninstall AIR applications manually.

Select distribution points for the SCCM package

  1. Open the New Distribution Points wizard.

    • In the SCCM console, navigate to Computer Management > Software Distribution > Packages.
    • Select the SCCM package you just created.
    • Under it, select Distribution Points > New Distribution Points. This displays an introductory screen. Click Next.

  2. In the New Distribution Points wizard, select the distribution points to which you want to copy the SCCM package.

    It is assumed that at this point the distribution points you want to use for this SCCM package have already been created. You can select one or more distribution points for this package.

  3. View the Wizard Completed screen and click Close.

Advertise the SCCM package programs

Follow the directions in this section once for each SCCM package program you want to advertise. 

These directions assume you already have a collection with target systems where you will advertise the SCCM package programs.

  1. Open the Distribute Software to Collection wizard.

    • In the SCCM console, navigate to Computer Management > Collections.
    • Locate the collection you want to use to advertise this SCCM package.
    • Right-click on the collection name and choose Distribute > Software.

  2. In the Distribute Software to Collection wizard, choose the SCCM package to advertise.

    On the Package tab:

    • Turn on Select an existing package.
    • Click the Browse button next to the text field. In the Select a Package dialog, locate the desired SCCM package and select it. Then click OK. Your selection will appear in the text field on the Package tab.
    • Click Next.

  3. Make sure you have chosen the distribution points to which you want to copy the SCCM package.

    On the Distribution Points tab, select the distribution point(s) you want to use to distribute this SCCM package. Then click Next.

  4. Select the SCCM package program to advertise.

    On the Select Program tab:

    • The SCCM package name and its programs are displayed. In the Programs: area, select the program you wish to advertise.
    • Click Next.

  5. Set advertisement characteristics.

    On the Advertisement Name tab:

    • Enter a name for the advertisement in the Name field.
    • Optionally, enter a comment that describes the advertisement in the Comment field.
    • Click Next.

    On the Advertisement Subcollection tab:

    • The name of the collection you chose for this advertisement is displayed in the Collection field. Choose whether you want this advertisement to be sent to any subcollections of this collection. The results of your choice are displayed in the field at the bottom of the tab.
    • Click Next.

    On the Advertisement Schedule tab:

    • Set the date and time you want the advertisement to occur.
    • Specify whether the advertisement will expire. If you want it to expire, set the expiration date and time.
    • Make any other settings as necessary and click Next.

    On the Assign Program tab:

    • Choose whether you want running this program to be mandatory. If you do, specify the date and time to force its execution. Notice the advertisement date from the previous tab is displayed here.
    • Set an expiration date if you want.
    • Choose other options as desired.
    • Click Next.

  6. View the summary screen for the advertisement.

    Review the information on the summary screen. If you need to change anything, do it now. Then, from this screen, click Next.

    The Wizard Completed screen will appear. Click Close to terminate advertisement creation.

When the SCCM package is advertised, the Windows toolbar of the target machines displays a notification that a program is scheduled to run.

Further reading

 Adobe

Get help faster and easier

New user?

Quick links

View all your plans Manage your plans
View quick links
Hide quick links

Legal Notices    |    Online Privacy Policy