Can anyone confirm this? If so, I assume that this is more of a push towards named licensing on Adobe's end. Same error each time a user tries to launch Adobe.įrom what I have read, it seems that some serial deployments are being phased out, and it seems that with older versions of Adobe that use volume licensing are starting to run into this problem. To avoid negative consequences, it is very important to get it from legal sources. I thought I would re-create the Appvolume on a new 1909 VM for good measure using the same process documented in the Adobe article. Adobe CC 2017 is a complete set of applications and services you need for editing videos, photos, etc. When doing so, the users entitled to the Adobe AppVolume started calling regarding an error every time they would launch it: Roughly a year later, I am working on getting users moved over to a 1909 floating pool. The serialize deployment article is what we originally used to accomplish this and everything worked as expected: Our company has a paid volume license of Adobe Acrobat 2017 Pro DC that we originally used with AppVolumes 4 on a Windfloating pool. I figured for the sake of it, I would post in communities. I've been spinning my wheels for a while on this and have read around quite a bit to get an idea of other people's experience with it.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |