I'm trying to setup Adobe CC 2018 on an app stack. I have been able to capture the application on a stack fine. The challenge I have is to capture the actions of accepting the license agreement and to logon to the adobe cloud for licensing using UEM.
Here is what happens:
User logs on > Opens a component of CC > users is asked to accept the license agreement then user is asked to logon to the cloud for the license. User logs off > vm gets deleted/rebuilt (Persistent Instant Clone) > User logs on > Opens a component of CC > user is asked to accept the license agreement then user is asked to logon to the cloud for the license.
Has anyone figure out a way to address this with UEM?
App Vols. 184.108.40.206
Upgrading soon to
App Vols. 2.14
Not a solution but more of a "I feel your pain" kinda comment.
We have the exact same issue and are using writables with profiles so all info is stored.
For as far as I can see Adobe checks both user name and computer name when activating a license. Because you always end up on a different computer it will ask for credentials and license acceptance over and over again.
Unfortunately our users want to keep using Adobe. The way they handle licenses if it was me we would have parted ways with them already. They should also, apart form the user logon, create a concurrent licensing model with a flexlm engine. This way businesses can setup licensing for Adobe in a normal way... I don;t think any profile management tool can fix this issue on a VDI environment.
We had a similar issue with the licensing of Visual Studio Express. Even though it is free, MS creates a license key using the S-ID of the pc it is installed on. We use non-persistent linked clones and AppVolumes, so this was a nightmare getting it to work in AppVolumes. Our solution was to actually capture the AppVolume of VSE on the root image of the Instant Clone pool. As long as you only apply the AppVolume to that one desktop pool it works.
Not sure if that would solve the issue with the Adobe CC, but it should eliminate the constant changing of the computer ID if that is the issue.
hmmm where did I see that one .
We had the exact same issue wuth Visual Studio Express.. A free tool that has licensing issues . Go Figure..
But unfortunately no, it will not fix it. Problem is that if you have named user licenses, it will be activated when the user starts it up so you can't sequence that process..
Are you capturing the Appdata for the CC product? I went through this with Acrobat. Once I had the correct license that works with a non-persistent VDI environment. According to Adobes documentation as far as Acrobat is concerned it saves the licensing in the roaming Appdata.
Can't speak exactly to the CC from Adobe, but I would imagine their products would work in a similar fashion.
I have fixed this with the following settings on tab "Personalization":
Then on the Import / export tab:
After above settings go to tab "directflex" (if you want to use directflex)
Enable with the following executable:
C:\Program Files (x86)\Adobe\Adobe Creative Cloud\ACC\Creative Cloud.exe
We did try your suggestion as we are trying to capture as much info as we can within UEM regarding applications, unfortunately no go with this setting.
Not only that, we had a zip file of over 200MB being created after starting up a few applications in the CC suite.
But to be honest it also doesn't work with our writable which is still almost catch all. I guess we need to be looking at Adobe for some answers or a decent licensing program
What about this one:
Persisten or non-persistent can be serialised or NUL:
Pre-reqs User profile data in
<user>/appdata/Roaming as well as the HKCU hive must sync to the VM instance on which the user logs in.:
I went through this article and ended up going a bit "Old School" I used a UEM logoff task that simple follows this links instructions.
I created a CMD file to just run at logoff that renames and deletes the files for the user. So far so good.