Adobe_prtk Download For Mac

Got Munki?Want Adobe CS5.5? Read on.

  • Bestand,adobeprtk.exe in Windows of adobeprtk in Mac OS. Adobe Provisioning Toolkit Enterprise Edition Syntaxis voor Creative Suite 6 3 De toolkit bevat opdrachten waarmee u het volgende kunt doen.
  • In the past, Mac administrators have used the Casper Suite together with Adobe technologies to administer Acrobat Pro in the enterprise. Similar workflows can now be used to administer Acrobat.
  • Find solutions to the following Adobe Creative Cloud installation log error: 'Exit Code: 14 - Failed due to insufficient privileges'.
  • Adobeprtk.exe in Windows or adobeprtk in Mac OS. The toolkit contains commands to: serialize or unserialize previously deployed products perform other actions such as generating request code and accepting response code to complete offline activation (for Creative Suite 6).

Using the AAMEE, it is possible to make onebig fat installer .pkg that will install of CS5.5,fully patched and serialized. Unfortunately, at present the Munkitools aren't capable of delineating the original Adobe installs from the updatepackage created by doing it this way.

Therefore, it's necessary to make fourpackages:

1) A package for the Adobe licensing tool
2) The CS5.5 Design Premium install
3) A recent updater package
4) A package that serializes the machine with a serial number of your choosing(this way we can share the software without handing out licensing information).

The Sassafras ashbuilderis handy for step 4 if you use the Sassafras Key Client (http://www.sassafras.com/tools/ashbuilder.html)

It's relatively simple, especially with thefantastic munki server.

Creating the Adobe licensing tool install pkg (APTEE):

Create a separate transcript for the LaunchDaemon + shell script combo. Configure the command file to include excludes for the license locations. I ended up switching to using the AAMEE tool to create serialization files instead of using the adobeprtk tool. As of July 2010, Reader update installers on the Reader Download Center for Tier 1 are chained by default. If you are downloading the product from the RDC rather than the FTP site, just download the latest file and you’ll get all patches in one file. Mac: adobeprtk. DC Consumer track. (which specifies the 'adobeprtk' install item (-i), and its' destination (-d) will be / usr /local/bin) Upload the. Dmg into your Munki repo. Be sure to click options and upload the accompanying pkginfo.plist from the above step. Remember to edit your pkginfo.plist to include version info, a description and a good bundle name.; Creating the CS5.5 Design Premium install.

  1. Download this
  2. Fix the .dmg made by morons at Adobe so the 'adobe_prtk' CLI binary is in the root of the .dmg

3.Make a pkginfo file for this .dmg byrunning:

(whichspecifies the 'adobe_prtk' install item (-i), and its' destination (-d) will be /usr/local/bin)

  1. Upload the .dmg into your Munki repo. Be sure to click options and upload the accompanying pkginfo.plist from the above step. Remember to edit your pkginfo.plist to include version info, a description and a good bundle name.

Creating the CS5.5 Design Premium install:

  1. Get the Mac AAMEE kit here. Install it. Get your original Adobe CS5.5 install media mounted.
  2. Run the AAMEE, create a new pkg, name it appropriately and point the tool at your install media (it's locale matches the your serial number, right? See notes at bottom!!)
  3. Disable all popups, surveys, EULA agreements, updating, Adobe AIR, surveys. DISABLE EVERYTHING, OKAY?
  4. Do not download, or include updates.
  5. Read that last line again.
  6. Don't include a serial number (you can, at this point, but in order to provide shared/federated packages it's best to not serialize the software). We take care of that in the last step, anyhow.
  7. Edit the info.plist to get descriptive info for the Munki server
  8. Plop the resulting install and uninstall .pkgs into .dmgs, (in the root of the .dmg). Just the install.pkg into one, and the uninstall.pkg into another different one. Nothing else.
  9. Upload to Munki server and make sure both are of 'Installer Type': AdobeCS5AAMEEPackage

10.You'll likely have to make reliable installs keys (theapp paths/versions, for example - the installer will not make a receipt). Thisis a bit of an art form, as not all CS5 install variants are the same! If youfail to get this right, managedsoftwareupdate willcontinue to try and install CS5 every time it runs. You NEED to get this right(See the notes).

Creating the CS5.5 Update package:

  1. Start the AAMEE kit again.
  2. Make a new update pkg
  3. Include all updates
  4. Wait
  5. Edit the info.plist to get descriptive info for the Munki server
  6. Plop the resulting install .pkg into .dmg, (in the root of the .dmg).
  7. Upload to Munki server and make sure both are of 'Installer Type': Package
  8. You can use the receipts key reliably (ca.sfu.CS5_5DesignPremium-5.5-updates).
  9. Make this pkg an update for the CS5.5 Design Premium install package

Creating the CS5.5 Design Premium 'serializer'package:

  1. Know how to make a payload-free package? Make one. If you don't, feel free to use Greg's template.
  2. Find out:
    1. your serial number (it's locale matches the install media you used above, right? See notes at bottom)
    2. your package LEID (internal to Adobe. Look it up here)

3.Edit the postinstall script with contents:

Adobe prtk download
  1. Make sure the postinstall script is executable
  2. Plop the resulting install .pkg into .dmg, (in the root of the .dmg).
  3. Upload to Munki server and make sure both are of 'Installer Type': Package
  4. You can use the receipts key reliably.
  5. Make the 'CS5.5 Design Premium install' package a requirement for the install.

Deploy:

Bundle the software together in MunkiServer.

Prtk Download

You should also include the 'Java for OSX 2012-003' package for Lion clients that don't necessarily ship withJava. Dreamweaver and Flash will ask forit on first run.

Assign to your unit/group/department/client

Caveats:

  • Using the local Adobe uninstall app, or installing the AAMEE uninstall pkg will leave the pkgreciept for the updates pkg on workstations. If you manually remove the suite, be sure to delete the 'ca.sfu.CS5_5DesignPremium-5.5-updates' receipt.

·The command toUN-serialize the machine is:

(I might make aun-serialize pkg. Then again I might not. YMMV).

  • It is recommended to disable update checking in your base installer, but ultimately this is up to you.

NOTES:

*** It's really important to make sure what localeyou're dealing with when managing Adobe products. If your installer .pkg is made with en_GB(International English), you cannot register it with aen_US (Universal English) serial. Or vice versa.

Munki installs keys:

Installs keys aren’t necessarily the bestway, but they are the most exact. If you get a basic CS5 suite installed, youwill shortly be updating the suite with an update package. So your updater willthrow the versions off for the installs keys you’ve set in the base package.Not good. You’ll get repeated installs forever. The package receipt is anothergood option:

Receipts:

Combined with a couple reliable installs keysshould be sufficient. Your mileage may vary!

Installs:

More information:

http://code.google.com/p/munki/wiki/MunkiAndAdobeCS5

http://afp548.com/mediawiki/index.php/Munki_and_Adobe_CS5_deployment#Licensing_postflight_pkginfo

Adobe enterprise deployment tools, manualsand downloads:

http://www.adobe.com/devnet/creativesuite/enterprisedeployment.html

Adobe package IDs for the PRTK serializer tool:

Adobe_prtk Download For Mac Windows 10

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

Greg's easy payload free package template (usefulfor tonsof things):

http://managingosx.wordpress.com/2010/02/18/payload-free-package-template

To reserialize Acrobat with a different serial number using the Adobe Provisioning Toolkit Enterprise Edition (APTEE) tool.
  • Acrobat DC
  • Acrobat Classic 2017
  • Acrobat Classic 2015

Follow the steps below to reserialize Acrobat with a different serial number using the APTEE tool (Adobe Provisioning Toolkit Enterprise Edition):

  1. Win
    Download the zip file and extract the Adobe_Provisioning_Toolkit_10_0_ALL.exe file.

    Mac
    Download the zip file and extract the Adobe_Provisioning_Toolkit_10_0_ALL.dmg file.

  2. Open the Command Prompt (Win) or Terminal (Mac) as Administrator, and navigate to the location of the PRTK tool.

  3. Create a prov.xml file using the new serial key. Run the following command with administrative privileges in Command Prompt (Windows) or Terminal (Mac):

    adobe_prtk --tool=VolumeSerialize --generate --serial=<new serial number> --leid=<Acrobat LEID> --regsuppress=ss --eulasuppress [--provfile=<Absolute path to prov.xml>]

  4. Unserialize the existing serial key using the following command:
    adobe_prtk --tool=UnSerialize --leid=<LEID> --deactivate --force [–removeSWTag]

    Note:

    The return code for this command may be 0 or 29.

    • Return code 0 - License is deactivated successfully.
    • Return code 29 - License is already deactivated on the machine. If a user launches Acrobat post serial expiry date, the serial license is deleted from the machine.
  5. Reserialize Acrobat using the newly created prov.xml file. Use the following command:

    adobe_prtk --tool=VolumeSerialize [--provfile=<Absolute path to prov.xml>] --stream

ProductWinMac
Acrobat DC (ETLA serial key) - To be used only in unserialize command
V7{}AcrobatETLA-12-Win-GMV7{}AcrobatETLA-12-Mac-GM
Acrobat DC (ETLA serial key)
V7{}AcrobatCont-12-Win-GMV7{}AcrobatCont-12-Mac-GM
Acrobat Classic 2017V7{}AcrobatESR-17-Win-GMV7{}AcrobatESR-17-Mac-GM
Acrobat Classic 2015V7{}AcrobatESR-12-Win-GM
V7{}AcrobatESR-12-Mac-GM

Adobe_prtk Download For Macbook Pro

More like this