Skip to main content
anish.aqua
anish.aqua
Participant
May 13, 2026
Answered

Automating Adobe Application Deployment to Intune / SCCM

  • May 13, 2026
  • 1 reply
  • 105 views

Hello Adobe Community,


I’m currently working as a Patch Administrator and looking for guidance on automating the deployment of Adobe products (e.g., Acrobat, Creative Cloud apps) into Microsoft Intune and SCCM (Configuration Manager).


At present, our process is entirely manual:

  • We download Adobe installers/packages from the Adobe Admin Console
  • Repackage or prepare them for deployment
  • Upload and deploy them via Intune/SCCM

This approach is quite time-consuming, especially when handling frequent updates and multiple products.


What I’m Looking For
I would like to understand if there are more efficient or automated approaches available, such as:

  • Integration between Adobe Admin Console and Intune/SCCM
  • APIs, scripts, or tools for automated package creation and deployment
  • Best practices for managing Adobe updates at scale
  • Any existing workflows or pipelines others are using to streamline this process

Additional Context

  • Environment: Enterprise (Windows endpoints)
  • Deployment tools: Microsoft Intune & SCCM
  • Goal: Reduce manual effort and improve deployment efficiency for Adobe applications and updates

If anyone has implemented a similar automation or can point me toward relevant documentation, tools, or workflows, I would greatly appreciate your insights.

Thank you in advance for your help!

Best regards,
Anish

    Correct answer BaniVerma

    Hi ​@anish.aqua, 

     

    Managing Adobe deployments at scale across Intune and SCCM, especially with frequent updates across multiple products, is genuinely one of the more time-intensive workflows in an enterprise environment, so we completely understand the drive to find a more efficient approach. Good news: there are official Adobe tools built specifically for this.

    Package creation - the starting point

    Regardless of subscription type, packages are created from the Packages section in the Admin Console. You can also enable email notifications there to be alerted when new product versions become available for previously created packages, a small but useful way to stay on top of when action is needed.

    For managing updates at scale

    Two dedicated tools can significantly reduce the manual effort you're dealing with:

    • Adobe Remote Update Manager (RUM) gives you a command-line interface to remotely trigger Adobe updates on client machines without needing to log in to each one. You can invoke it via SCCM or Intune as part of a scripted workflow, targeting all products or specific ones. One important limitation to keep in mind: RUM handles updates only, not full version upgrades. For upgrades, you'd need to either create a new package from the Admin Console or have users update through the Creative Cloud desktop app. Full details here: https://helpx.adobe.com/enterprise/using/using-remote-update-manager.html
    • Adobe Update Server Setup Tool (AUSST) lets you host Adobe updates on an internal server, so client machines pull from within your network rather than from Adobe's servers. When used alongside RUM, you can push updates from that internal server on demand. Full details here: https://helpx.adobe.com/enterprise/using/update-server-setup-tool.html

    Hope this gives you a clearer picture of what's possible. Feel free to follow up here with any questions as you work through the setup.

    Thanks, 

    ^BS

     

    1 reply

    B
    Community Manager
    BaniVermaCommunity ManagerCorrect answer
    Community Manager
    May 13, 2026

    Hi ​@anish.aqua, 

     

    Managing Adobe deployments at scale across Intune and SCCM, especially with frequent updates across multiple products, is genuinely one of the more time-intensive workflows in an enterprise environment, so we completely understand the drive to find a more efficient approach. Good news: there are official Adobe tools built specifically for this.

    Package creation - the starting point

    Regardless of subscription type, packages are created from the Packages section in the Admin Console. You can also enable email notifications there to be alerted when new product versions become available for previously created packages, a small but useful way to stay on top of when action is needed.

    For managing updates at scale

    Two dedicated tools can significantly reduce the manual effort you're dealing with:

    • Adobe Remote Update Manager (RUM) gives you a command-line interface to remotely trigger Adobe updates on client machines without needing to log in to each one. You can invoke it via SCCM or Intune as part of a scripted workflow, targeting all products or specific ones. One important limitation to keep in mind: RUM handles updates only, not full version upgrades. For upgrades, you'd need to either create a new package from the Admin Console or have users update through the Creative Cloud desktop app. Full details here: https://helpx.adobe.com/enterprise/using/using-remote-update-manager.html
    • Adobe Update Server Setup Tool (AUSST) lets you host Adobe updates on an internal server, so client machines pull from within your network rather than from Adobe's servers. When used alongside RUM, you can push updates from that internal server on demand. Full details here: https://helpx.adobe.com/enterprise/using/update-server-setup-tool.html

    Hope this gives you a clearer picture of what's possible. Feel free to follow up here with any questions as you work through the setup.

    Thanks, 

    ^BS

     

      rosenec
      rosenec
      Participant
      May 14, 2026

      Hi ^BS,

      In relation to this thread and pretty much in the same situation as Anish stated in his comments, I’d like to ask if there’s a download location anywhere with Adobe for individual Creative Cloud products/downloads? Needless to say, the proposed solutions will not suffice in our environment (that is AUSST and RUM) as we use a specific packaging tool that is integrated already in our Intune process and all our third-party updates outside Microsoft pass through it for deployment.

      We won’t be able to extend our setup to use those tools only for Adobe while using the other tool for everything else, so I’d like to put a side question how exactly can we go about deploying e.g. Photoshop or Dreamweaver individually to secure-patch our clients. I’d like to make a note that we only deploy security updates and it’s quite relevant for us that we gain control over the installers before shipping them to hosts (as we add some internal friendliness to them for our users). 

      If you can help and point us out how we can obtain individual installers as part of our Adobe subscription, that would be great! I’m new to this just yet, so it’s been pretty hard to get my hands on those. Thank you in advance

       

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices