@jkaigler The package was corrupt but it is all good now in Jamf Admin. Still will not install on Mojave 14.2 out of Self Service. The package downloads OK, verifies, executes but results in a failure. The logs seem to indicate that it is a pathing issue. Anyone have Photoshop 2019 successfully installed on Mojave 14.2?
Many thanks
Joseph
I was able to package up the entire 2019 suite (from Adobe console) and distribute to test machines. I also have a script to uninstall all the 2018 apps and clear the way for 2019. These run fine.
Here is my issue (as expected). When I launch a 2019 CC app, I am prompted to log in (expected). I log in and do my thing... then purposely leave it logged in. Then I try to login as a new user and guess what... all the CC apps still show my login from the first account.
This after I asked the question of Adobe in the webinar as to how to deal with this... their answer was "each user session is self contained in the user profile and there is no need to log off".
Anyone have a solution yet for this in a lab environment?
EDIT: apparently it does cache the user's info into the local profile for that user. So each user DOES have a separate session as Adobe said.
@kricotta There is an Adobe Pilot Program going on right now that looks to address this exact login issue on a multiuser/lab machine.
The way we overcame the login issue in the past, was to set up a loginhook and startup script which unlicensed and relicensed the Adobe suite.
@kricotta what you said earlier has been my experience as well.
@taugust04 What OS did you use to run the user sync tool on?
I'm currently experimenting with a win10 to have the configuration of scripts set up properly.
Then I will have it run as a job on a server. Doubting between linux and windows server.
@arnokenis I have the user sync tool running on a Windows Server 2016 VM in our VMware 6.5 virtualized data center environment. So far so good, but other than some light testing not a lot of heavy usage so far.
If behind PROXY, how do you deal with Adobe Creative Cloud client?
Seems like ACC client does not go to the system network settings by authentication saved in Keychain.
Is there any way to direct ACC client to use system PROXY settings?
@mhasman we worked with our network team and Adobe support to allow no-auth rules for Adobe's listed network addresses.
@csanback , could you please elaborate on how you were able to get the no-auth rules set up? I spoke to Adobe support this morning, and they said that there is no way to remove the login prompt upon opening Adobe CC 2019 apps deployed through SDL...
We are a very small university, and we only buy enough seats for faculty and staff, NOT students. So for lab/classroom computers, we used our serialized license (up till CC 2018) to deploy to those computers, which removed the need for students to log in to the CC apps.
So if there is indeed a way to remove the need for our students to login on Adobe CC 2019 every time on lab computers, then I'd love to hear it.
@asiddiqui The new Adobe Shared Lab license will only utilize one license per machine, but keeps the login requirement even though it doesn't utilize the login for licensing. IE - you have to implement Enterprise/Federated Adobe ID's for users and they'll be required to login whenever they launch CC 2019 or newer, but it'll use a single "lab" license. I've already seen the option to convert my device licenses to this new type when I login to Adobe Admin Console.
@asiddiqui The no-auth rule was for the our proxy not the login of Adobe CC Desktop app.
