Adobe 65019371 Deployment Guide - Page 38

Creating Packages Editing Package Files Testing Packages If you are deploying with ARD, skip this section and go to Chapter 3. If you are deploying with SMS/SCCM, skip this section and go to Chapter 4. Now that you have created your packages, you will want to test them before deploying them widely. 1. Set up your test system so that it is configured just like a target system.  Make sure the test system meets the system requirements for the package you are testing.  Make sure the product install folder the deployment package references is located as specified on worksheet #3 in the PACKAGE-TO-PRODUCT INSTALL FOLDER PATH field.  Make the package available in the same way that it will be deployed to the target systems, as specified on planning sheet #3. 2. Run the Uber program on the test system. You must have administrative privileges to run the Uber program. Either navigate into the package folder or provide a complete path to the folder to invoke the Uber programs. On Windows XP: On Windows Vista: On Mac: Make sure you are logged into an account with administrative privileges. Open a command prompt window. Type the following: cd AdobeUberInstaller.exe Open a command prompt window using Run As Administrator. Type the following: cd AdobeUberInstaller.exe Open a command prompt window. Type the following: cd sudo ./AdobeUberInstaller Test your package on a system that meets the performance requirements for the applications you will install from these packages. This machine should have similar system capacity as the target systems on which you will deploy your packages. 3. Check the log file. The AdobeUberInstaller program creates a log file in which it records the steps it has taken along with the exit code returned by the install program. If this log file already exists, it appends the latest results to it. The file is called adobecsdt.log and is located in %temp% on Windows and in /tmp on the Mac. Document Version 1.0 September 2009 38