Adobe 65019371 Deployment Guide - Page 44

4 Deploying Adobe® Packages with SMS This chapter guides you through the process of creating either an SMS 2003 or an SCCM 2007 package to deploy an Adobe® CS4 deployment package. Since both Adobe and Microsoft® use the term "package" and since there are currently two versions of the Microsoft software in use, we use the following naming conventions for clarity in this chapter:  When referring to the older version of the Microsoft software, we say "SMS 2003". When referring to the newer version of the Microsoft software, we say "SCCM 2007" or just "SCCM". When referring to the Microsoft software in general, independent of a particular version, we say "SMS".  When referring to a package created with either SMS 2003 or SCCM 2007, we say "SMS package" unless the context is very clear, when we may say just "package". When referring to a package created by the Adobe Enterprise Deployment Toolkit, we say "Adobe deployment package" or "Adobe package". We never use the term "package" alone to mean an Adobe package. Preparation SMS was designed for a great variety of network configurations. Despite this variety, when deploying with SMS, the best choice of deployment configuration for the Adobe package and its product install folder is TS, where the Adobe package and its product install folder are placed together on the same distribution server(s). Before Adobe deployment packages existed, when you created an SMS package for an Adobe product install folder, you turned on "This package contains source files" and then provided the SMS package a path to the product install folder. Then, when creating the programs for this SMS package, you specified the Setup.exe that resided in the top level of the product install folder structure. When using Adobe deployment packages to install CS4 software, you have two things to hand to SMS instead of one: you have the Adobe deployment package itself, which is a folder with four things in it, and you have the product install folder associated with that Adobe package. Furthermore, the XML files in the Adobe deployment package contain a path to the product install folder. Product Install Folder Adobe Deployment Package Setup.exe Other stuff.. AdobeUberInstaller.exe AdobeUberInstaller.xml AdobeUberUninstaller.exe AdobeUberUninstaller.xml Since an SMS package treats its source files as a single entity, you must combine the two Adobe items in such a way that they look like one item to the SMS interface, are propagated as one item to distribution servers, and possibly target systems, and still function appropriately when the Adobe package is invoked. Document Version 1.0 Sep 2009 44