Copy link to clipboard
Copied
Are you using VMware Horizon with Instant Clones with Adobe 2020 Classic installed on your master image? Do you also use App Volumes 4 (or later) with it? Do I have some good news for you. According to Adobe you have to install Acrobat on you master or gold image so if you actually have it installed as an app in App Volumes then youcan skip this. Do you run in to the problem where after you use the provisioning toolkit to serialize and supress registration on your install that your users still get the pop up to log in after you've pushed the image out? You need to go in to C:\Program Files (x86)\CloudVolumes\Agent\Config on your master image and create a folder called "Custom" (without the quotes) and then a folder called "app" (without the quotes) in that "Custom" folder. In the newly created "app" folder create a text file called Snapvol.cfg and save it. Once you save it it will be called Snapvol.cfg.txt, just remove the "hide extensions for known file types" in the folder options and delete the .txt after the .cfg. Now open the config file with a text editor and put this in:
# Adobe
exclude_path=\Program Files (x86)\Adobe
exclude_process_path=\Program Files (x86)\Adobe\Acrobat 2020\Acrobat
exclude_process_name=Acrobat.exe
Save the config file and do what you normally would do to push out a new snapshot to your users. I tore all my hair out trying to figure out the problem. Adobe tech support couldn't help, VMware tech support couldn't help, nothing...So in order to hopefully save your sanity this is for you.
Copy link to clipboard
Copied
Apparently you can't use App Volumes 4 to install Adobe as an application using volume licensing. This is a known issue with App Volumes 4 and later. This is the only way I was able to fix this.
Copy link to clipboard
Copied
Out of curiosity, do you have a link to any official statement (KB article, etc.) from Adobe regarding this? I am going through something similar with Acrobat 2017 and App Volumes 4. The way it manifests in our environment is that it will function perfectly for some period of time, then the user will randomly get the pop up to log in. I would like something a bit more official to present to my managers if I can find it. I have searched, and at least to this point have found nothing.
Copy link to clipboard
Copied
I can't apologize enough for not seeing this response as it's been over a year and I completely forgot I even poseted this. There was no official statement from them. That's just what I got from the tech at Adobe. As with most responses from them saying they don't support things they were probably blowing smoke up my a$$. I had a case open with them last year but they marked it resolved and told me they don't support it.
Copy link to clipboard
Copied
Drizzt-Do-Urden,
just to confirm, so this way you still appstacked Adobe using appvolume Ver 4 or higher and you create dthe folder structure and the config and it worked?
Thnaks
Copy link to clipboard
Copied
I apologize. I completely forgot I even posted this as it was a year ago almost to the day. No, I don't have it installed with App Volumes. It is installed on the master/gold image and the custom Snapvol.cfg file is also modified on the master/gold image. But something happens when any App packages are attached that if you don't have the programs that are intalled on the master image in the primary Snapvol or custom Snapvol config files then they break down somewhere. This just happened to be that it broke down when trying to register the serial number after using the PRTK tool to install it. After putting everything mentioned in my original post into the custom Snapvol.cfg file it works no problem and I have had no problems with that since I did it a year ago.