• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

adobecreativecloudcleanertool.exe parameter/argument detailed list

New Here ,
Feb 24, 2023 Feb 24, 2023

Copy link to clipboard

Copied

We use enterprise level CC software. I have been experimenting with cleaning up installs. i have successfully been able to script the adobecreativecloudcleanertool.exe with the parameter --removeAll=ALL and run this behind the scene, pushing the cleaner file to the temp directory and remotely blowing away all CC products, however this is not what i want to do in most cases.

 

Due to circumstances I have no control over, local administrators install adobe CC products on top of each other and some standalone (pre CC) products still exist on some machines resulting in huge array of outdated and duplicate versions of CC products.

 

I am trying to find a paper on all the arguments i can feed to the executable cleaner tool to acheive the following (assuming say our company currently has CC6 and associated products tested and ready for deployment) I want to blow away every version of CC that is not up with our current versions and all of its sideloaded programs BUT leave all of CC6, associated products, dependencies and login credentials intact.

 

Is this possible with the current cleaner tool? would i be able to develop an argument list (in simple terms) -remove all versions earlier that CC6? or create a list of commands such as cleaner.exe - remove all CC5, cleaner.exe - remove all CC4 etc to acheive the goal of running the executable through psexec to get a clean environment with only the CC6 software remaining?

 

The clean all option has worked well but leaves the local administrator responsible for reloading the current version and assisting the customer with signing back into their account which would be a scenario created on alot of machines, put customers down with no CC software until they request a reload and so my current tool will only be usefull on a case by case basis.

 

I am also looking for a generalized location for the registry entry (if one exists) that will force a version of CC into auto update mode so that its individual programs will self update without the customer needing to update them, or even flip the switch in the options.

 

Maybe im shooting for the moon here and apologize as my spelling can be atrocious, however any ideas the community has would be very helpful

TOPICS
Deploy and package apps , Enterprise

Views

469

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Feb 25, 2023 Feb 25, 2023

@Ash28575677tu2f  I would recommend using method 3 from the following link wherein you can defined the version you would like to uninstall from the device in XML and run the executable file silently: https://helpx.adobe.com/enterprise/using/uninstall-creative-cloud-products.html#uninstall-select-versions

Votes

Translate

Translate
Adobe Employee ,
Feb 25, 2023 Feb 25, 2023

Copy link to clipboard

Copied

LATEST

@Ash28575677tu2f  I would recommend using method 3 from the following link wherein you can defined the version you would like to uninstall from the device in XML and run the executable file silently: https://helpx.adobe.com/enterprise/using/uninstall-creative-cloud-products.html#uninstall-select-ver...

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines