AAMEE 3.0 Serialization. Lab deployment. Via clone/Ghost .Command Line issue

[sparkyhatton58]

Design and Web Prem Ver6

Lab Environment - University

Preferred Deployment method: Network deployment. Via image cloning.

Platform: Mac

Adobe Application Manager Enterprise Edition Deployment (version 3)

Description of problem:

I want to deploy CS6 Design Premium, by deploying disk images over a network. I have used this method in several previous versions. However now I am having problems.

After some investigation, I have discovered i need to use AMEE to create a serialised package of CS6 design Premium. (using above serial number) I have sucsessfully deployed/installed it to client Macs using Apple Remote Desktop.

However, after being cloned, the applications revert to trial status. I then attempted to create a serialisation executable too run on the client machines, using AAME. I successfully created the executable and the prov.xml. But now I am having issues getting it to work. I have tried to follow the instructions in your guide to no avail.

[K Gibson]

Hi

Have you viewed the Adobe TV video on this topic ? Please provide a detailed description of the issue with serialization if the video does not answer you question

http://tv.adobe.com/show/creative-suite-in-the-enterprise/

Cheers

Karl Gibson

[ValleyROP]

Karl,

Thanks for pointing us to these videos.  I have another question.

Wouldn't it be just as bad to have my "Serialization File" stolen as it would be to have someone take my serial number?

Its seem you/adobe have gone to great lengths to embed the serial number into a serialization file so I don't have to give it out.  But isn't the file just as risky to let out?  Am I missing something?

Thanks

Terry Hofer

[K Gibson]

ValleyROP,

Thank you for your comment, The reason for the "create serialization file" workflow in AAMEE is that it is something the community was asking for. It can be used in many different circumstances. For example when a customer is issued with an expiring serial number and wish to serialize again with a different serial. Also when user's download or wish to try and trial of the software they can do so and IT can then remotely serialize. We just wanted to give IT admins flexability and the tool is command line so it gives flexibility it is designed to be executed remotely not given to users. There is some circumstances where IT admins may wish to create a double click file so user's can execute it themselves but it is up to the IT admin to make sure this is secure whether that is by storing it on a secure server or configuring it to delete itself after execution again there is great flexibility provided and that at the end of the day is what we want to give the IT admin. Security is of course important to us and there is risks associated with the serialization file getting out into the wild but wouldn't it be worse not to give our user's such a valuable workflow.

Cheers

Karl Gibson

CS Enterprise Systems Engineer

[sparkyhatton58]

Great! Thanks Karl

I'm almost there, I have got it all working following your videos. However I have one last request. I have been attemting to run the script via ARD, but I'm having trouble. Can you advise me what I'm doing wrong as the command is failing using this method. This is what I'm sending out.

/Users/amdtech/Desktop/Serialization/CS6-Serialization/AdobeSerialization AdobeSerialization --tool=VolumeSerialize

Many thanks

Mark

[K Gibson]

Hi AMDTECHSTAFFS,

Glad the video prooved to be useful. The command

"AdobeSerialization --tool=VolumeSerialize --provfile=Absolute_Path_of_prov.xml" should be run on the client once you have copied the two files that AAMEE created onto the client machine. If both files are copied to the same location then you do not need to point to the location of the "prox.xml" file. so the command would just be "

"AdobeSerialization --tool=VolumeSerialize"

If this is still not working, then run the command locally from terminal and note the "exit code" the tool produces or alternitively send me the log files from the client the "oobelib.log" file is located in %temp%

E-mail kagibson@adobe.com

Cheers

Karl

CS Enterprise Systems Engineer