Posted on 05-15-2015 08:17 AM
Hi y'all,
I'm considering a modular approach to the Creative Cloud apps, and I recently discovered that running the uninstaller (created by Adobe CCP) disassociates the device from the license in the Adobe Portal, deactivating it. That's great, except what if I have multiple packages in Self Service (say, one for video production and one for web design)? Would uninstalling one, deactivate the Creative Cloud license for both? Has anyone found themselves in similar waters? It's safe to assume we are only interested in the full Creative Cloud license (all of the apps) for this example.
Thanks!
Solved! Go to Solution.
Posted on 05-15-2015 09:43 AM
Note we have an ETLA and serialized installations, so I can only speak directly to that.
In our case if we use CCP to create a "serialized" installation of an application, the CCP uninstaller removes that serial number. So (ignoring the legality issues of breaking apart "suite" licenses) if we created:
And then we:
Premiere CC 2014 would become unserialized, since the AE CC 2014 uninstall removes the license ("12345") that Premiere depends on. My solution depends on the ability to do three things:
If you can do those three, see:
Also worth reading: Fixing Adobe CCP’s Broken Uninstallers
Posted on 05-15-2015 08:50 AM
Posted on 05-15-2015 09:43 AM
Note we have an ETLA and serialized installations, so I can only speak directly to that.
In our case if we use CCP to create a "serialized" installation of an application, the CCP uninstaller removes that serial number. So (ignoring the legality issues of breaking apart "suite" licenses) if we created:
And then we:
Premiere CC 2014 would become unserialized, since the AE CC 2014 uninstall removes the license ("12345") that Premiere depends on. My solution depends on the ability to do three things:
If you can do those three, see:
Also worth reading: Fixing Adobe CCP’s Broken Uninstallers
Posted on 05-15-2015 11:49 AM
Posted on 05-15-2015 12:13 PM
Please take the time to complain to Karl Gibson and the Adobe IT team about this. They've acknowledged it's a bug but haven't provided any details regarding priority or when they expect to have a fix released.
Posted on 05-15-2015 11:04 PM