Adobe DC 2017 package for macOS 10.15 (Catalina)

[nl-fm its nla83276705]

We are trying to make a package of Adobe DC 2017 (64 bits) for macOS 10.15 with the Customization wizard version 17.009.20044(1) and we have We have a volume License for Acrobat Professional 2017 (MAC).

This works oke when we leave the Check the Grant Offline Exception & Disable Registration open, but we dont want our users to log into so this checmark has to be on, but we get an error.

We also tried later with the CC Package Launcher, but then the Adobe Creative Could gets installed and and there is a need to login aswell, which we dont want.

[victorr27984024]

Dear Colleagues,

we're experiencing the same error. We have a legacy ETLA subscription until December 2022 and are unable to repackage Acrobat 2017 Classic as well. Have you gotten any reply?
Thank you in advance!

Best regards

Victor

[Bani Verma]

Hi there, 

Are you trying to disable the sign-in option? then you need to uncheck the grant offline access option during the package creation process. Please refer to the articles:
https://helpx.adobe.com/creative-cloud/kb/disable-adobe-sign-in-launching-acrobat-dc-with-creative-c...
https://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/whatsnewdc.html#license-types

https://community.adobe.com/t5/enterprise-teams/acrobat-dc-2017-quot-sign-in-required-quot/td-p/9389...

Hope this helps.

[victorr27984024 · Accepted solution]

Thank you very much, but in the meantime, I've been to able to solve the problem through the following steps:

1.) Downloading the newest full version of Acrobat 2017 Pro: https://helpx.adobe.com/de/download-install/kb/acrobat-2017-downloads.html

2.) Downloading the newest Acrobat Customization Tool from here: https://www.adobe.com/devnet-docs/acrobatetk/tools/Wizard/basics.html

3.) Customizing the Acrobat installation package under macOS 10.13.6 High Sierra

Because we are a public university, we have to strictly adhere to our state's privacy and employee's rights laws and having a personalized Adobe ID for each employee is absolutely out of question.

Best regards

Victor

[Bani Verma]

Thank you, Victor, for sharing the steps that helped you resolve the issue. This will surely help other community members who might be facing a similar issue.