Skip to main content
Known Participant
January 22, 2013
Question

Security Settings

  • January 22, 2013
  • 2 replies
  • 3042 views

Does anyone know how I can configure client's security settings in Acrobat via a centrally managed location?

I need to be able to set security settings so when users print to pdf the document has the security applied and the user didn't need to do anything.

Settings I'd like to configure on clients:

Adobe PDF - Security:

Restrict editing and printing of the document. A password will be required in order to change these permission setings.

pre-set the password

Prinint allowed: high resolution
Changes allowed: none

uncheck, enable copying of text, images and other content.

check, enable text access for screen reader devices andthe visually impaired

I would also like to set their printer preferences:

Default settings: standard

Adobe PDF Security: Use the last known security settings (which would be the above)

Adobe PDF output folder: prompt for adobe pdf filename

Adobe PDF page size: A4

check. view adobe pdf results

check, add document information

uncheck, rely on system fonts only; do not use document fonts

check, delete log files for successful jobs

check, ask to replace existing pdf file

Thank you

This topic has been closed for replies.

2 replies

EnterpriseHelp
Inspiring
January 22, 2013

Hi,

The regshot method is not dodgy at all. There are thousands of settings and not all are documented. Also, Distiller and the PDFPrinter are products in their own right. So the question is what's supported: Basically, changing most settings you have the right to change is supported, GPO is supported, etc. Another thing that's supported (I should have mentioned above) is to use the Customization Wizard and set your printing options there.

What admins do in an enterprise settings is read the Admin Guide, the Wizard Guide, and the Preference Reference (500+ documented prefs). Then if the setting is not documented, they do what I described above.

LiveCycle is a digital rights management solution. If you want to protect, control, and audit your docs, then use LC or another solution.

I'm looking into  the password question, but I'm 95% sure you can't do that as the mass deployment of passwords defeats their purpose. You might consider looking at certificate security methods.

Ben

EnterpriseHelp
Inspiring
January 22, 2013

I'm going to assume you only need to know about the first part of your question (configure settings) and that you know the "central location" part (GPO, scripts, or any other preference propagation method).

Start with the ETK to learn about preferences generally: www.adobe.com/go/acrobatetk.

Then (since all those settings aren't documented), do the following:

  1. Get regshot.
  2. Close all apps.
  3. Open Acrobat.
  4. Take a regshot snapshot.
  5. Configure all the settings you need.
  6. Close Acrobat.
  7. Take another snapshot.
  8. See what's changed. Those are the settings you want.

I don't think you can preset a password however. I think that's stored in an acrodata file. You could try copying that file to other machines, but I haven't tried it and my first thought is it's not possible.

hth,

Ben

Known Participant
January 22, 2013

Thanks for the reply,

Using the regshot method seems really dodgy, why is there no support for this kind of thing? what are people expected to do in a corporate/enterprise environment?

If I set all the security settings and copy the acrodata from that PC and copy it to another, the security settings copy over but the password does not. I really need this to be as non interuptive as possible, I can't be annoying our users and stopping them from working. That's why I need to do it via a GPO or some such way.

I really don't get that Adobe has no support for this, this seems like such a normal thing that everyone in an enterprise environment would do.

On another note, does the extension for Livecycle do anything like I described in my original post?

Thanks

EnterpriseHelp
Inspiring
January 22, 2013

The password answer: No. Document passwords are stored in the document. They must be created on a per document basis.