We successfully installed Adobe Acrobat DC on our users machines with a serialized license, however they are not allowed to use all of the features such as 'send for signature'.

[Guest]

We have deployed Adobe DC by creating a package installer using Adobe CC package installer. When we created the file, we selected only Adobe DC, and used a serialize license with our Adobe CC license number.

The program installs successfully and does not require a user to sign in. But, when our users create a document and try to use 'send for signature', they are first asked to sign in. So, they sign in using their own personal adobe ID, because we use Serialize Licensing in our environment. Then after they sign in, they are asked to 'upgrade' their account and pay for an Acrobat Pro DC subscription. But, we already deployed a licensed copy on their machine. 

Please advise on what might be the issue and how we can resolve this.

[EnterpriseHelp]

I think you need to customize the installer so that these items are removed from the UI. See the admin guide for an overview and the Wizard guide for details about customizing installs.

You can also use both docs to get the reg keys you can propagate if you don't want to reinstall.

Acrobat-Reader Enterprise Toolkit Home

HTH,

Ben

[Guest]

We will WANT our users to be able to use items/added features such as 'send for signature'. We do not want to remove them. It is part of Adobe DC we which have licensing for, so it does make sense as to why our users can not use it. It don't believe the documentation say anything about Adobe DC requiring a 'named license' in order for users in an enterprise environment to use the full features of DC, but I am worried that it looks like that is the only way it will work.