Whatever method you use to upgrade SMS 1.2 PGC applications to SMS 2.0, you need to become familiar with the SMS 2.0 features that replace SMS 1.2 PGC features. Table 5.1 lists the primary SMS 1.2 PGC features and their corresponding features in SMS 2.0. For more information about each SMS 2.0 capability, see Chapter 12, “Distributing Software,” in the SMS 2.0 Administrator’s Guide.
Table 5.1 Comparison of PGC-Related Features in SMS 1.2 and SMS 2.0
| This SMS 1.2 capability | Is Replaced by this SMS 2.0 capability |
|---|---|
| Applications distributed to Windows NT user groups | Applications advertised and distributed to collections of systems, users, and user groups |
| One-time configuration script execution | One-time execution of one or more dependent programs |
| Partial load balancing between distribution servers | Optional load balancing between distribution points during initial program execution |
| Persistent desktop groups and icons based on Windows user group memberships and removal of these groups when the user is removed from the Windows user group | Shortcuts distributed and installed on each client. Optional removal of the application from clients when the application is no longer advertised to the clients |
| Creating a job with a repeating schedule in <Job Properties><Schedule> | Recurring assignments (mandatory programs that run repeatedly on a schedule you set up) |
| Limited support for file association and OLE support for applications shipped with SMS 1.2 | Full scripting support including file and icon placement, file association, and OLE support, using SMS Installer scripts |
| Partial registry management of applications shipped with SMS 1.2 | Registry management using SMS Installer scripts |
SMS 2.0 provides many features that were not directly supported in SMS 1.2. Among these are: