Site License Advisory Team Adobe Creative Cloud December 10, 2014 meeting

Agenda 1.Overview of the Adobe Creative Cloud license 1.Agreement terms 2.Who can use it, and Where 1.Home Use options 3.What the percentages mean 2.Available Resources 1.Adobe Presentation 2.Powerpoint 3.Readme Files 3.Deployment 1.Important First Steps 2.Common Issues 3.Security considerations 4.Tips and Tricks 4.Questions 2

Overview of the Agreement: Terms The agreement is a 3-year agreement term. Costs are set year-to-year. –Expected savings, university-wide, are between $250k - $500k, per year. –Payments made yearly Provides access to all Creative Cloud products and Acrobat Pro, but not other Adobe products. Virtualization is permitted, but performance is not guaranteed. 3

Overview of the Agreement: Usage The CC software is available to OSU Faculty and Staff, on OSU-owned machines –Acrobat available for work-at-home on personal machines. –Grad Associates are included in this Home Use: –The license includes a home use option for CC, but it is not ready yet. It will be $10/year, paid by the fac/staff/GA, and will include the full suite. We will work on this aspect next. 4

Overview of the Agreement: Percentages Deployment percentages: –100% Acrobat coverage, on OSU-owned and personal machines (personal for work-at- home only) –35% Creative Cloud coverage, on OSU- owned machines only at this time OSU Purchasing will ensure we do not exceed. If we do, funding for extra licenses will come from departments using the software. 5

Available Resources for Distribution Distribution tools (CCP Launchers, Readme’s, and the resulting Pacakgers) are available only to SLSC’s at this time. –We may increase this distribution down the road, but because of the 35% requirement and the complication of the tools, we did not wish to distribute this to every faculty/staff person. Box links can be given to those who do not have access to SLSC downloads, but need the software to do their job. 6

Available Resources for Distribution You must review two key resources before attempting deployment. The first: –A video presentation (40 minutes long) that was attended by a few people from OSU and is focused on our deployment. – –This video will answer almost all questions you might have about the deployment process. It is required viewing prior to deployment. 7

Available Resources for Distribution You must review two key resources before attempting deployment. The second: –A powerpoint that goes in depth on the distribution process: The link to this has some issues in the readme document: the “-” got replaced by word and creates a non-readable character. Re-typing it will get you to the right link. 8

Available Resources for Distribution There is a Readme File included in the download: please read it –This file includes a number of answers to questions about both the process and the licensing –The file also includes ideas for how to update the license files and respond to common issues during the installation. –This document includes your serial numbers. 9

Deployment: First Steps The CC Packagers allow the creation of multiple, usage-specific packages. Please do not deploy as part of a “standard image” on all machines –Select areas with a business need for this software and deploy to those areas Departments should keep a record of where this software is deployed –Adobe has indicated that enterprise tools will be available in the new year, but they are not yet. 10

Deployment: First Steps The download provides launchers which will download the package for installation. You must be connected to the internet You must create a deployment package for Windows on a Windows machine, and a deployment package for Mac on a Mac machine. You must have an Adobe account to run the installer. 11

Deployment: First Steps The CC Packager will create a.msi and.exe file (win) or a.pkg file (mac) Adobe has designed these for deployment via SCCM and Casper, but indicates they should be fine for other products as well You may only package a single language at a time 12

Deployment: Common Issues Problem: Some customers apparently do everything correct but still end up with trial licenses on their machines. –Solution: re-serialize the deployed product with the CCP Packager Problem: Not all packages appear in 32-bit Windows distributions –Solution: there are not 32-bit versions of all products: customer needs a 64-bit machine. 13

Deployment: Common Issues Problem: Upgraded to CC already with the “Grand Gesture” –Solution: re-serialize the deployed product with the CCP Packager Problem: I’m not sure when updates come out. How do I know when to package new ones? –Solution: Follow Adobe’s blog on this: eupdates eupdates 14

Deployment: Common Issues Problem: I have a machine not connected to the internet: can I deploy? –Solution: Yes: you can put the deployment package on a thumb drive or external hard drive, transfer it to the machine, and run it. No internet connection is required (according to Adobe). 15

Deployment: Security Concerns You must disable the “Creative Cloud Desktop Application” option during package creation –This allows for items such as cloud storage (2GB) and other consumer-based items. –None of the CC Desktop Apps have been vetted by OCIO Security. Leaving that box unchecked is required. –Adobe has indicated that beyond security concerns, there are also serialization concerns with the CC Desktop Apps: they might break your deployment. 16

Deployment: Tips and Tricks Make sure you have enough space for the deployment when you build the package –Complete deployment package with all products is over 14 GB in size It is useful to create a test deployment that includes all products first, but not to deploy it to machines: –This will download all products onto your computer and speed up the packaging process. 17

Deployment: Tips and Tricks Create multiple deployment packages for multiple business needs –Most people do not require all 26 products to do their jobs, but they will require different combinations. The product we have is officially called “Creative Cloud for Enterprise” Set up an Adobe account that is non-personal and can be forwarded to several individuals: –The Adobe account will receive information on updates to the packages you create. 18

Questions/Comments 19