Skip to main content

Hello there everyone!



It's that wonderful time of the year when all of our school district technology gets updated for the next semester! The only upgrades we are doing this year is to High Sierra (10.13.5), Microsoft Office (16.13.18), and Adobe CC 2018.



Thus far everything has gone well, except for Adobe CC 2018. We built out our IT installer package via adminconsole.adobe.com and simply placed the .pkg installer in our JAMF Admin console. The install works perfect, but the issue we run into is that every time an app is launched a popup dialog shows up asking to log into Adobe Cloud with an account. This isn't a message that has to do with licensing, as they give you the option to close it, and everything works fine--it's just frustrating that every time any program is opened a user is asked to login. This wouldn't be an issue if all students had an Adobe account, but that is not a project we wish to take on right now, nor pay for.



Has anyone else run into this scenario? What were your fixes?

Currently we use Creative Cloud Packager. Make 1 for EACH program. Package the PKG in a DMG using Disk Utility & add to JAMF. Policy runs the installPKGfromDMG.sh file. Updating works MOST the time, no flagging to log in, but still an option.

@c.archibald you are absolutely correct on this workflow.

For device licenses, use the Creative Cloud Packager desktop app to build installation packages on a system which doesn't already have Creative Cloud installed. To prevent users from logging in with an Adobe ID and breaking your device activation, be sure to uncheck the Creative Cloud desktop application box so it's not included.



For named-user installations, use the browser-based packager to build installation packages in either self-service mode (end-users can manage apps, no administrator privileges required) or managed mode (administrators must manage apps). Login with an Adobe ID is required, so the Creative Cloud desktop app will be included.

Thanks @erowan. This was exactly what we needed! The Creative Cloud Packager app was having issues launching, but it turns out it's because you need to build your packages on a machine that doesn't already have the Creative Cloud Packager. I just built it out on one of our Mac Mini servers and then dropped it in the local jamf share. Worked perfect!

whoops Forgot about that, thanks! I edited my post, just in case someone stumbles upon it in future.

Terms & ConditionsCookie settings