Copy link to clipboard
Copied
Hello,
I have been tasked with deploying Adobe Acrobat DC (Named License) to 400 machines throughout our offices. We are going to be upgrading to Windows 10 this year so I would like to install the program on one machine and deploy using our imaging software. i downloaded the CCP file and "customized" the install. Once distributed, Adobe Acrobat DC asks the user to login via an Adobe login and they must create an account and I also need to assign them a license inside of the Adobe Admin Console. Doing this for 400 users is not going to be a fun task on long with the other things needed to get users upgraded to Win10. If this is the only way to deploy this software that is absurd and they need to figure out a better way to do this. From what I have been told, the only way to install with a .MST file is to use a serialized version of Adobe which is out fo the question since it is 4x the price of the named license. if anyone has any insight on this that would be great.
-Ben
Hi,
You can deploy named-user Acrobat with an MST file, however if you don't have a serial number you obviously can't serialize it. If you are using the Creative Cloud Packager you can build a named user package including Acrobat. If you dig down in the Build folder you will find the APRO15.0 folder and ultimately the AcroPro.msi file. You can open that MSI in Customization Wizard in the normal way to create an mst. Deploy Adobe Acrobat XI or DC
If you are including other applications within the
...Copy link to clipboard
Copied
Hi,
You can deploy named-user Acrobat with an MST file, however if you don't have a serial number you obviously can't serialize it. If you are using the Creative Cloud Packager you can build a named user package including Acrobat. If you dig down in the Build folder you will find the APRO15.0 folder and ultimately the AcroPro.msi file. You can open that MSI in Customization Wizard in the normal way to create an mst. Deploy Adobe Acrobat XI or DC
If you are including other applications within the package then use the setup.exe from the Build folder, as this will also install Acrobat. If you prefer to use the MSI then you will need to run the build MSI separately from the Acrobat MSI.
When adding your users to the Admin Console you will probably find it easiest to batch import them using a CSV. Manage users in Adobe Enterprise deployments
Hope that helps.
Copy link to clipboard
Copied
Ok that's helpful. Will the users still be required to setup an Adobe ID and Password?
Copy link to clipboard
Copied
If you have an Enterprise ETLA and are using the Admin Console, you do have the option of using Federated ID (for Single Sign-On) or Enterprise ID. Manage identity types in Adobe enterprise offerings
Otherwise Adobe ID will be the type used. The users don't have to set it up in advance. When you give them product entitlement on the Admin Console they will be sent an invitation. They simply click a link in that invitation and will be invited to create a password if they don't have one, and they are good to go. Accept an invitation to join Creative Cloud for teams or enterprise membership
Copy link to clipboard
Copied
You can also download Adobe Built customized packages for individual apps in the Admin Console. These packages are meant to work with user based licenses, and you can edit some details before building the package.
Find more inspiration, events, and resources on the new Adobe Community
Explore Now