Skip to content
This repository has been archived by the owner on Jun 13, 2023. It is now read-only.

Acrobat Reader DC GPO Policy #24

Open
onedererer opened this issue Feb 8, 2017 · 5 comments
Open

Acrobat Reader DC GPO Policy #24

onedererer opened this issue Feb 8, 2017 · 5 comments
Assignees
Labels

Comments

@onedererer
Copy link

Policy is incorrectly setting:

HKLM\SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockdown\cServices\bTogglePerfsSync

Proper registry key is

HKLM\SOFTWARE\Policies\Adobe\Acrobat Reader\DC\FeatureLockdown\cServices\bTogglePrefsSync

Confirmation of policy is here

Only way I could fix the policy is using Powershell to Remove-GPRegistryValue and then set it using the ADMX/L templates provided. Please let me know if you need additional information.

V/R

@iadgovuser1 iadgovuser1 added the bug label Feb 8, 2017
@iadgovuser1
Copy link
Contributor

Doh... it took me a while to see that typo. Set this policy to Not Configured for now and then let all your systems go through a Group Policy refresh. After that's done then copy in the new templates and enable the policy. I will fix this and upload new templates and GPO.

@iadgovuser1
Copy link
Contributor

iadgovuser1 commented Feb 10, 2017

@onedererer
Copy link
Author

Run a gpo report on the policy or use policy analyser. Both show the key coming back with the typo. I saw it was correct in the admx, the actual GPO is wrong. Not sure how that would happen.

@iadgovuser1
Copy link
Contributor

I'm guessing what happened was that the original template had the error when we exported the GPO. We fixed this typo a few months ago but never updated the exported GPO. I will export and upload with the new setting. In the meantime you should be able to configure the setting to Not Configured, then replace the current admx file if it isn't the correct one, and then configure the setting again.

@onedererer
Copy link
Author

Sadly, because the typo has been fixed, the setting is already set to Not Configued because its looking for the correct key, not the broken original one. The only way I could remove the setting from the existing policy was to use Remove-GPRegistryValue for that registry key on that policy.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants