Software Deployment Question
Adobe Creative Suite 6 (CS6) Software distribution
Anybody have good links or information on a good way to distribute Adobe CS6 through KACE. I have already made the software packages using the Adobe Application Manager Enterprise Edition which was the easy part. Reading through the the Adobe Enterprise Deployment Guide I find myself a bit stumped especially when it comes to the part about deploying the exceptions as adobe calls it. The Adobe Enterprise Deployment Guide can be found here for reference: http://wwwimages.adobe.com/www.adobe.com/content/dam/Adobe/en/devnet/creativesuite/pdfs/AdobeApplicationManagerEnterpriseEditionDeploymentGuide_v_3_1.pdf
Since these are large I know I will have to use an alternate location but I just am not sure if I just need to run the packaged msi using the typical msi installer commands or if I have to make a whole script that deploys the exceptions as well.
If anyone has successfully deployed Creative Suite 6 or even 5/5.5 as I am sure they are similar and had success a nice guide outline would be appreciated.
Community Chosen Answer
Here's a writeup I did for a classroom we gave at Konference last year. I don't think CS6 has changed.
1. Preparing the Package
First things first, we have to prepare the package for use with, or without K1000.
Adobe Application Manager Enterprise Edition (AAMEE) provides a straightforward and customizable way to wrap CS 5 and 5.5 applications and their updates as MSI or PKG packages for silent deployment across the enterprise.
a. Install ApplicationManagerEnterprise_2_1_all.exe (AAMEE) from C:\Labs
Also available for download at: http://www.adobe.com/devnet/creativesuite/enterprisedeployment.html
b. Once installed- Use AAMEE to generate your enterprise package.
i. Package Page:
Package Name= Adobe CS5 Master Collection (Your name Here)
Save To= \Desktop\Projects\CS5
Locate the Product Install Folder=
C:\Packages\Adobe\Adobe Master Collection CS5\Adobe CS5
OS Support= 32-Bit
ii. Serialize Page
-Proceed Without Serializing
-Select Language= English North America
iii. Options Page
Install All default or selectable options
iv. Configure Package
Disable all product launch options
Conflicting processes- ignore conflicts and continue
Adobe Updater options- Distribute Manually
Install Location- Default
v. Updates Page
Include no updates.
vi. Build! Warning this will take some time. 5-15 Minutes possibly. When complete you should find the package at \Desktop\Projects\CS5\CS5\Build
vii. Since the K1000 only allows 1 file to be uploaded, we need a compressed archive. Zip the contents of the Build folder together into “AdobeCS5.zip”. We recommend 7-Zip for speed and compression optimization. See 7-zip.org if it’s not already on your machine.
2. Uploading the package
a. Look under Inventory > Software for the version of Adobe Creative Suite that you downloaded. Is it there?
i. If so, open the record by clicking on the name.
ii. If not, let’s create a custom inventory rule to [loosely] detect it temporarily.
1. Inventory >Software > Add New Item (Choose Action Drop-down).
2. Name your package and choose supported operation systems (All versions of Windows)
3. Create a Add the Custom Inventory Rule. Possible Examples:
a. FileExists("C:\Program Files\Adobe\Adobe Photoshop CS5 (64 Bit)\Photoshop.exe")
b. RegistryValueEquals(HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Photoshop\12.0, Version, XXX.XXX)
b. Review the information on the page, such as version, installed computers, display name, supported operating systems and ensure that it is the correct data record for the software you are uploading. Even if it isn’t, we’ll come back and fix it later…
c. Using the software detail page, upload the package Created in Part 2. Can you upload from the Software inventory page as usual? Nope. It’s too big- the browser doesn’t want to upload things larger than 1.5 GB. Sad day… Workaround!
i. Copy the file to your \\kboxname\clientdrop
ii. Browse back to the software detail record and choose the file from the samba share. Only files larger than the client-drop filter size (1GB by default) will show up here. (Alternate methods exist also, talk to your instructor for more details.)
d. Click save.
3. Configuring the managed install
a. Browse to Software Distribution > Managed Installs
b. From the “Choose Action” box, select “Add New Item”
c. Now, select the Adobe CS5 record that was uploaded in the previous step. It’s a zip file, right?
d. Using Appdeploy.com, research which parameters will allow a silent install and insert the fill install command with silent switches into the command line section (configure manually radio button). Tips: http://www.itninja.com/software/adobe/creative-suite-5-any-edition/12-455
e. In the Notes box let’s input the major data points: Windows Silent Install- No EULA, No Updater
f. Select a managed action appropriate for testing. (While logged on, or Execute Anytime typically.)
4. Machine selection for deployment
a. Select a label or a single machine to target for provisioning CS5.
b. Set the Max number of retries to 10, and the Deployment order to 10.
c. Leave the deployment window set to the default of 0/24.
d. Next decide if you want pre/post installation messages for visibility during testing.
5. Test the installation
a. Review your Managed installation for correctness. Check syntax, command lines, targeted machines, Supported OSes.
b. Once you’re comfortable that the package is correct, save the new Managed Installation.
c. Force an inventory update from Inventory > Computers > <Computername>
d. If you created a Software Inventory record in step 3a, Re-upload the zip file to the correct software inventory record and reassociate the managed install to that database record.
6. Rejoice! Now you’re ready to deploy your package to more systems.
This wasn’t an easy package, but certainly not the most difficult either. Some software will require much more work on your part- especially if the manufacturer doesn’t provide or support a tool to create a deployment. Adobe, Microsoft, Autodesk, and many other software manufacturers that make large complex software titles such as Adobe Creative Suite and Microsoft Office, may provide tools to simplify enterprise deployment. They certainly don’t have to, and often don’t, but when the tools exist they simplify creation and future maintenance. Check in with the manufacturer of your software for their documented practices on command line based deployments. AppDeploy is also a great resource for going beyond what the manufacturer has, and in many cases where the manufacturer doesn’t have documentation.