Author Archive: Eric Wilde

Macworld 2010

Thanks to any of you who attended our discussion today at Macworld 2010. Its always great to see customers face-to-face, even on such a trying topic as deployment and provisioning. The presentation was short and we had a lot of good questions or requests come our way.
Also I’d like to thank a customer of ours, John Welch, for helping to arrange this presentation at Macworld.
Updated (Feb 18, 2010): A few people asked for more details about what happened at Macworld 2010. In short:
The target audience was those individuals who deploy Adobe Creative Suite software for others. That’s generally system administrators for volume deployments; but, includes a handful of others such as OEM distributors or those who make tools such as InstaDMG. We discussed the history of deployment and licensing issues with Adobe Creative Suite and our plans for the immediate future.
The crowd asked some tough questions and provided really good feedback to us. Although we cannot solve every issue folks raised quickly, we do believe we’re addressing the most pressing issues first.
Please find attached the slide presentation used at Macworld 2010.
IT811_E_Wilde.pdf

Interactive Walkthrough of Volume Deployment Proposal

You are invited to participate in a live interactive walk through of our upcoming Enterprise Deployment experience. This session is targeted to those who deploy in large enterprise sized environments and will be conducted via an Adobe Connect session and hosted by Sharma Hendel, our Lead Sr. Experience Researcher. There is limited space available, so please sign up early.
The session will take place at Friday 2/12/10 at 10 a.m. to 12 p.m. PST. Please contact Victoria Selwyn (vselwyn@adobe.com) to reserve your spot today.
Thanks and regards,
Victoria Selwyn
Update: Thank you all for the responses. We’re full now and not taking any more requests for inclusion on this interactive walk through. –Eric

Removing Deactivation Limit

Currently, activating Adobe software has a limit on the number of deactivations that can occur. For all Adobe activating software (including Acrobat-based products), that deactivation limit is 20. Starting January 15th, the deactivation limit will no longer be enforced.
Deactivations are useful when installing the software on a new system. Adobe’s license agreements stipulate that the software can be installed on two different systems at any one time. Activation is intended to enforce this license agreement. When installing on a new system it is often necessary to remove the software from older systems. That removal is tracked by deactivating the software on the old system prior to removing it.
The deactivation limit has caused numerous problems and I’m very happy to see it go. As stated above, we should go live on the a new activation server implementation on January 15th that completely removes the deactivation limit. Although deactivation is still necessary (which causes some other problems), there should no longer be any limit to the number of deactivations.
In email discussions with a couple of readers I mentioned that this implementation may go live as late as March. I’m happy to say that we were able to certify and post it earlier.
Note that this affects software as far back as Adobe Creative Suite 3 and Acrobat 8.
Update: Per one of the comments, here’s a URL for getting help from adobe.com
Contacts at adobe.com for support.

Closing Firefox to Install Adobe Creative Suite

Customers have stated very clearly that they do not want to close other applications while installing Adobe software. For some applications, we really do have to quit those processes in order to successfully install due to locks on system resources, etc. This may be acceptable with respect to closing other Adobe software; but, it isn’t acceptable when users have to close critical tools such as browsers.
We had really hoped to improve this aspect of our installers in the coming CS releases. We have made some inroads on our upcoming installers; but, there still are some limitations. Most importantly, there are two cases where we still need browsers to close before we can successfully finish installation:
(1) When installing plugins for various browsers we need those browsers to quit. This usually happens when installing a product that also installs the Flash Player. Such products include Flash Pro and any Creative Suite that includes Flash Pro in its distribution. Fireworks also deploys some browser plugins and needs browsers to quit.
(2) When installing some color settings files we need Firefox 3.0 to quit. Firefox 3.0 holds a lock on system color files while executing. We deploy versions of these same color files and cannot do so when Firefox has a lock on them. This was fixed with Firefox 3.5; however, there are still 14.5% of our user base using a version of Firefox prior to Firefox 3.5. Complicating this fact is that the process name for Firefox has no indication of version number. So we will still require Firefox to quit before installing upcoming Adobe product releases. Once more users have shifted to Firefox 3.5+ we will be able to remove this obstacle.
We have at least addressed one of the worst consequences of needing to close browsers while deploying by limiting the amount of time the browser needs to be down. With upcoming CS releases non-Adobe conflicting processes can remain open throughout most of the installation process. We cache any locked files until the very end of the install process. At that point a warning dialog is provided to the user to close conflicting processes such as browsers for the last minute or so of installing these few remaining, cached files. This will allow users to keep open their browsers for the vast majority of time consumed in deploying. Silent deployments will, of course, not have such a warning dialog and so will need the browsers to be down during the entirety of the deployment.
This all applies to future Adobe Creative Suite retail releases. CS3 and CS4 installation will not receive the changes mentioned above and will still need browsers to quit.

Survey for Volume Deployments of Adobe Creative Suite

To set a baseline as well as gather data from a broad array of system administrators, we put together a survey to understand where are the costs customers incur when deploying Adobe Creative Suite software. We’ll use this data to more finely tune the set of features delivered in the Enterprise Deployment Toolkit for future Adobe Creative Suite releases. We’ve heard a lot of feedback from customers both here on the blog and elsewhere. We’d love to hear more input from you all so that we can deliver on the most important features for volume deployments going forward.
Please provide feedback here.
We’ll be collecting the data and closing down the survey at the end of January. After the next release of the Enterprise Deployment Toolkit we’ll perform this survey once more to see how effective the release has been and prioritize follow on features.
Thanks,
–Eric
Updated: It seems the word ‘cost’ is causing some confusion. By cost I mean anything that might take up time or resources in order to succeed at the deployment, not just the $ amount for support software or hardware. These are generally areas that cause pain and grief for those who do the deployment. –e

Software Tagging in Adobe Products

Akash Jain and Ravi Prakash Singh are developers on the core engineering team who focus on the installation technology.  Here they describe the usage of tags to help manage software deployments across enterprises. — Eric

Software tagging is the process of maintaining a set of tag files (.swtag) on a client machine to determine the install and license state of various software products. This tagging process can be used to assist in Software Asset Management (SAM) tasks and there is an ISO industry standard for this which is denoted by ISO/IEC 19770. For asset management purposes an administrator can run any SAM tool that will scan the .swtag files on the client machine and parse them for analysis and reporting purposes.

Software entitlement tags (.swtag) are files that provide authoritative identifying information about software licensing rights. These entitlement tags taken together with 19770-2 software identification tags, which accurately identify installed software programs, facilitate conducting software audits, reconciliation, and license compliance management with ease.

Prior to ISO/IEC 19770-2 electronic discovery of software licensing rights was non-existent. Entitlements data was commonly found in printed documents like purchase orders, invoices, and purchase receipts which were hard to organize and track. Standardization of entitlement data tags provides uniform, discoverable data for the license compliance processes of Software Asset Management (SAM), making it possible to optimize software license compliance.

Software Tagging in Existing Adobe Products A9 and CS4

Acrobat 9 was not only the first Adobe product but the first ever product to utilize ISO/IEC 19770-2 software identification tags. Adobe Creative Suite 4, which was shipped in 2H2008, was next to follow. Since the active development cycles for these products closed prior to the current ISO/IEC proposed Final Draft International Standard v1 19770-2 dated 2009-05-13, this implementation is based on an earlier proposed Final Committee Draft version released on 2008-08-04.

Adobe Creative Suite 4 products dynamically generate tag file during install time and product launch time. They also support a self‐healing capability. The self-healing capability restores tag files to their correct state at product launch time in the event of a missing or corrupted tag file. Licensing state changes or product configuration changes can also result in a change to the tag files.

Software Tagging in Future Adobe Software

While ISO Tagging in Adobe Acrobat 9 and Adobe Creative Suite 4 was based on the Final Committee Draft version released on 2008-08-04, future Adobe software will incorporate the changes proposed by ISO/IEC in the Final Draft International Standard v1 19770-2 dated 2009-05-13. As with Adobe Acrobat 9 and Adobe Creative Suite 4, future Adobe products will dynamically generate tag files during install time and product launch time and also support self-healing capability. To incorporate the changes of the new draft there are few changes in different areas of tagging process.

1. Tag File Location in A9/CS4 and future Adobe software

CS4 and Acrobat 9

Future Adobe software

Apple Macintosh OS:X

/Users/Shared/Adobe/ISO‐19770

/Library/Application Support/regid.1986-12.com.adobe

Windows XP and Server 2003

%ALLUSERSPROFILE%\Application Data\Adobe\ISO‐19770

%ALLUSERSPROFILE%\Application Data\regid.1986-12.com.adobe

Windows Vista and Server 2008

%PROGRAMDATA%\ Adobe\ISO‐19770

%PROGRAMDATA%\ regid.1986-12.com.adobe

2. Tag File Naming convention in A9/CS4 and future Adobe software

CS4 and Acrobat 9

Future Adobe software

Tag File Name

<product_title>‐<unique_software_identifier>.swtag

<regid>_ <product_title>‐<unique_software_identifier>.swtag

Where

<product_title> ‐ is the product name, which will be the same as the <product > inside the tag file.

<unique_software_identifier> – is a GUID value for A9 while for CS4 it is combination of product licensing identifier and licensed locale, which will be same as <softwareID> inside the tag file. Trial Tag file for CS4 will have locale information as “ALL”

<regid> – regid.1986-12.com.adobe which refers to the regid of Adobe

<product_title> ‐ is the product name, which will be the same as the <product > inside the tag file.

<unique_software_identifier> – is combination of product licensing identifier and licensed locale, which will be same as <softwareID/unique_id> inside the tag file. Locale information is applicable only for non-trial Tag files.

3. Important Tags and values

All mandatory identity elements are supported along with some optional information. Some tags have been deleted, added and renamed. Important tags with their possible values are shown in tag file examples.

a. Example of Tag File in A9/CS4

Since Adobe supports what is known as “Flexible Licensing” an application can be installed and serialized as a standalone app or as a part of a Suite. There are some differences in the tag files in both the cases.

i. Software tag files for Standalone Application for e.g. Photoshop licensed by itself looks like:


ii. Software tag file for an Application licensed as a part of Suite for e.g. Photoshop licensed as a part of Adobe Creative Suite Design Premium looks like:

4. Process/Stages of Tag file Updation:

a. Product install – On product install a tag file gets created for

i. Non-Serialized Install: <entitlement_required> set as “false”.

ii. Serialized Install: <entitlement_required> set as “true”.

b. Product launchOn product launch existing tag file is updated if present otherwise a new one is created. Tag file is updated based on licensing state changes thusly:


tagtable.tiff

c. Product Uninstall – Tag file is not removed from the disk even though the product is un‐installed. In case product is selected to be deactivated at uninstall time then the values of the tag file are updated as in the deactivation case above.

d. Product Reinstall – At reinstall the previous files are updated which were left behind on uninstallation with the new status.

5. Software reconciliation: A9, CS4 and future Adobe software which are either serialized or activated will have entitlement_required set to “true” and therefore need be considered for reconciliation as per ISO/IEC 19770-2 standard.

 

 

 

Expiring Licenses

Sanjeev Biswas and Kanika Dalmia are two core engineers in the licensing domain at Adobe. They write below about one of the common customer service calls and what we’re doing to fix it longer term. — Eric
The handling of license expiry in Adobe CS4 has been one of the highest customer calls generator for Adobe, with anxious customers calling in to find the way out of this dead-end.
This ‘License Expiry’ screen is all too familiar to many of us
LicensingExpiredCS5.jpg
In CS4, “License Expired. Licensing for this product has expired” was displayed to the user if either the software build had expired or if the serial number used to license the application had exhausted its validity and had expired. This was a hard-stop and it prevented the user from running the application again. In particular, the user of expiring serial numbers had no direct way to resolve the license expired state and renew his license with another serial number. This situation becomes more complicated when other Adobe applications / suites are installed and licensed on the machine. The user was blocked on this and ended up ringing customer support.
There has been a workaround to the License Expiry issue, wherein the user had to manually roll back the system clock by a few days to re-launch the application, and then deactivate the license with the “Help-> Deactivate” option with erase serial number preference set. This would remove the expired license and the corresponding serial number from the user system. So when the user resets the system date back, on subsequent application launch the user is presented the user interface to enter a new serial number.
In CS4 handling of license expiry, the user wasn’t reminded that the product’s license is about to be expired and also, the user was not given an opportunity to renew his license with a new serial number. The user was bound to use the workaround, to be able to run the application.
In our next version, the design of the license expiry workflow has been altered to effectively tackle all the issues in CS4 handling of license expiry.
In our next version, when the product is launched the check for license expiry is performed. If the serial number associated with the license has expired, the user would not be displayed a hard-stop alert as was done in CS4. Instead, the module responsible for licensing of the product would bring up a user interface. This license expiry user interface screen would

  • Inform the user that the license in use has expired with an error message.
  • Additionally, it would provide an option to the user to enter a new serial number to renew his expired license.

This is like a ‘bonus launch’ of the product as the product is giving a bonus opportunity to the user to renew his expired license by entering a new serial number. This eliminates the need for previously used workarounds, to bring up the user interface (serialization screen) for entering an alternative serial number in case of license expiry.
If the user does not use the ‘bonus launch’ of the product to renew his license, then on every subsequent launch of the product, the license expiry user interface would be displayed, prompting the user to enter a new serial number.
With this design, the user would no longer be blocked on license expiry. Just a new serial number is to be procured and provided in the user interface, to continue to run the application seamlessly.
Improving the user experience for all adobe products is one of the principal design consideration for the next version of our licensing solution and, through this approach, we aim to do just that and thereby also reduce the volume of technical support calls.

Spam Filters

We recently noticed that our spam filters have been overzealous for the last four weeks. Many comments have been delayed between 2 days and 4 weeks before being posted because of this effort. The spam filters are all cleared out at this point and I’ll go try to fix them now. Sorry for the delay in getting your recent comments posted.
Now to get those filters fixed and start reading all the comments that were blocked…

Updater Approach

Hello all. Its been a while and we’ve been busily working on various features for deployment and provisioning. One area that has seen a fair bit of attention lately is the workflow for updating Creative Suite products. Ravi Prakash Singh is the lead development engineer on the new updater team. Below he talks about some of the design goals and solutions used for the next version of the updater workflow. – Eric
Adobe’s updater technology through CS4 is known as the Adobe Update Manager (AUM.) AUM has a long history of various problems. Our user community has been vocal about the number and types of problems experienced through AUM. In the next instance of the Creative Suite, we intend to provide a different update experience that should address a number of the most egregious problems discussed thus far. In particular:
* Failure of an update to successfully apply to a user’s system
* Failure to adequately roll back a partial or failed update, thus leaving the user’s system in an unusable state
* The update process interferes with users trying to get their own work done
When we started out the design for the new Adobe Updater we set a few simple goals:
* Make the Adobe Updater install the updates successfully and if the updater fails, ensure whatever was installed as part of updater is rolled back and the machine is back to its orginal state.
* Make the Adobe Updater non-intrusive. The Adobe Updater should not interfere with the user’s tasks by poping dialogs in middle of your extremely critical workflows. It will not be an in your face application.
* Make sure the Adobe Updater when running does not hog your CPU cycles.
* Using the Adobe Updater should be a pleasant experience.
* Checking for updates is silent and the notification for available updates is clean and unobtrusive.
* Provide ways for system administrators to turn-off updates completly. Secondarily, we also want to enable easier management of updates by system administrators.
In order to achieve the desired reliability, sensitivity to system CPU cycles and roll back ability, the updates themselves will use the exact same deployment engine as the original installer. In past versions, the updater was managed by one team while the patches and installation were managed by another team. We’ve brought these teams together into a single organization for better cooperation between them. The technology that lays the bits down on the users’ systems at install time will now be the same technology that updates the products post-install. This solution simplifies the implementation and makes it more robust by having consistent use of installed component databases and deployment strategy.
In order to ensure the updater is non-intrusive, we intend to have the client machine know about each update within 24 hours of that update being advertised by Adobe servers; however, users are notified either when they quit their app (not at app launch or in the middle of application use) or by an unobtrusive notification elsewhere on the system (e.g. a badge on the right side of the menu bar on a Mac.) There are two main parts to this approach:
1) Let the client machine know about updates as soon as it is hosted and made available by Adobe. To achieve this goal the updater will not be linked to Adobe product launch. Instead it will run as a scheduled activity independent of any product. During installation of an Adobe product, the Adobe Updater will be added as a task to the Task scheduler on Windows and as a Launch Demon on Macintosh. This step will help the updater perform a scheduled check for updates in silent mode. Such silent checks should occur at 2:00 am.
Minimal resources are used to check for updates. If you are not online at 2:00 am no connection will be initiated. The updater will wait until the following day at 2am to check again.
2) Once the update is discovered and downloaded, notification for the update is non-intrusive. In particular, there is no popup dialog that tells you an update is available and requires your attention. The notification itself will depend on the platform; but, will be somewhat similar to other status notifications on that platform. For example, on Mac the notification will likely be a badge on the right side of the menu bar indicating the status of an update. This is much like the status of other Mac services such as Time Machine or instant messaging clients.
If the user takes action on the notification then a dialog will appear that lists what applications have updates available and provide easy access to user preferences. As in CS4, all updates are cumulative. This means you should not see one update after another in serial for any given product.
There are a few more items to touch upon here:
Updates UI – When launching the updater, it will be possible to explore each product with an update to see which updates are pending, a description of the update and what other products are affected by those updates.
Notification UI – When you express interest in an update notification, a dialog will display showing which Creative Suite products have pending updates. It will be possible to explore each product with an update to see which updates are pending, a description of the update and what other products are affected by those updates. It is also possible to access user preferences from this dialog.
Preferences – To let users control Updater behavior, there will be preferences options for
a) Turn on / off menu notification
b) Disable/enable Auto updates for CSXS Services.
c) Auto download/install updates.
Enterprise Support – Support for volume deployments include the ability to turn off the entire update system at install time as well as the above mentioned user preferences. In addition, we have tentative plans for post-ship delivery of instructions on how to host Adobe’s patches directly on your own servers. This enables end users to use our Adobe Updater but recognize, download and apply patches directly from volume customers’ own servers.
Scheduled Check for Updates – Update checks would run as a scheduled activity; on Windows as a task (in the Task scheduler) and on Mac as a Launch Agent (via plist in ~/Library/LaunchAgents). This check would be performed on daily basis at 2:00 am. If the system is asleep at 2:00 am, then the next check for an update would occur when the system awakens. If system was shutdown at 2:00 am then update check would be performed at restart/user logon (via Run key on Windows and plist in /Library/LaunchAgents on Mac). If still there is a missed update check in past 24 hours, product launch would ensure that an update check is scheduled to occur after 2 hours.
Non-Admin Users – User’s without an admin account can now install the update from normal user account with the typical admin password prompt. This will be possible for all platforms except Win Vista where UAC has been disabled.
Hope the insight in to the new Adobe Updater is useful and provides some information on what we are planning for the next revision. Your comments and feedback are most welcome and we look forward to an healthy discussion and do any course correction if needed.
Updated: Based on the comments below, there have been three updates above. Two sections were added to clarify behavior (Scheduled Check for Updates and Non-Admin Users.) Further detail has been added to the preferences section as well. –Eric

CS4 Component Payload Descriptions, Windows Version

Last week I posted the Mac version of what each payload meant in the cS4 Master Collection installer. Mac was chosen because the vast majority of comments here and email to me on this subject were from Mac users. Since then I’ve received a few requests for the Windows version. So today’s post is the Win version. They are mostly identical, though there are approximately 20 additional payloads on the Windows side. I’ve repeated information for payloads that are on both Mac and Windows.
Acrobatcom-fr_FR – This payload is a dummy payload that really deploys nothing. It is used in order to conform to French legal rules that all components sold in France must be able to display using the French language. Since Acrobat.com was not localized to French in CS4, we could not install nor support that component in French installations. No point product features will break if this payload is not deployed.
Acrobatcom-mul – This is the payload for deploying the Acrobat.com feature set for all supported languages.
AdobeAcrobat9-cs_CZ – This is the core payload for Acrobat 9 Pro for Czechoslovakian, Hungarian and Polish. Without this payload, Acrobat 9 will not be installed for the given locales. Note that the Mac Acrobat 9 Pro build has fewer locales supported and so only has a single, multilingual installer.
AdobeAcrobat9-es_ES – This is the core payload for Acrobat 9 Pro for Spanish (European), Spanish (Latin American), Italian, Dutch and Portuguese (European and Brazilian.) Without this payload, Acrobat 9 Pro will not be installed for the given locales. Note that the Mac Acrobat 9 Pro build has fewer locales supported and so only has a single, multilingual installer.
AdobeAcrobat9-fr_FR – This is the core payload for Acrobat 9 Pro for German, International English, US English, French (European) and French (Canadian.) Without this payload, Acrobat 9 Pro will not be installed for the given locales. Note that the Mac Acrobat 9 Pro build has fewer locales supported and so only has a single, multilingual installer.
AdobeAcrobat9-ja_JP – This is the core payload for Acrobat 9 Pro for Japanese. Without this payload, Acrobat 9 Pro will not be installed for the given locales. Note that the Mac Acrobat 9 Pro build has fewer locales supported and so only has a single, multilingual installer.
AdobeAcrobat9-ko_KR – This is the core payload for Acrobat 9 Pro for Korean. Without this payload, Acrobat 9 Pro will not be installed for the given locales. Note that the Mac Acrobat 9 Pro build has fewer locales supported and so only has a single, multilingual installer.
AdobeAcrobat9-ru_RU – This is the core payload for Acrobat 9 Pro for Romanian, Russian, Turkish and Ukranian. Without this payload, Acrobat 9 Pro will not be installed for the given locales. Note that the Mac Acrobat 9 Pro build has fewer locales supported and so only has a single, multilingual installer.
AdobeAcrobat9-sv_SE – This is the core payload for Acrobat 9 Pro for Danish, Finnish, Norwegian and Swedish. Without this payload, Acrobat 9 Pro will not be installed for the given locales. Note that the Mac Acrobat 9 Pro build has fewer locales supported and so only has a single, multilingual installer.
AdobeAcrobat9-zh_TW – This is the core payload for Acrobat 9 Pro for Traditional Chinese. Without this payload, Acrobat 9 Pro will not be installed for the given locales. Note that the Mac Acrobat 9 Pro build has fewer locales supported and so only has a single, multilingual installer.
AdobeAfterEffects9All – This is the core payload for After Effects 9. Without this payload, After Effects 9 will not be installed. It includes all languages supported by After Effects on the given media.
AdobeAfterEffects9PresetsAll – This payload contains specialized preference settings for After Effects 9. Without this payload After Effects 9 will not have all its presets loaded on the system at install time.
AdobeAfterEffects9ProtectedAll – There is some content for After Effects that must not be deployed and unencrypted without first verifying the serial number used for deployment is valid. This content generally includes royalty-bearing items such as codecs, mpeg encoders/decoders, etc. Without this protected content some primary workflows for After Effects 9 will not be supported. The installation technology will verify that a valid serial number is used.
AdobeAIR1.0 – The Adobe AIR Runtime 1.0 installer is wrapped by this payload. It actually executes the publicly available AIR Runtime 1.0 installer. Any and all behavior in the AIR installer will also occur when deploying this payload. Not deploying this payload will mean that no AIR-based products will function. AIR-based products in CS4 include only Acrobat.com and Adobe Media Player.
AdobeALMAnchorService2-mul – This payload is needed to support 32-bit point product provisioning. Without this payload the 32-bit products will not correctly serialize or activate. Products will then cease to execute. All products in the suite are 32-bit products. Only Photoshop has a 64-bit product in addition to the 32-bit Photoshop.
AdobeALMAnchorService2-mul-x64 – This payload is needed to support 64-bit point product provisioning. Without this payload the 64-bit products will not correctly serialize or activate. Products will then cease to execute. Only Photoshop has a 64-bit product in addition to the 32-bit Photoshop.
AdobeAmericanEnglishSpeechAnalysisModels1All – Data for speech analysis. Video and sound applications that use speech analysis will not support this feature without the data payload being deployed.
AdobeAMP-fr_FR – This payload is a dummy payload that really deploys nothing. It is used in order to conform to French legal rules that all components sold in France must be able to display using the French language. Since Adobe Media Player was not localized to French in CS4, we could not install nor support that component in French installations. No point product features will break if this payload is not deployed.
AdobeAMP-mul – This is the payload for deploying Adobe Media Player for all languages supported by AMP.
AdobeAssetServices4All – Not listed in toolkit list; but, required for Version Cue Server. This payload deploys a service that runs as a background process. It generates thumbnails and extracts metadata for the Version Cue Server. Without this payload the Version Cue functionality and the CSXS functionality will cease to function.
AdobeAUM6.0All – This deploys the Adobe Update Manager for all supported locales. Without this payload an end user is unable to seek or deploy updates automatically or through the Help menu.
AdobeBridge3All – The Adobe Bridge product installer.
AdobeCameraRaw5.0All – This payload deploys the camera raw plugin for Photoshop and Bridge. Provides the ability to manipulate still images and allows viewing and editing of camera-native format digital negatives. Without this payload the ability to read, write or edit camera raw data will cease to function.
AdobeCameraRaw5.0All-x64 – The 64-bit version of AdobeCameraRaw5.0All. This is required only for the 64-bit version of Photoshop.
AdobeCMaps2-mul – Character mapping tables, necessary for correct font behavior. This is required for most CS4 applications.
AdobeCMaps2-mul-x64 – The 64-bit version of AdobeCMaps2-mul. This is needed only for the 64-bit version of Photoshop.
AdobeColorCommonSetCMYK2-mul – Color profiles for CMYK color spaces. Required for some of the CS4 applications. Without this payload critical color profiles for the print production workflow will not be available and products supporting the print production workflow may cease to function properly.
AdobeColorCommonSetRGB2-mul – Color profiles for RGB color spaces. Required for many of the CS4 applications. Without this payload critical, common color profiles will not be available and products may cease to function properly.
AdobeColorEU_ExtraSettings2-mul – Extra color profiles for the European Union region. Required for Flash, Illustrator, InDesign and Photoshop.
AdobeColorJA_ExtraSettings2-mul – Extra color profiles for Japan. Required for Flash, Illustrator, InDesign and Photoshop.
AdobeColorNA_ExtraSettings2-mul – Extra color profiles for all regions outside of the European Union and Japan. Required for Flash, Illustrator, InDesign and Photoshop.
AdobeColorEU_Recommended2-mul – Recommended color profiles for the European Union region. Required for Flash, Illustrator, InDesign and Photoshop.
AdobeColorJA_ Recommended2-mul – Recommended color profiles for Japan. Required for Flash, Illustrator, InDesign and Photoshop.
AdobeColorNA_ Recommended2-mul – Recommended color profiles for all regions outside of the European Union and Japan. Required for Flash, Illustrator, InDesign and Photoshop.
AdobeColorPhotoshop2-mul – Color profiles specific to Photoshop. All other products do not use these color profiles in any way.
AdobeConnect-mul – Used to provide an in-application connection to Acrobat ConnectNow. Required for most products. Without this payload the ConnectNow feature set will not function in any supporting products (Illustrator, InDesign, InCopy, Photoshop, Dreamweaver, Flash Pro, Contribute, Fireworks.)
AdobeContribute5-mul – Payload for Adobe Contribute 5 product.
AdobeCSIAll – Creative Services Infrastructure payload. Utility used by CSXS and the Service Manager Extension and Adobe Drive for accessing CS4 online services embedded in CS4 applications. Without this payload CSXS, the Service Manager Extension and Adobe Drive will cease to function. Required by most products.
AdobeCSIx64All – The 64-bit version of AdobeCSIAll, needed only by the 64-bit version of Photoshop.
AdobeDefaultLanguage2-mul – Used to determine the default language in which to run for Bridge and Device Central.
AdobeDeviceCentral2-mul – Payload deploying the Device Central feature set.
AdobeDreamweaver10-mul – Payload deploying the Adobe Dreamweaver 10 product.
AdobeDriveAll – Payload deploying the Adobe Drive feature set. Without this payload the Adobe Drive feature set will cease to function.
AdobeDrivex64All – The 64-bit version of AdobeDrivex64All, needed only by the 64-bit version of Photoshop.
AdobeDynamicLinkSupport1All – Support for the Dynamic Link feature set in video and audio applications. Required for AfterEffects, Encore, Flash Pro, Premiere Pro and Soundbooth.
AdobeEncore4All – Payload deploying the Adobe Encore 4 product for all languages supported by the given media.
AdobeEncore4CodecsAll – There is some content for Encore that must not be deployed and unencrypted without first verifying the serial number used for deployment is valid. This content generally includes royalty-bearing items such as codecs. Without this protected content some primary workflows for Encore 9 will not be supported. The installation technology will verify that a valid serial number is used.
AdobeExtendScriptToolKit3.0.0All – Development and debugging tool for JavaScript scripts. Its easy-to-use built-in syntax checker identifies problem areas in your scripts and suggests solutions. Required for Flash, Illustrator and InDesign. Optional in other products.
AdobeExtensionManager2All – The Extension Manager application payload. Without this product workflows requiring extensions will not be available. Required for Fireworks and Dreamweaver. Optional for all other products. Available freely online from Adobe Exchange as well.
AdobeFireworks10All – Payload for Adobe Fireworks 10 product.
AdobeFlash10-en-ExtensionFL30 – Adobe Flash Lite extension for Flash Pro. Without this payload the Flash Lite workflows in Flash Pro will cease to function. English version.
AdobeFlash10-es-ExtensionFL30 – Adobe Flash Lite extension for Flash Pro. Without this payload the Flash Lite workflows in Flash Pro will cease to function. Spanish version.
AdobeFlash10-fr-ExtensionFL30 – FlashLite – Adobe Flash Lite extension for Flash Pro. Without this payload the Flash Lite workflows in Flash Pro will cease to function. French version.
AdobeFlash10-others-ExtensionFL30 – Adobe Flash Lite extension for Flash Pro. Without this payload the Flash Lite workflows in Flash Pro will cease to function. All other languages version.
AdobeFlash10-mul – Adobe Flash Pro 10 product installer.
AdobeFlash10-STI-en – Flash Player 10 plugin/extension, English version.
AdobeFlash10-STI-es – Flash Player 10 plugin/extension, Spanish version.
AdobeFlash10-STI-fr – Flash Player 10 plugin/extension, French version.
AdobeFlash10-STI-other – Flash Player 10 plugin/extension, all other languages version.
AdobeFlashPlayer10_axDbg_mul – A debug version of the Flash Player ActiveX plugin for use with Flash Pro to debug output from Flash Pro.
AdobeFlashPlayer10_plDbg_mul – A debug version of the Flash Player for use with Flash Pro to debug output from Flash Pro.
AdobeFontsAll – Collection of bundled Adobe fonts. Required for some CS4 Applications. InDesign will not execute without it. Optional for Photoshop.
AdobeFontsAllx64 – The 64-bit version of AdobeFontsAll so that 64-bit applications (in this case, only Photoshop) can also access fonts.
AdobeIllustrator14mul – Adobe Illustrator 14 product installer.
AdobeInDesign6AppBase-mul – Adobe InDesign 6 product installer.
AdobeInDesign6AppFSet-Japan – Adobe InDesign 6 product installer, Japan-specific resources. InDesign will not execute in Japanese without this payload installed.
AdobeInDesign6AppFSet-Roman – Adobe InDesign 6 product installer, Roman glyph-based languages resources. InDesign will not execute in all Roman-glyph based languages without this payload installed.
AdobeInDesign6CommonBase-mul – Adobe InDesign 6 product installer required payload. InDesign will not execute without this payload.
AdobeInDesign6IconHandler-mul – This payload only does very specific work to ensure the InDesign icons and bitmaps are properly used InDesign files on the system. Without this payload, InDesign files will have a generic icon when using the Explorer.
AdobeInDesign6IconHandler64-mul – The 64-bit system version of AdobeInDesign6IconHandler-mul. Without this payload, 64-bit systems will show generic icons for InDesign files.
AdobeLinguisticsAll – Spelling and hyphenation data files used by the linguistics library. Required for Contribute, Flash, Illustrator, InDesign and Photoshop. Without this payload core, text-based features will fail to function properly.
AdobeLinguisticsAll_x64 – The 64-bit version of AdobeLinguisticsAll, used only by Photoshop.
AdobeMasterCollection4-mul-trial – Data required for trial installations.
AdobeMotionPicture2-mul – Color profiles specific to After Effects workflows. Required for After Effects primary workflows to function properly.
AdobeOnLocation4All – Adobe On Location 4 product installer.
AdobeOutputModuleAll – Export functionality for many products. Without this payload the Export feature will fail to function properly in many products and will fail to function at all in After Effects.
AdobePDFL9-mul – PDF Library files for in-application support of the PDF format. Required by most CS4 applications. Without this payload PDF support will not be available in products.
AdobePDFL9-mul-x64 – The 64-bit version of AdovePDFL9-mul, used only by Photoshop.
AdobePDFSettings9-ja_JP – Utility for creating, editing and managing specialized PDF creation settings. Required for Flash Pro, Illustrator, InDesign and Photoshop. This is the Japan-specific version.
AdobePDFSettings9-mul – Utility for creating, editing and managing specialized PDF creation settings. Required for Flash Pro, Illustrator, InDesign and Photoshop.
AdobePhotoshop11-Core – The 32-bit Adobe Photoshop 11 product installer.
AdobePhotoshop11-Core_x64 – The 64-bit Adobe Photoshop 11 product installer.
AdobePhotoshop11-Support – Hardware accelerator payload required by Photoshop in order to execute. Without this payload Photoshop will not run properly on some platforms.
AdobePremierePro4AllM – Adobe Premiere Pro 4 product installer.
AdobePremierePro4FCAll – Functional content for Premiere Pro. Without this payload the functional content will not be deployed for Premiere Pro. Critical workflows will no longer be fully-features without this content.
AdobePremierePro4ProtectedAll – There is some content for Premiere Pro that must not be deployed and unencrypted without first verifying the serial number used for deployment is valid. This content generally includes royalty-bearing items such as codecs, mpeg encoders/decoders, etc. Without this protected content some primary workflows for Premiere Pro 4 will not be supported. The installation technology will verify that a valid serial number is used.
AdobeSearchforHelp-mul – In-application access to online help search service. This is required by most CS4 applications. Without this payload the help search functionality will not function in-application.
AdobeServiceManager-mul – Provides an in-application connection to your account with Adobe online services. Without this payload the CSXS functionality will cease to function.
AdobeSGM3-en_US – Adobe SING Glyphlet Manager. Used only with Traditional Chinese, Simplified Chinese, Japanese and Korean fonts in InDesign and InCopy. Without this payload users will be unable to view characters of these languages. Useful for the Arabic, Czechoslovakian, Danish, German, Greek, International English, US English, Spanish (European and Latin American), Finnish, French (European and Canadian), Hebrew, Hungarian, Italian, Norwegian, Polish, Portuguese (European and Brazilian), Romanian, Russian, Swedish, Turkish, and Ukranian versions of InDesign.
AdobeSGM3-ja_JP – Adobe SING Glyphlet Manager. Used only with Traditional Chinese, Simplified Chinese, Japanese and Korean versions of InDesign and InCopy. Without this payload users will be unable to view characters of these languages. Useful for the Japanese version of InDesign.
AdobeSGM3-ko_KR – Adobe SING Glyphlet Manager. Used only with Traditional Chinese, Simplified Chinese, Japanese and Korean versions of InDesign and InCopy. Without this payload users will be unable to view characters of these languages. Useful for the Korean version of InDesign.
AdobeSGM3-zh_TW – Adobe SING Glyphlet Manager. Used only with Traditional Chinese, Simplified Chinese, Japanese and Korean versions of InDesign and InCopy. Without this payload users will be unable to view characters of these languages. Useful for the Traditional Chinese version of InDesign.
AdobeSING2-mul – Smart Independent Glyphlets. Required for InDesign, InCopy and SING Glyphlet Manager. It provides management of Asian characters. SING is required for InDesign and InCopy in all languages to open and modify documents containing embedded asian glyphlets.
AdobeSoundbooth2All – Adobe Soundbooth 2 product installer.
AdobeSoundbooth2CodecsAll – There is some content for Soundbooth that must not be deployed and unencrypted without first verifying the serial number used for deployment is valid. This content generally includes royalty-bearing items such as codecs. Without this protected content some primary workflows for Soundbooth 2 will not be supported. The installation technology will verify that a valid serial number is used.
AdobeSuiteSharedConfiguration-mul – Flexible serialization and BridgeTalk group information are both contained in this payload. Without this payload the products will fail to activate and no longer execute.
AdobeTypeSupport9-mul – Type support required by most CS4 applications in order to accurately display fonts. Without this payload most applications will fail to execute.
AdobeTypeSupport9-mul-x64 – The 64-bit version of AdobeTypeSupport9-mul, used only by Photoshop.
AdobeVersionCue4All – Payload enabling Version Cue functionality. Optional in InDesign, Photoshop, Illustrator and Flash Pro. Without this payload Version Cue functionality will fail to execute.
AdobeVideoProfilesAE2-mul – Color profiles specific to After Effects.
AdobeVideoProfilesCS2-mul – Color profiles specific to video workflows in Photoshop. Video workflows in Photoshop will continue to work without these profiles; but, will not have useful color profiles available.
AdobeWinSoftLinguisticsPluginAll – A variant on AdobeLinguisticsAll specific for Middle Eastern, North African and Central European languages.
AdobeWinSoftLinguisticsPluginAll_x64 – The 64-bit version of AdobeWinSoftLinguisticsPluginAll, used only by Photoshop.
AdobeXMPPanelsAll – This payload installs the XMP metadata read/write/edit feature set in most point products. Without this payload none of the UI for supporting XMP metadata will be available. This payload is require for most products; but, optional for Soundbooth.
aifsdk-win – This payload includes the Adobe Pixel Bender toolkit, an IDE for working with the Pixel Bender image and video processing infrastructure.
AMEAdditionalExporter1All – The payload for the Adobe Media Exporter application extensions used with Flash Pro, Premiere Pro, and After Effects. Without this payload the Adobe Media Exporter will fail to execute.
AMECore1All – Payload continuing the Adobe Media Exporter application, used in common workflows with Flash Pro, Premiere Pro and After Effects.
AMEDolby1All – There is some content for the Adobe Media Encoder that must not be deployed and unencrypted without first verifying the serial number used for deployment is valid. This content generally includes royalty-bearing items such as codecs, mpeg decoders, etc. Without this protected content some workflows for the Adobe Media Encoder will not be supported. The installation technology will verify that a valid serial number is used.
AMEExporter1All – There is some content for the Adobe Media Encoder that must not be deployed and unencrypted without first verifying the serial number used for deployment is valid. This content generally includes royalty-bearing items such as codecs, mpeg decoders, etc. Without this protected content some workflows for the Adobe Media Encoder will not be supported. The installation technology will verify that a valid serial number is used.
AMEImporter1All – There is some content for the Adobe Media Encoder that must not be deployed and unencrypted without first verifying the serial number used for deployment is valid. This content generally includes royalty-bearing items such as codecs, mpeg encoders, etc. Without this protected content some workflows for the Adobe Media Encoder will not be supported. The installation technology will verify that a valid serial number is used.
kuler2.0-mul – The kuler CSXS extension payload. Without this extension point products should continue to function properly but without the kuler functionality.
MSXML6.0 – The MicroSoft XML Core Services module, used for MSXML support by most products in the suite.
Updated (May 26, 09): Updated a few typos and strings above.