Skip to main content
Participant
January 20, 2025
Question

Acrobat Pro in shared MS Azure VDI

  • January 20, 2025
  • 1 reply
  • 561 views

Hi, all.
I've a question for you as per subject.

We have a customer which uses 2 balanced shared VDI in Azure, for 15 of its users (2 of them, except the above, have a dedicated VDI, with no problem).
Among these 15 users, 4 of them need to use Acrobat Pro (the rest of them need to use Reader). Another user with this need is one of the ones with dedicated VDI
We bought 5 license of Acrobat Pro and, for the one with dedicated VDI, we had no problems: he accessed, system downloaded setup file that installed Creative Cloud and then it opened Acrobat (previously Readr) as Pro.
So we tried the same with the first of the users with shared VDI: access, download of setup.exe and installation: in this case, since user isn't admin (differently from the 2 with dedicated VM), it asked for credentials we correctl y gave. Then it installed CC but, when it came to open Acrobat, it still was Reader, even with the user logged. We almost tired eveything (disconnect the user, reconnect, close completely the session) with no luck.
Anyone with this scenario? Any suggestion?
Thanks in advance!

1 reply

Meenakshi Negi
Community Manager
Community Manager
January 21, 2025

Hi CapMarvelJr,

 

Thank you for reaching out.

 

Please refer to the information on the following help documents:

https://adobe.ly/4h4UAPz

https://adobe.ly/4h4UCHb.

 

If this does not help, please contact the support team via the admin console, using the steps suggested in the following help document: https://adobe.ly/4h4UEih

 

Thanks,

Meenakshi

Participant
January 25, 2025

Hi, @Meenakshi Negi 
Thanks a lot for your reply and please excuse the delay.

I'll take a better look to the links you gave (at the moment, I'm in a little holiday) but, at first glance, it seems even too much for our purpouses (we only need to use both Acorbat Pro and Acrobat Reader on same shared VDIs depending from the user).
At least, I'll contact support team.

thanks a lot again!