Mar 3, 2009
Cool Tips for Deploying Creative Suite 4 – SMS 2003/SCCM 2007
I would like to introduce a new segment on the blog, dedicated to the latest and greatest methods for deploying your Creative Suite software. Please look for future tips covering all aspects of deployment and updating.
My name is Chris Hohman and I have been a Product Manager with Adobe for the last 2.5yrs. Working on improvements to the enterprise deployment experience since I began, I am now fully indoctrinated into the land of OOBE. It was speaking with customers like you that inspired the creation of the Adobe Creative Suites 4 Deployment Toolkit (CSDT). Hey it is a start, and there will be more to come.
Let me also introduce the CSDT if you are not familiar with it. The CSDT is an efficient, easy-to-use, and reliable application that configures Adobe Creative Suite 4’s installers for silent deployment. It’s Adobe AIR-based (Adobe Integrated Runtime) interface allows you to create a remotely deployable install package without laboriously hand-editing configuration files. More information can be found at http://www.adobe.com/aboutadobe/openoptions/cs/deployment_toolkit.html
Setting up multiple distribution points using Microsoft SMS 2003 /SCCM 2007 and the Adobe CS4 Deployment Toolkit
On a recent customer visit, our team was able to address an issue relevant to many of you that set up multiple distribution points spanning across more than one server.
Here’s what you need to know:
Microsoft SMS/SCCM provides the ability to deploy from a common shared file. Here are the details straight from the MS website, “At installation, SMS assigns the distribution point role to the site server. You can create additional distribution points to reduce the load on the site server and provide access to all client computers in your site. If software distribution in your SMS system includes multiple sites, specify a distribution point in each site to ensure access by client computers and to distribute the load.”
“If you use the common SMS package shared folder on distribution points, when the first package is sent to a distribution point, the distribution point is given the share name \\computername\SMSPKGdriveletter$ on the NTFS drive that contains the most available space.”
The CSDT requires an absolute path to the source install location in the AdobeUberInstaller.XML and AdobeUberUninstaller.XML files and this causes problems with the share location.
Load distribution can be achieved by changing the UNC install location path of the UberInstaller to the local parent directory of each DP server.
This is accomplished as follows:
1. Use the CSDT to create a package normally.
2. Open the AdobeUberInstaller.xml in an editor and replace the UNC parameters with a “/.” to indicate that it needs to refer to the parent drive of the server. Please note that the usual value of the “InstallerLocation” parameter is taken from the same “Media Path” which you selected in the first screen of the CS Deployment Toolkit.
3. Repeat for the AdobeUberUninstaller.xml.
4. On the source server, place the full adobe installer including all payloads and extensions along with the two modified XML files and the two executables created by the CSDT.
5. Use this source location to set up the SMS/SCCM packages
6. Repeat this process across all servers used for load balancing
This process can help you set up SMS using the CSDT. It has worked for two customers and counting. If you know of an alternative way to accomplish this same task, please share.
Feedback is always appreciated.
Cheers until next time.