(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. Open the Command Prompt (Win) or Terminal (Mac) as Administrator, and navigate to the location of the PRTK tool. Create a prov.xml file using the new serial key. Run the following command with administrative privileges in Command Prompt (Windows) or Terminal (Mac).
MSI support¶
Adobe Acrobat and Adobe Reader installers are developed using standard Windows Installer technology and Microsoft Installer (MSI) commands were developed by Microsoft.
The required MSI version for DC is 3.1 or higher.
MSI best practices¶
MSI usage¶
Adobe has tested and supports the installation of Acrobat products using the command line. You can use command line methods to install software in many ways, such as typing commands at a command prompt or in a batch script. When using the bootstrapper, command line parameters can be sent to msiexec from within the Setup.ini as well as on the cmd line.
The syntax for msiexec is as follows:
MSI switches¶
For Microsoft documentation, see http://msdn.microsoft.com/en-us/library/Aa367988.
MSI properties¶
You can specify MSI properties at install time; for example, to set a company name or suppress rebooting. For a complete list, refer to Microsoft documentation.
Supported MSI properties¶
Unsupported MSI properties¶
Troubleshooting msiexec¶
When using msiexec, if you receive an “Incorrect command line parameters” error message, verify that: Adidas micoach app.
Note
For more information about msiexec options, refer to http://technet.microsoft.com/en-us/library/cc759262(WS.10).aspx#BKMK_Install.
Bootstrapper installation¶
The bootstrapper Setup.exe file uses setup.ini as its configuration file. As you customize the installer with the Wizard, the Setup.ini file automatically updates. The Setup.exe file uses Setup.ini as it’s configuration file. Before deployment, open Setup.ini, verify it contains all the properties you need, and edit it as neccessary.
Setup.ini contains two sections:
MST usage in Setup.ini
Command line examples¶
These examples demonstrate different ways to install Acrobat products using the command line. Keep in mind the following:
Note
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.
Listing installed updates¶
Occasionally, certain bugs or features may be impacted by a specific OS version. You can use a Windows utility to list installed Windows udpates.
After installing the utility, run the following:
Installing Acrobat 2019 with logging¶
The silent install below creates an install log. Note that IGNOREVCRT64 can only be used when the C++ x64 Runtime is not required.
Language selection¶
You can use the LANG_LIST property to specify languages. Specify both the language code and the language-specific MST:
For details, see Adobe Properties
Creating an AIP¶
To create an administrative installation for a customized installer, use /a and TRANSFORMS. For example, the following installs Acrobat Pro with an MST file created with the Customization Wizard:
To create an administrative installation for a major release installer and a patch, use /a and /p. For example, the following installs Acrobat Pro 10.0 with the 10.1.0 patch:
Note
It’s always a good idea to keep the files in the same directory and cd to that directory so that you can run the commands from there.
TRANSFORMS and .mst¶
Installer modifications created in the Customization Wizard are saved to an MST file. The MST must be referenced in the .ini file or on the command line. This example installs a customized version of Acrobat Professional, displays a basic user interface, and enables verbose logging.
Installing with an MST
LEIDs and post-install prtk usage¶
Once an ETLA serial is provided, the LEID changes for unserialized commands. For both tracks, it becomes
V7{}AcrobatETLA-12-Win-GM (on Windows) and V7{}AcrobatETLA-12-Mac-GM (on Macintosh). For example, you would use the “ESR” LEID version to initially serialize, and you would use the “ETLA” version to deactivate or perform any other action with the prtk utility.
Silent uninstalls¶
A silent removal runs without any dialog boxes to show the user that the removal is running. All products use the same command line and the same installer file for silent updates:
Note
You must include the braces in the command line. An MSI package name (e.g. AcroRead.msi) can be substituted for the Product Code. For Acrobat products, the Product Code is the GUID.
Browser integration¶
Pass either
ReaderBrowserIntegration or AcrobatBrowserIntegration to REMOVE when a product is already deployed and a subsequent deployment requires disabling browser integration. For example:
To re-enable Browser Integration, use ADDLOCAL:
Removing product features¶
Because Acrobat products support MSI technology, it is possible to the use the REMOVE property to uninstall any component as described in the Microsoft documentation: “The value of the REMOVE property is a list of features delimited by commas that are to be removed. The features must be present in the Feature column of the Feature table. Note that if you use REMOVE=ALL on the command line, the installer removes all features having an install level greater than 0. In this case, the installer does not remove features having an install level of 0. For more information about the install level of features see http://msdn.microsoft.com/en-us/library/windows/desktop/aa371194%28v=vs.85%29.aspx.”
Removing any feature via REMOVE that is not specifically identified as a unique component in the user interface during a custom install is not supported. Moreover, some components have subcomponents which don’t appear in the UI, and admins are advised to inspect the installer tables and test their installs prior to deployment.
The command line is in the form of:
Where
<Package.msi|ProductCode> is either the full path to the original MSI file or the ProductCode of this product.
APTEE example for DC products¶
For standalone Acrobat deployments which not part of a Creative Cloud packager install, download the Adobe Provisioning Toolkit Enterprise Edition (APTEE). The APTEE is a platform-specific executable file:
DC Consumer track¶
For more details, refer to the PRTK documentation.
Serialization; machine online¶
Use following PRTK command to serialize Acrobat with ETLA serial number:
Un-serialization; ETLA serial license; machine online¶
Note
Once an ETLA serial is provided, the LEID changes for unserialized commands. For both tracks, it becomes
V7{}AcrobatETLA-12-Win-GM (on Windows) and V7{}AcrobatETLA-12-Mac-GM (on Macintosh). For example, you would use the “ESR” LEID version to initially serialize, and you would use the “ETLA” version to deactivate or perform any other action with the prtk utility.
Un-serialization; Pro Subscription license; machine online¶Un-serialization; Standard Subscription license; machine online¶Replace an existing serial number¶Type 1 Exception; machine offline¶
The command to generate request code for both Windows and Mac is:
Type1 Exception; machine offline¶
The command to get an accept request code for both Windows and Mac is:
Type1 Exception; Un-serialize; machine offline¶Type 2 Exception; Command to generate prov.xml; machine offline¶Type 2 Exception; machine offline¶
On Windows and Mac, serialize Acrobat using the
prov.xml as follows:
Type 2 Exception: Un-serialize Acrobat¶Adobe_prtk Download For Mac Windows 7Command to suppress EULA¶DC Classic track¶Serialization; machine online¶
Use following PRTK command to serialize Acrobat with ETLA/Perpetual serial number:
Un-serialization; ETLA license; machine online¶Un-serialization : Continuous (Retail/Volume) license; machine online¶Un-serialization; Pro subscription license; machine online¶Un-serialization; Standard Subscription license; machine online¶Type 1 Exception; ; machine offline¶
Generate a request code with the following (both Win and Mac):
Type1 Exception; machine offline¶
Command to accept request code
Type1 Exception : Un-serialize (ETLA/Perpetual serial); machine offline¶Type 2 Exception; generate prov.xml; machine online¶Adobe Prtk ToolType 2 Exception; serialize Acrobat with prov.xml; machine offline¶Type 2 Exception; Un-serialize Acrobat; ETLA license¶Type 2 Exception; Un-serialize Acrobat; Continuous track & volume license¶Suppress EULA¶
Jan 18, 2013
A significant licensing bug has caused certain installs of CS6 software on Mac systems to begin prompting the Trial screen indicating that the software is no longer licensed but is now in Trial mode. Normally the trial period is for 30 days. But in this case, it states that the trial period is 32,767 days. Just a bit over 89 years. So imagine it is 2102. Your kids and grandkids have long since moved to Mars, but apparently you, the IT admin are still stuck on Earth dealing with the Adobe’s CS6 licensing issues! I joke. Why? Because this is particularly egregious and has been very disruptive for many production environments, school labs, etc. And we have been particularly slow to respond to this issue. I am not saying this as self criticism but rather as a simple fact.
Do we have a fix? Let me jump to the chase (for once) and then explain the root of the cause and explain why our response to this has been sloth-like.
How to resolve the 32767 Days Left licensing issue:
1) Apply the Mac Photoshop 13.0.4 update patch
2) Use AAMEE 3.1 to create a serialization file
3) Run serialization file on affected systems
Details on #1: Photoshop 13.0.4 is available via the Mac version of AAMEE 3.1 in the Update workflow. It can also be applied manually if updates are enabled. The Remote Update Manager (RUM) is also available to apply the updates on the system. The specific command line for this would be:
Adobe Prtk Download
RemoteUpdateManager –channelIds=AdobePhotoshopCS6-13.0
Details on #2 & #3: Adobe Provisioning Toolkit Enterprise Edition (APTEE) is the command line serialization tool that is included in the AAMEE 3.1 install. It is covered in detail on Chapter 9 of the Enterprise Deployment Guide.
Now, why did this happen and if it hasn’t happened to you why not? The pattern we have seen appears to point at the Photoshop 13.0.2 and 13.0.3 updates as they had impacts to the licensing database. This update caused a synchronization call to the serial entry that would basically cause that entry to become unusable. Therefore the product that had been licensed would switch to becoming trial. Except of course a trial time period is 30 days and these installs would of been past 30 days so it displays that ridiculous 32,767 message.
We initially provided guidance on the Enterprise Deployment forum to use APTEE to un-serialize and then serialize and this resolved the issue for some folks. Same for the suggestion that came up to just use the serialization executable workflow in AAMEE 3.1. But, of course this wasn’t a proper fix because the same synchronization call would occur and then break things. Again. Ugh.
So, what was needed was the Photoshop 13.0.4 update that came out this week to stop breaking things. Then use APTEE to un-serialize. Bam, clean slate. Then use APTEE to serialize. Why not use the serialization executable workflow in AAMEE 3.1? Good question. The guidance from our Engineering Director I got was to stick with the APTEE step of un-serialization. Easier/cleaner to write to a file/entry that wasn’t there vs. one that is and might have been corrupt. Makes sense.
Why weren’t we able to diagnose and provide better guidance in a proper manner is two-fold. We are dealing with licensing that is time and actual product usage based. One would be unable to take the exact same AAMEE produced package with the same volume serial number and reproduce the issue after an install. Trust me, we tried. No, the licensing mechanism we have created is now like a ninja. One that we trained. Then we told it to go out in the woods at night and not be seen by us. Then we had to go out there in the woods to find him. Guess what? Totally hard. I am not sure if that metaphor works but I really like the imagery of a ninja hiding in the woods laughing (silently of course) at me.
In addition we did not want to announce a fix widespread until we had actual validation from customers that this was working. Once again, not a fix that they could validate instantly with any confidence that it had “stuck.”
We have learned a lot from this whole thing and need to do a lot internally to make sure this doesn’t happen with another product update…ever! In the meantime, you are owed an apology for the impact this had on your organizations. We understand that these types of issues are not simply things that make Adobe look back, but if you are an IT admin who manages a lab and the lab stops working the precipitation is that it is your fault. I know this first hand. Many moons ago I managed labs at a college and then when I first came to Adobe ten years ago I maintained Adobe’s training classrooms. I know what it is like to see a classroom of frustrated students and worse an angry instructor rolling their eyes at me or even yelling at me. Not pretty.
I also want to thank the members of the IT community that helped on this by reaching out to us with detailed info of the issue, providing logs, helping us test and validate, etc. Special shout out to the Enterprise Deployment forum posts. This forum has a large visibility internally and issues that get many reports here turn into data that is seen by our executives on a real-time basis. I also want to thank those who reported the scale of the impact to your Adobe Account Executive or your Channel Reseller partner. It is important that you be heard through all these outlets and that we understand the inconvenience and pain this has caused you and your organization.
Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Digital Media | Adobe Systems
Adobe_prtk Download For Macbook Pro
Update 1: Please note that if you have systems that have not seen these issues then our recommendation is to simply make sure that you update the Photoshop 13.0.4. No need to unserialize and re-serialize if the PS 13.0.2 or 13.0.3 updates were not on the system. If you have an AAMEE 3.1 package with the PS 13.0.2 or 13.0.3 in it be sure to update the package to include 13.0.4.
Prtk Download
Update 2: This entry was changed to clarify that that 13.0.4 is for Mac systems only.
Update 3: For clarity instructions to resolve have been updated. No longer require un-serialize & reserialize. AAMEE 3.1 serialization file takes care of both.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2020
Categories |