Install Packages stop working after a period of time

[BatesIT]

We have to constantly create new installation packages because they stop working after several weeks. We create and download a package for a particular lab or classroom, for instance, we install it and that part works fine, but when we go back to use it again, because of we've added computers or upgraded computers, the installer doesn't work. There usually is no error, but the installer just stops running (it disappears and the process terminates without notice).  The problem with that besides the hours it takes to create and download a new package, is that we have to try and create an identical package to what we had before. Are we doing something wrong or is this by design?

[John T Smith]

Packager Links https://forums.adobe.com/thread/1586021

http://forums.adobe.com/community/download_install_setup/creative_suite_enterprise_deployment

[Pattie-F]

moving  to Creative Cloud Download & Install

[Jeffrey_A_Wright]

Moving this discussion to the Deployment for Creative Cloud Team, Enterprise, & CS forum.

[alisterblack]

How are you creating your packages? With Creative Cloud Packager?

Are you building named user or serialized packages?

[BatesIT]

Yes, we are creating the packages by running the Creative Cloud Packager and we are selecting "Serial Number License" as the License Type and entering the activation or license code.

[alisterblack]

Is it possible that users are trying to sign in via the Creative Cloud Desktop App and breaking the licensing? If you have not already done so you may want to turn off the desktop app in your packages.

[BatesIT]

Sorry it took so long to reply but I wanted to check my information first. I don't see how what you described would break the licensing but I have checked and the Creative Cloud Desktop App is not available to the users.

[Ric5]

It may be useful to look at the log files to see where the install is breaking. Here's the link with the locations: Troubleshoot install issues with log files | CS5, CS5.5, CS6

If you're building installers for Windows, I've gotten into the habit of changing /qn to /qb so I can at least get an idea of when and where it fails.

One more stupid thing that people (including this tech) sometimes forgets is to make sure there are no browsers or Adobe apps running during the install.

Good luck!

Ric