Premiere Elements 13 serialize Return Code = 14

[Guest]

I have 24 AOO licences of Premiere Elements 13 that I need to deploy with SCCM.

I have created an .msi with AAMEE as I was told by Adobe support. Next I tried to create a prov.xml with the following command:

adobe_prtk.exe --tool=VolumeSerialize --generate --serial=xxxx-xxxx-xxxx-xxxx-xxxx-xxxx --leid=V7{}PremiereElements-EMT13-Win-GM --regsuppress=ss --eulasuppress --provfilepath="path to desired folder"

I get Return Code = 14. I am running the command prompt as administrator. What have I done wrong?

[killebrewj]

I'd like to know what to do with this. I ran into the same problem, basically trying to force PSE13 and PRE13 silent installations the same way as 12 because I have no access to the new creative cloud packager. We purchased volume licensing for 12 which came with a version 13 upgrade and the only official directions I could find to build a silent installer require creative cloud packager which is nowhere to be found on our LWS page. What am I supposed to do?

[Guest]

We have no access to CCP either. It looks like that's only available to another licensing level.

I think the above might work if I had the right LEID. That's the only thing I'm not sure of. I could find no reference to it in the .msi. So I found the version 12 one and changed it to 13, hoping it would be right.

[killebrewj]

I did the same and I think we do have the right LEID because V7{}PhotoshopElements-13-Win-GM shows up in the log file at %temp%\AMT3.log.

[ErikR]

Found a solution to this?

Seems to be same "problem" with versions 14, so curious if the leid would be something like "V7{}PhotoshopElements-14-Win-GM" or if the version has changed etc.

We neither has access to that CCP util, so that seems not to be an option for us (and I also HATE everything with "cloud" in it), so just glad if I can find another, DECENT way, to deploy.

Br,

Ø.S.

[puneeta23771395]

Hi,

Error code 14 represents missing LEID for the product. LEID does not exist for Premiere elements 13 and that is the reason you are getting this error. Solution to this issue is you can create the package using creative cloud packager and deploy it.