Skip to main content
R
robert_humphreys
Inspiring
September 7, 2012
Question

CS6 Build reverting to unlicensed on imaged machines.

  • September 7, 2012
  • 1 reply
  • 2533 views

Mac Environment, 10.6.8, 10.7.4, and 10.8.1   DeployStudio for Imaging Machines, current version.

I used the AAM 2.0.97 to create a "Build" of CS6 that has the serial and activation embedded per our corporate License.

I can "push" out the build to machines just fine.

The apps launch, and run no problem. I can update them on the Admin side as it should be. All is well.

So, I take one of the machines with CS6 and create a new "Build Image" with DeployStudio.

I wipe a machine and put the updated "Build" on it which now includes CS 5.5 AND CS6.

When I log onto the fresh machine as Admin and Launch Photoshop 6, I am greeted with a "Design Premium and Web Trial" box stating that I can continue to use this product in Trial mode for 32767 days, or, Buy now.

The CS 5.5 apps work fine. So it's something specific to CS6 and it's Activation/serialization/registration.

Something is going wrong. I have used this method for updating my base builds in CS2,3,4,5,5.5 It's always worked. I've always used DeployStudio for imaging my machines.

What am I missing in order to add CS6 to my "Build Image" to deploy to all new users?

I'm jsut using the defaults in AAM to create my CS6 Build, see screenshot.

    This topic has been closed for replies.

    1 reply

    Mylenium
    Mylenium
    Legend
    September 8, 2012

    CS6 applications in Creative Cloud unexpectedly revert to trial mode

    Mylenium

    R
    robert_humphreysAuthor
    Inspiring
    September 8, 2012

    Thanks for the reply, but that's not it, none of these apps are in Creative Cloud.

    I can't be expected to have to deactivate, close, relaunch, accept the license, close, relaunch, sign in with an Adobe ID, close, relaunch, license, and then run Every time i build a machine?

    What's the point of using the AAM to create a Build to push out to users then? There has to be a way to image up machines for deployment that keeps the serialization in tact. It worked in all the previous version is CS products.

    I guess i'm mostly "hoping" that your reply is not the corrrect answer. What about pushing out a Serialization File? DeployStudio can be scripted to run after a machine is built that installs the serial file. Anyone had any luck with that?

    Thanks for the reply though..

    M
    Manish-Sharma
    Inspiring
    September 8, 2012

    Have a look at

    http://helpx.adobe.com/creative-suite/kb/technical-support-boundaries-virtualized-or.html

    Check the Known issue sevtion and may help.

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices