• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Succesful commands for Provisioning Tool(CS6/PC)

Engaged ,
Jun 14, 2012 Jun 14, 2012

Copy link to clipboard

Copied

Hi,

Have any of you guys had any luck using the Provisioning Tool to unserialize a CS6-installation?

If so - what was the command line you used?

We've tested various commands but none of them have been succesful.

Some gives the return code 1 and a single one gives the return code 0.

The one giving the return code 0 should work, but sadly it doesn't actually unserialize.

Our CS6-package is made using AAMEE and packed as a serialized install.

After the install we plan on unserializing the install, but have no luck doing so.

The reason for this procedure is bad experiences trying to serialize a trial install of CS5.5.

Kenneth

Views

6.4K

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Jun 20, 2012 Jun 20, 2012

Copy link to clipboard

Copied

Hi,

please confirm if you are using this commandline - "adobe_prtk --tool=UnSerialize --leid=Photoshop-CS6-Mac-GM [ --locale=en_US ]" to unserialize the CS6 product. use LEID of suite/product which you have used to create the AAMEE package.

please refer to these document for detailed information on PRTK usage for managing licenses.

http://www.adobe.com/devnet/creativesuite/enterprisedeployment/licensing-identifiers.html

http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/creativesuite/pdfs/AdobeProvisi...

if you still see an issue, please send across amt3.log and oobelib.log

It should be located at

/tmp/oobelib.log on OSX

and

%TEMP%\oobelib.log on Windows.

thanks,

Rahul | rbaiswar@adobe.com | Adobe Systems

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Jun 21, 2012 Jun 21, 2012

Copy link to clipboard

Copied

Hi,

First of all some basics about our procedure.

We deploy a serialized version of Master Collection packaged using AAMEE3.0.

Once successfully installed we run this command:

adobe_prtk --tool=UnSerialize --leid=MasterCollection-CS6-Win-GM

to unserialize Master Collection. This gives the return code 0 and leaves us with a trial version.

We then want to serialize to eg. Design & Web Premium - using the Provisioning Tool - and the Master Collection CS6 Install using this command:

adobe_prtk --tool=Serialize --leid=DesignWebSuitePremium-CS6-Win-GM --serial=xxxx-xxxx-xxxx-xxxx-xxxx-xxxx --adobeid=xxx@xxx.com

This gives the return code 0.

If we then use the Provisioning Tool to unserialize Design & Web Premium using this command:

adobe_prtk --tool=UnSerialize --leid=DesignWebSuitePremium-CS6-Win-GM

this gives the return code 6.

According to the oobelib.log this should be due to the LEID not being valid.

I don't have a clean oobelig.log and amt3.log at the moment, but could prepare one if you want to take a look at it.

Is it no longer possible to serialize to a different package using the Master Collection-install?

This procedure worked in CS5.5 where we use it today.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Engaged ,
Jun 25, 2012 Jun 25, 2012

Copy link to clipboard

Copied

LATEST

It seems that the current version of Provisioning Tool can't unserialize.

This should be fixed in a release later this year.

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines