Skip to main content
L
larrys17047195
Participating Frequently
March 24, 2019
Answered

Adobe Reader 2017 Classic

  • March 24, 2019
  • 1 reply
  • 4360 views

Privileged Locations doesn't seem to work with this version as it did in reader 11.x

I have used the deployment wizard and put in the folder path, also tried file name

however each time the pdf file that I want opened on a file share it will give me the security warning

do you want to continue and I have to press allow

This worked great in reader 11 but not in reader 2017 dc classic

using the customization wizard

during reader install I can check the register and those entries are there but it doesn't work

This topic has been closed for replies.
Correct answer EnterpriseHelp

I can see why it could be confusing. You need a full exe (which are all MUI) and the latest update

OK, I didn't know what you just stated because I was comparing the "file names" that had the actual 'MUI'

in their name.

So it sounds like all I have to do is download the latest full exe (in my case 2019 DC continuous) and any .msp

patch to get it current, disable the updates using cust manager and all will be fine.  Our English users and Japanese users will the user interface they need.  I will also get the Japanese font pack for them if needed


As mentioned above, you have multiple options. You can get a single installer or a base + msp.

DC Continuous track is the preferred and Adobe recommended version. However, keep in mind that disabling updates with that track is possible but not recommended. If you are using services, you shouldn't. If you are not using services, disable both the product updater and services plugin updater. The doc explains it.

1 reply

T
Community Manager
Tariq AhmadCommunity Manager
Community Manager
April 11, 2019

Hi larrys,

Why are you using Reader 2017 classic?

Why don't you use Reader DC: Adobe - Adobe Acrobat Reader DC Distribution ​Also, have you tried to install the Reader 2017 with all updates available? If you set the location manually on a test machine under preference, do you still see this problem?

If you already have found an answer or workaround to this issue. Please update this discussion with your findings.

-Tariq Dar

L
larrys17047195Author
Participating Frequently
April 14, 2019

Hello,

I'm using 2017 classic DC because I want to be able to control the updating process, basically we do not want reader auto updating and that's the case for classic DC.  I've placed the links within adobe manually also and still get the security warning.  Reader 11 this worked fine.

I haven't tried installing the latest patch and will go ahead and do but these are generally security patches so I wouldn't think these would fix our issue.

I did use your link and download reader dc 2019 but doesn't this auto update?

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices