Skip to main content
Participant
December 18, 2024
Question

Upselling gets triggered, deployment of Adobe Reader on Microsoft RDS environments.

  • December 18, 2024
  • 2 replies
  • 689 views

Dear Sir or Madam

We are an IT service provider in the greater Zurich area and provide Adobe Reader for our end customers on our around 100 private cloud environments.

Unfortunately, we have been experiencing more and more problems in the past, which can currently only be controlled by switching off the update service. Unfortunately, we are not in a position to contain this, which is why I am contacting you with my request.

Our issue is that we are successfully providing the Free Adobe Reader and it is running so far. If a customer then “voluntarily” logs into Adobe Reader in the Adobe Cloud services, this can trigger the so-called upselling process, which then updates the software to Adobe Acrobat Pro on the entire terminal server environment without requiring administrative rights. As a result, users without a subscription will no longer be able to open PDF files overnight. We are not the only ones who find this procedure very unpleasant and we would like to curb it in the long term.

 

We use the Adobe Customization Wizard to adapt the installer using Transform Files, i wanted to attach the file to the inquiry, but .mst is not supported in the field - if you want that, pls give me a way to send that to you.

 

We also use a group policy for each end customer, which sets the following keys:

 

Unfortunately, all our measures do not prevent upselling. Worse still, once this has happened, it can no longer be rectified without stopping the update service for good.

 

We take the following steps to clean this up, but they don't work:
- We uninstall the software
- We clean up residues of the software with the Adobe Cleaner Tool
- We delete all files and directories under
o “C:\Program Files\Adobe”
o “C:\Program Files (x86)\Adobe”
o “C:\ProgramData\Adobe”
o “C:\Users\*USERNAME*\Appdata\Local\Adobe”
o “C:\Users\*USERNAME*\Appdata\Roaming\Adobe”
o “C:\Users\*USERNAME*\Appdata\LocalLow\Adobe”
- *USERNAME* signals to us here that we are really cleaning this up on an RDS environment for each user which takes a lot of time.

 

Hence our questions:
Can you please answer in as much detail as possible how we prevent this upselling process from being triggered without turning off the Adobe Update Service?
Can you please answer which RegKeys/folders/files need to be cleaned up so that the upselling does not start again IMMEDIATELY when the program is started for the user who triggered it?

Unfortunately, the problems are increasing and we don't really know how the best practice could work. Your documentation on the Internet has already been implemented. Various opinions in internet forums are contradictory and have little validity.

 

We would very much appreciate your support in this matter in order to remedy this in the long term.

greetings from switzerland, have a nice day!

 

2 replies

Participant
March 18, 2025

Running into this same issue. Breaking the MSI up in the Adobe Customization Tool, the "Suppress Sign in" option is greyed out...

S_S
Community Manager
Community Manager
April 24, 2025

Hi @thomas_5222,

 

Hope you are doing well. Sorry for the trouble.

 

You might want to check the given link for more info on how to prevent this: https://adobe.ly/4itt668.

Also, info around the customization wizard can be found here: https://adobe.ly/3EN8NCK

 

Let us know if this helps.


Regards,
Souvik.

RGour
Participating Frequently
December 23, 2024

Hi @RubenGarcia 

 

Could you please try creating the following key. It should restrict the users to upgrade to fully functional Acrobat when they log in in Reader with Adobe ID having paid subscription.

 

Registry path : - Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Adobe Acrobat\DC\FeatureLockDown

Key Name -  bShowUpgradePrompt

Key Type  - DWORD

Key Value - 0

Participant
January 24, 2025

Hi RGour and others

 

so i placed that Key and it doesn't seem to work.

 

I placed it at

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\Adobe Acrobat\DC\FeatureLockDown as you said but it doesn't help with the situation. Hexadecimal 0 is good there, right?

In our experimental enviroment based on Microsoft Server 2022 Terminalserver, upselling process already got triggered, our specific question is where to find the parameter that declares this upselling process. Once it got triggered, we clean all AppDatas of all users, reinstall and the same stuff happens again.

 

There must be a place that signals the "Acrobat Reader" to upgrade to Adobe Pro and on that exact location we want to prevent that by controlling it. So can somebody give us more advice about that?

 

Thanks a lot! I am ready to assist where i can, we need to get rid about that issue on our private cloud enviroments and this matter would be very helpful for others as well i think!