![]() It's serialized, but it still wants an Adobe login to Register. But again, the problem is that every time any Adobe app is launched, it prompts the user to register. That is the only method I've tried that works. Casper copies the CS6 package to a temp location on the internal drive, then on first reboot/login (using internal boot drive), it installs the CS6 package. Boot target machine to external drive, launch Casper Imaging from external drive, choose the "CS6 Install" configuration, and image. Create a "CS6 Install" configuration in Casper Admin, and add the CS6 package to the configuration. Upload AMEE created package to Casper Admin, and check the "install on boot drive after imaging" option. The way I've been able to successfully distribute CS6 is this… Create package in AMEE 3.1, using the "ignore conflicts" option, and not installing any AIR-related pieces. So somehow the Casper process is breaking that "already registered" flag that is a major benefit of using AMEE. ![]() When I manually install on a machine (not using Casper) using the same AMEE package I uploaded into Casper Admin, the Adobe apps do not ask for Registration when launched. ![]() The product is serialized, but for some reason still wants registration. However, every time a CS6 app is launched, an Adobe prompt comes up for Adobe product registration by way of an Adobe login. ![]() After reading all of those threads, I was able to come up with a workflow that is successful in getting CS6 on the target machine and automatically serialized. I'm having an issue with Adobe CS6 that I haven't seen specifically mentioned in any of the numerous posts about CS6 distribution. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |