Skip to main content
Question

Removing Adobe CC 2015 in preparation for CC 2017

  • December 13, 2016
  • 38 replies
  • 295 views

Show first post

38 replies

Forum|alt.badge.img
  • New Contributor
  • April 5, 2017

@endor-moon thank you for this script. Will help a ton. The only thing i changed was with the user's folders. Need to put wildcard in to delete the crud from all the user's folders(if needed).

So instead of: rm -Rf /Users/admin/Library/Application Support/Adobe
Now: rm -Rf /Users/*/Library/Application Support/Adobe

Thank you


donmontalvo
Forum|alt.badge.img+36
  • Hall of Fame
  • May 27, 2017

Wanted to circle back, finally got around to hitting some requests to deploy security patches for Adobe CS/CC apps.

The issue with these apps, as always are:

  1. Patch can potentially change install path, leaving vulnerable untouched, so we have to find a way to remove.
  2. Old version that needs to be removed can be CS6, CC2015 or CC2017, so need a reliable way to handle removal of any of those versions.

As is the case whenever a new version of Adobe CS/CC is released, we open a ticket to ask the same question (due diligence).

The response we got from Adobe this time around was refreshing optimistic, compared to the response we got when CC2015 was released. :)

Hi Don, For CC versions you should use uninstall the package from CCP. There is no way to reliably, comprehensively and silently remove older versions than that. Thanks, XXXXXXXX

Since Adobe's dev team seem to feel it is a good idea to sometimes change the path to an application, the issue we run into is where this app:

/Applications/Adobe FancyApp CC 2017/Adobe FancyApp CC 2017.app

...is updated to

/Applications/Adobe FancyApp CC 2017.1/Adobe FancyApp CC 2017.app

...or

/Applications/Adobe FancyApp CC 2017/Adobe FancyApp CC 2017.1.app

...or

/Applications/Adobe FancyApp CC 2017.1/Adobe FancyApp CC 2017.1.app

...and you're left with the vulnerable version AND the updated version both installed.

So its good to see CC2015/CC2017 "Uninstallers" work (of course we'll have to see), but not surprised that older CS uninstalls are a crap shoot.

For CS versions, we'll resort to the usual BFH, witchcraft, and secret sauce to get those removed.


Forum|alt.badge.img+13
  • Valued Contributor
  • November 21, 2017

I've had issues using the built uninstaller with the package I made, but I found the individually generated uninstallers, worked alot better.


Forum|alt.badge.img+5
  • Contributor
  • March 6, 2018

Just and FYI. You can use pkill obe instead of pgrep obe | yada yada. Saves a pipe and an xargs. Keepin it simple.

Cheers. J


Forum|alt.badge.img+11

Looking for a way to remove 2017 before going to 2018 now would this script still work for that?


dsweigart
Forum|alt.badge.img+5
  • Contributor
  • March 29, 2018

@mattmcchesney I was able to get this to work. I first went back to the creative cloud packager and created an uninstaller. Once I had that uninstaller created I then used composer and created a .dmg of that unistaller folder by doing the following.

  1. Open Composer
  2. Drag the executable to Sources in Composer
  3. Create a DMG from the executable
  4. Upload the DMG to Casper Admin

I then created a policy to install the DMG on a test computer. Then I was able to execute the exec from the uninstaller by running a command that directs to the path. That command can be put in the Files and Processes payload where it says Execute Command. The path that you need to place in the Files and Processes payload is the path to where the executable is located.

I hope this helps.


Forum|alt.badge.img+2
  • New Contributor
  • August 29, 2018

@MattCasper I am having the same issue you was having. Did you ever get it to work from 2017 to 2018??


Forum|alt.badge.img+10
  • Contributor
  • October 17, 2018

@dsweigart I took the same approach you did and everything seemed to work. Im looking at the cleanup scripts above to see if those files got left behind and sure enough they did.

Did you bother to cleanup anything or just run the uninstaller?

Did you install a newer version afterwards and did it install correctly?

Thanks

Mark


dsweigart
Forum|alt.badge.img+5
  • Contributor
  • October 18, 2018

@msnowdon I just ran the uninstaller and then in a separate package via Self Service we installed 2018 and that installed correctly. Let me know if you have any other questions.


Forum|alt.badge.img+10
  • Contributor
  • October 19, 2018

@dsweigart Just an update. I ended up bundling the uninstaller and the new package into a dmg file. The policy places the dmg file in a temp folder and I have a script to run the uninstall package, pause for 5 minutes and install the new package.

Tested it and it works!

Thanks


dsweigart
Forum|alt.badge.img+5
  • Contributor
  • October 19, 2018

@msnowdon That's awesome! You're welcome.


Forum|alt.badge.img+4
  • Contributor
  • March 7, 2019

@dsweigart i had to remove CS6 CC2015 and CC2017 installations while CC2018 had to remain, followed your instructions for removing CC2015 and CC2017 , for CS6 i used an Adobe script to remove it, combined both in 1 policy worked like a charm.
Only some folders remained because of plugins but that was easily solved.
thx for he tip, it was life saving.


dsweigart
Forum|alt.badge.img+5
  • Contributor
  • March 7, 2019

You’re welcome @ateazzie