91
edits
Changes
→Lightroom: Fixes that didn't make it into my last version, plus a new fix because Lightroom tampers with the default profile
You need to grab a copy of the Adobe Creative Cloud Packager. It's currently available here: [http://helpx.adobe.com/creative-cloud/packager.html].
Install the CCP application, launch it and feed it the info it requires. This will include your serial number, installation media location, output folder and options on which 'features' you wish to suppress including auto-updates etc. Note that CCP will stay logged in to your Adobe account until you explicitly log out.
The application will create a folder in your specified location containing an MSI file and a couple of subfolders. You must copy all of these into your software deployment location.
This package does not depend on any other packages, but it's set to a lower priority than the other Adobe product packages so that it will run after they're installed in the hopes of getting everything installed and updated in a single run. However, sometimes it will take several runs for all updates to install correctly.
Note that Remote Update Manager does not update Acrobat or products like Lightroom 5 that use <code>ExceptionsDeployer.exe</code>. To update programs that use exceptions, you need to re-run Creative Cloud Packager.
There is a [https://forums.adobe.com/message/6898298 defect in RemoteUpdateManager] which sometimes causes it to hang forever. '''If you use [[WPKG-GP]] or another solution that prevents user login while WPKG is running, users won't be able to log in until RemoteUpdateManager times out and WPKG kills it.''' If this might affect your site, '''set the timeout value to something reasonable''' or deploy new updates by re-running Creative Cloud Packager instead of with RemoteUpdateManager. The package as provided uses a three-hour timeout because normal update installation has been observed to take at least that long and the author's site is not configured to block user login. '''Do not set the timeout to 0.'''
</package>
</source>
= Special provisions required for silent removal =
Some Adobe products do not leave an easy-to-find package code or otherwise are difficult or problematic to silently remove. According to Adobe support, you'll need to use the [https://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-problems.html#enterprise Creative Cloud Cleaner Tool] to perform a silent uninstall.
These package definitions assume that the Creative Cloud Cleaner Tool has been unzipped into <code>%SOFTWARE%\AdobeCC\cleaner</code>. For packages where CC Cleaner Tool is known to be needed, cleanup XML files are provided.
= Individual packages =
== Lightroom ==
<source lang="xml">
<variable name="PKG_FILEVERSION" value="5.7.1.10" architecture="x86" />
<variable name="PKG_INTERNAL_VERSION" value="23" architecture="x64" />
<variable name="PKG_EDITION" value="cc" architecture="x64" />
<variable name="PKG_EDITION_LONG" value="6.0.1" architecture="x64" />
</install>
<!-- Lightroom insists on creating a link on the default desktop. I can't
find an environment variable that points to the default profile, so we
do this and hope it doesn't break on localized Windows editions -->
<install cmd='%COMSPEC% /c del "%SYSTEMDRIVE%\Users\Default\Desktop\Adobe Lightroom.lnk"' architecture="x64" >
<exit code="any" />
</install>
<!-- Like other things that use ExceptionDeployer, Lightroom 6 won't
</package>
</source>