Adobe updaters for Creative Suite products, CS5 and beyond, include a "mode=sassa" option that can recognize a keyed installation and update it correctly while preserving the keyed state.
The standard product updaters for Adobe CS5, CS5.5 and CS6 are "keyed-state-aware" – this means they will recognize a keyed installation and refuse to run while posting a dialog that says "Contact your KeyServer administrator...". However, Adobe has implemented a special "mode=sassa" option which when activated, causes the modified updater to correctly preserve the keyed state of the main executable.
Before proceeding, make sure your K2 Products database has the latest definitions for Adobe products – use the "Find Product Definitions" from the KeyConfigure Tasks menu.
1. Install the latest, updated, Adobe Product versions and set up KeyServer Policies to manage the keyed variant:
With a management Policy configured for one or more of the CS Products, verify that you have achieved the desired behavior when launching the keyed program.
In the next steps, you will modify the updater's behavior using Adobe's "--mode=sassa" option so the updater will still run even when encountering a keyed installations. Furthermore, when this modified updater is run on a computer where an unkeyed program version is installed, it will likewise be replaced by a keyed version!
Note: the steps below must be performed on a computer where step 1 was performed so that it that has the updated and keyed executable installed in the standard location.
2. Create a modifiable copy of the updater:
(as the "mode=sassa" option is applied, a message will confirm success while listing the updater payloads being modified)
3. Navigate within the modifiable mounted dmg or updater folder and activate the "sassa" option:
The next steps describe how to reconstruct a dmg (Mac) or zip (Win) that is exactly like the original in terms of structure, name, and contents but containing the "sassa" modified installer from above. It is important to make sure that the resulting updater has exactly the same file and folder structure (starting at the root level of the dmg or zip) as the original updater.
4. Reconstruct the product updater(s):
We now have an updater that will produce a keyed executable when run on a computer that has some previous version installed. Test the modified updater to verify its behavior and then make it available by whatever means is convenient for use on computers where keyed software is installed. Caution: this modified updater will also produce a keyed executable when run on a computer with an unkeyed older product version, so take care to manage where it is run.