Of course, software packages are what the Software Installation and Maintenance part of IntelliMirror is all about. Once you've set up the group policy and configured the general software installation options, you're ready to start adding software packages and working with them. The following sections help you add packages to the group policy, change their properties, upgrade and modify packages, and remove obsolete packages.
Before users can easily access applications that you copy to the software distribution point discussed earlier in this chapter, you need to add the installation packages to the group policy. To do this, follow these steps:
TIP
If you want to apply any modifications (transforms) to your package, you must do so when adding the package to your group policy. Transforms cannot be added to currently deployed packages.
Figure 24-6. The Deploy Software dialog box.
NOTE
You will see the Deploy Software dialog box only if you selected the Display The Deploy Software Dialog Box option in the Software Installation Properties window, as described earlier in the section "Setting Software Installation Options." Otherwise, the package you selected will be automatically published or assigned, or you will see the package's Properties window, discussed in the next section.
Once you've added a software package to a group policy, you may want to change the package's properties, perhaps changing the application's category, deployment type (assign or publish), or security settings. Use the following steps to change these and other settings:
Figure 24-7. The Deployment tab of a software package's Properties window.
Upgrading applications can be a pain for administrators. The new version of Microsoft Office is released and suddenly everyone wants it. In the past, this has often led to version management nightmares when some users couldn't read files created by other users, and managing applications in general was a headache. Fortunately, Microsoft (to name only one vendor) has worked to make this situation better. (For instance, they now change their file formats only when necessary.) Using IntelliMirror's Software Installation and Maintenance features helps a lot, because administrators can better manage the upgrade process. Of course, users of SMS have always had these features available.
When you get a new version of an application, you can start by publishing it (as an upgrade and a full installation) so that users can upgrade to it if they want to. After a period of time, you can assign the application to users, requiring them to either upgrade or install the new version in parallel with the old version. At this time you can also prevent new installations of the old version. Once all users have had a chance to get accustomed to the new version, you can remove the old software package and force it to be uninstalled from users' systems, completing the transition. Use the following procedure to install upgrades. See the section "Removing and Redeploying Packages" later in this chapter for information on how to complete the process and remove obsolete packages.
TIP
You may find it useful to apply a transform to the upgrade package—for example, to allow Microsoft Word 97 users simply to upgrade to Microsoft Word 2000 without installing the rest of the suite. To do this, see the next section, "Applying Package Modifications."
Figure 24-8. The Add Upgrade Package dialog box.
Select the Package Can Upgrade Over The Existing Package option to use the new package to upgrade the older package, preserving the users' settings. Click OK when you're done.
Figure 24-9. The Properties window for an upgrade package.
TIP
Use the Uninstall The Existing Package, Then Install The Upgrade Package option when an upgrade either isn't possible (in the case of upgrading to a different application) or isn't desirable (when the upgrade process works poorly).
Package modifications, also called transforms, allow you to customize an installation package without completely reauthoring it. For example, instead of offering Office 2000 only in its complete configuration, you may want to offer users the choice to install a subset of the programs installed by default. Without using transforms, you would have to create a completely separate package, consuming an excessive amount of disk space. Instead you can create a transform to simply modify an existing package to your needs, saving disk space and time. Thus, rather than adding two different packages to your group policy for two different configurations of an application, you can add your complete package and then add the complete package a second time with a transform to modify the original package to your specifications. Instead of storing two full-sized packages, your complete package is stored once, with the small transform piggybacking off of it.
Since transforms are merely an easy and efficient way to modify a package for deployment, not a mechanism for allowing a single package to present multiple options to users and administrators, you still need to add the package to your group policy multiple times—once for each configuration you want available to users. Additionally, transforms must be applied at the time you add the package to Group Policy; they cannot be added to currently deployed packages. To create a transform, follow these steps:
TIP
To see the Deploy Software dialog box in step 4, you must have selected the Display The Deploy Software Dialog Box option in the Software Installation Properties window, as described earlier in the section "Setting Software Installation Options."
CAUTION
Do not click OK in the Properties window until you have configured all settings the way you want them. As soon as you click OK, the package is assigned or published in Active Directory and is immediately deployed, potentially affecting a lot of users. If, after clicking OK, you realize you made a mistake, you can fix it either by upgrading the incorrectly configured package with a correct one or by removing the package from Active Directory and all users.
Figure 24-10. Placing transforms in the correct order.
When an application has outlived its usefulness in your company, it's time to remove it from your systems—or at least to stop deploying it on new systems. There are also times when you may want to redeploy an application so that it is reinstalled on all clients. Use the following steps to accomplish these tasks:
Figure 24-11. The Remove Software dialog box.