Preparing Installation Scripts

Whether you are creating an entirely new shared application or migrating low risk programs using the PGC Migration Wizard, you must prepare the installation scripts for the shared application. There are three different methods for preparing installation scripts:

Using the PGC Migration Wizard
If you are migrating packages from SMS 1.2 to SMS 2.0, you can use the PGC Migration Wizard to migrate existing packages and programs from SMS 1.2 to 2.0. The wizard displays the shared SMS 1.2 packages that were preserved during the upgrade from SMS 1.2 to SMS 2.0. These packages are available for migration to SMS 2.0 packages. You can:
  • View a list of these packages and programs.
  • Analyze them for migration risks.
  • Have the wizard migrate them automatically.
  • Migrate them manually.

Using the wizard, you can also print a status report including the wizard’s analysis of your application. The PGC Migration Wizard keeps track of the status of programs as you migrate, and you can modify their migration status.

Modifying the Setstart Client Installation Script
If you do not use the PGC Migration Wizard, or for applications that do not migrate cleanly, you can use and modify the sample Setstart client installation script that is part of this resource kit. You can also use Setstart to create entirely new shared applications. Setstart creates desktop shortcuts that point to the directory where Setstart is placed on the server.
Creating New Installation Scripts
Another option is to create an entirely new client installation script using the SMS Installer to monitor the changes that are made to your computer when an application is installed.

Detailed instructions for using each of these methods are given in the next three sections: