Previous | Next

Using Apps.ini for Pull Installations

By creating an Apps.ini file, you can let users upgrade from Windows 95 to Windows 98 simply by clicking a button. Using an Apps.ini file provides the benefit of simplicity and the benefit that users can choose when to upgrade their operating systems.

The general process is as follows:

  1. Create a batch file that includes the Setup command, any switches you need, and any other commands you might need, such as version-checking commands.
  2. Create a PIF file for that batch file.
  3. Create an Apps.ini file that contains a reference to the PIF file.
  4. Create a system policy to activate the Network Install tab in the Add/Remove Programs option in Control Panel.

Creating the Batch File and PIF File

First, create a batch file that you can use to perform pull installations. The batch file should contain, at minimum, the following:

\\Server\Share\Setup.exe

You could also add switches to the Setup command, and you could use the Msbatch.inf parameter. Additionally, you could add other commands, such as a section that checks the version of your operating system so users cannot run Windows 98 Setup from a Windows 98–based computer. For more information, see "Implementing Version Checking for Automated Installations," later in this chapter.

Next, create a PIF file for the batch file. For information about creating PIF files, see Chapter 25, "Application Support." Make sure to select the check box Close on exit, so the batch program window will close after it runs. Otherwise, you will have problems with Setup.

Creating the Apps.ini file

Next, create an Apps.ini file (or an entry in an existing Apps.ini file) that refers to the PIF file. For information about how to create an Apps.ini file, see Chapter 25, "Application Support." The following example shows a basic Apps.ini file:

[AppInstallList]
ProgramName = * \\Server\Share\Directory\Filename.pif

You could also use Apps.ini to set up different computers with different configurations. For example, you could use Apps.ini to set up Windows 98 with Windows NT on some computers, and Novell Client for Windows 95/98 on others. You could even control which users get which client by giving different users different levels of access to the share that contains the Setup.exe command. The following example shows this configuration:

[AppInstallList]

********************** Marketing **********************=
Windows 98 Upgrade - Windows NT=
*\\Server\Marketing_Share\Directory\WinNT.pif
-=*
************************ Sales ************************=
Windows 98 Upgrade - Novell Client=
*\\Server\Sales_Share\Directory\Client32.pif

In this example, WinNT.pif refers to a batch file that includes an Msbatch.inf statement. The Msbatch.inf file directs Windows 98 Setup to install Windows NT when performing the upgrade. Thus, when a user clicks the Windows NT entry, Windows 98 is installed with Windows NT. Likewise, when a user clicks the Novell Client entry, Windows 98 is installed with Novell Client for Windows 95/98.

Now, suppose you have given the users in Marketing network access to Marketing_Share but no access to Sales_Share, and you have given the users in Sales network access to Sales_Share but no access to Marketing_Share. The Marketing users can run Setup and get the Windows NT, and the Sales users can run Setup and get Novell Client for Windows 95/98.

Giving Users Access to the Apps.ini File

Finally, you must set a system policy so users can access the Apps.ini file. After you set the policy, a Network Install tab appears on the Add/Remove Programs option in Control Panel. The tab shows all the applications the user can install, and the user simply clicks on the application to install. To set the policy, you must first add the Appsini.adm template, then set the policy named Network path to APPS.INI.

To add the Appsini.adm template

  1. In System Policy Editor, click the Options menu, and then click the Policy Template.
  2. Click Add, and then select the Appsini.adm file. This file is located in your \Windows\INF directory.
  3. Click Open, and then click OK.

To set a system policy to give users access to Apps.ini

  1. In System Policy Editor, click the File menu, and then click New Policy if you have no existing policy file, or Open Policy if you have an existing policy file.
  2. Double-click Default Computer.
  3. Click the plus sign to expand the Network Install section, and then click the plus sign to expand the Use APPS.INI for Network Installs section.
  4. Select the check box for the policy named Enable Add/Remove Programs, Network Install tab.
  5. In the Network path to APPS.INI box, specify the full network path and file name for the Apps.ini file, and then click OK.
  6. In the File menu, click Save, enter a name for your policy file, and then click Save again.

This policy adds the registry value AppInstallPath (string type) with the value of the universal naming convention (UNC) path to the following registry key:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion