We're a CC/Enterprise customer and just ran our first Windows deployment test (we use Symantec Ghost) and had some unexpected results when we tested the systems we imaged.
For the test, I built a lightweight MSI with the CC Packager that just included Acrobat XI and Photoshop CC. I created a batch file to first run the ExceptionDeployer.exe with the parameters --workflow=install --mode=pre --installLanguage=en_US. After that completed the batch ran the MSI built in packager and then the ExceptionsDeployer again in "post" mode.
On the imaged workstations, we discovered the following:
- If Photoshop was launched first, both programs would launch correctly (activated, no EULA, etc.)
- If Acrobat XI was launched first, it would exit a few seconds after the splash screen appeared. Further attempts to launch it would not even produce the splash screen. Then, when I launched Photoshop, it would demand an Adobe ID login.
- Running adobe_prtk on the system would fix all the activation and launch issues.
The batch file/installer worked perfectly on a test system I set up as an individual machine install. Any ideas why it's not holding up under a deployment?
Thanks for your quick reply. Does this mean that we need to launch Photoshop (or other point application) after imaging to activate/serialize each computer? This isn't much different than CS6 when we ran the serialization tool post-deployment. I was under the impression that if our prototype was successfully serialized that the serialization would "stick" on the imaged workstations.
Actually this issue was taken care off in CS6 Package created with AAMEE 3.1 but the license breaks down in CCP 1.3 if you image the machine and then deploy.
Only resolution is to run APTEE to reserialise the applications.