On Saturday, November 30th, 2019, all instances of serialized Adobe software will cease to operate. In preparation, individual users will need to be converted to the Named User License model, and shared devices will need to operate under the new Shared Device License model. Below you can find details, instructions, and tips and tricks.
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). 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.
Adobe software can be logged in to via two forms of authentication: the Adobe ID and the Federated ID. Adobe uses these terms to distinguish their traditional login from the PennKey SSO option. Each authentication method has its pros and cons, which are laid out below.
Adobe ID
The Adobe ID is the traditional email-and-password method of authentication. On end-user-facing products, this will be defined as the 'Personal Account.' When assigning named user licensed products to individual users, this is the form of authentication that is recommended. These accounts are more easily managed by local IT support providers at the schools and centers, who have a bit more control over the accounts.
Federated ID
The Federated ID is Adobe's terminology for integrated single sign-on (SSO) authentication -- in our case, PennKey. On end-user-facing products, this will be defined as the 'Enterprise Account.' To log in using a Federated ID, users will need to enter their username in the format of '[email protected]' on the Adobe login screen, at which point they will be prompted by a PennKey weblogin request.
ISC recommends that these accounts be used for faculty and staff who do not require an individual license, but rather, simply need to authenticate to gain access to shared devices. This is not typically recommended for use in situations where users will need to access a personal license, as they are more centrally managed, and local IT support providers will have less control over these accounts. For example, if you wished to remove a Federated ID account from your organization, the enterprise system administrator role is required to do that.
Users who were previously using serialized versions of Acrobat will need to be granted Named User licenses, in the form of Adobe IDs or Federated IDs, to access Acrobat going forward. To do so, follow the instructions below. Window managment app macos mojave free.
Manually Adding Named Users
Bulk-adding Users
In preparation, ISC will be available to assist with bulk-adding users to the Adobe console and assigning them Acrobat licenses. To request a bulk upload, simply fill out the linked CSV template with the information of the users you wish to have added, and send the completed CSV to Client Care.
Once we receive a CSV for your school or org, we will cross-reference with a report from the Adobe console, to determine which users already exist in the console and have an Acrobat or Creative Cloud license, and then add and assign licenses to the remaining users. This means that supplying a list of users that includes users who may already be assigned an Adobe license will not be an issue.
Adobe's new Shared Device License allows for IT support teams to create installer packages in the Adobe Admin Console that can be installed on devices that will be shared by multiple users. This license should be used in cases where multiple users will need to access Adobe software on the same machine, but where those users (in most cases) do not need to be granted access to Adobe software across multiple machines.
All serialized versions of Acrobat will need to be deserialized when support staff have prepared their users with named licenses.
Deserialize using the APTEE tool
Acrobat DC Classic vs Continuous
All versions of Acrobat DC Classic will need to be uninstalled, and replaced with Acrobat DC Continuous. Existing instances of Acrobat DC Continuous will not need to be uninstalled.
As part of our contract with Adobe, Penn IT staff have access to several modes of professional support from Adobe.
Escalation
Adobe_prtk Download For Mac Windows 10Adobe Enterprise Support
Adobe's Enterprise Support provides several options for obtaining support from Adobe.
As we learn and collect common technical or operational issues, as well as their solutions, we will update this section with any information we have.
Got Munki?Want Adobe CS5.5? Read on.
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: https://treegm508.weebly.com/blog/download-texmaker-45-mac.
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):
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)
Creating the CS5.5 Design Premium install:
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:
Creating the CS5.5 Design Premium 'serializer'package:
3.Edit the postinstall script with contents:
Deploy:
Bundle the software together in MunkiServer.
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:
(I might make aun-serialize pkg. Then again I might not. YMMV).
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: https://starbrown427.weebly.com/blog/download-ppsspp-for-pc-32-bit-windows-xp.
Adobe Prtk Download
Adobe lightroom cc download mac. Receipts:
Combined with a couple reliable installs keysshould be sufficient. Your mileage may vary!
Installs:
More information:
Prtk Password
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:
https://dnsclever815.weebly.com/blog/minecraft-pixelmon-mod-download-mac. http://www.adobe.com/devnet/creativesuite/enterprisedeployment.html
Adobe package IDs for the PRTK serializer tool:
http://www.adobe.com/devnet/creativesuite/enterprisedeployment/licensing-identifiers.html
Greg's easy payload free package template (usefulfor tonsof things):
Accessdata Prtk
http://managingosx.wordpress.com/2010/02/18/payload-free-package-template
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |