Installing Applications Across Your Network

I really like Windows NT 4.0. I love the interface, the speed, theflexibility, the new features, and the list goes on and on. But my favorite partof NT is an undocumented feature, a simple Registry change, that lets me use myserver to install software across the network painlessly.

The biggest challenge in using a Registry change for software installationis in getting the Registry change to each system. Two methods can help you getthe Registry change to each system: manually (as outlined in this article) orwith System Policy Editor, which lets you push Registry changes from a server toall systems on the network. (For information about how System Policy Editorworks in NT, see Robert Slifka, "How to Edit NT 4.0 System Policies,"February 1996, and Sean K. Daily, "Further Explorations of the NT SystemPolicy Editor," page 139.)

Considering Network Management Software?
Several software packages let you powerfully manage and control systems onthe network, even in a multiplatform environment. Intel's LANDesk, Attachmates'NetWizard, IBM's NetView, and Microsoft's Systems Management Server (SMS) arejust a few in the ever-growing niche of server-control software applications.

SMS can control DOS, Windows 3.x, Windows 95, NT (all versions), NetWareServers (Bindery mode only), Macintosh, IBM LANManager, and Microsoft LANManagerclients. SMS lets you install software and operating systems, remotelyadminister and troubleshoot systems across the network, monitor activity, set upfailsafe application serving, and perform other complex but powerful functions.

I used to use SMS to install software, which is the most powerful part ofthe program. I loved the ability to push software to users' systems and forcethem to accept it.

The reality, though, was that I seldom did that. Mostly, I set up SMS forusers to easily install the software at their convenience across the network,without a CD-ROM. (For more on SMS, see Brady Richardson, "SMS Tuning Tips,"page 95 and the list of related Windows NT Magazine articles.)

SMS requires SQL Server with licenses, plus SMS client licenses. For a100-user network, SQL Server costs $1795, including five client licenses. SQLServer client licenses are $40 each. SMS Server software costs $1495, whichincludes five client licenses, and each additional client costs $24. A reductionin initial cost is available if you purchase the entire BackOffice suite, but noreduction in cost of the client licenses is available, except for volumepurchases.

SMS is a nice but expensive package, as are its competitors. If you use allSMS's features, the time savings can justify the cost. But, if you only need SMSfor software installation, a simple Registry change is a better choice.

Using the Registry
Unlike SMS or a similar software package, the Registry change that lets youinstall software across the network is free (except for your software licenses).Rather than spend the money on a sophisticated software package, make a changeto the Registry, and every user will have access to pull the applicationinstallation across the network.

To make the Registry change, create a share, and copy the installationfiles to it. For example, create a share named Install and create subdirectoriesfor Excel, Collage for Windows, and PageMaker, as you see in Figure 1.

At the server, edit winntinfapps.inf, and add the [AppInstallList]section, followed by a line for each application, in the format Label={path tosetup.exe}. Screen 1 shows the entry in the app.inf file.

At each workstation (NT 4.0 or Win95) that will participate in thisprocess, add the Registry entry that follows. (Remember, editing the Registrycan be dangerous. Mistakes in editing the Registry can make the system unstable,or even unusable. Back up your Registry before continuing, and then proceed withcaution.)

HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersion

Add a new value, AppInstallPath, as a REG_SZ entry. (This tip uses theWindows key, not the NT key.) Type the name of the path to the apps.inf file onthe server, as you see in Screen 2. Use a universal naming convention (UNC) name(\servernamesharepathapps.inf) including the full path and the file name.

Once the data is at the server and you've made the Registry changes,activate the installation at the workstation with Control Panel, Add/RemovePrograms, Install, as Screen 3 shows. Notice the new Network Install tab shownin Screen 4. Click this tab, select the program you want from the list, andchoose Install to install the software across the network to your local system.

Of course, you must inform each user that software is available forinstallation. I usually do this part with email and let users install thesoftware at their convenience.

Installing Internet Explorer 4.0
When Microsoft releases Internet Explorer 4.0 (IE4), everyone on the networkwill want to install it. Rather than download it to each system, you can usethis Registry technique to download it once to the server, extract the files,and use one instance of the files to install the program to every system on thenetwork.

Although the application will be the same for NT Workstation and Win95, thesetup program is different (because of differences in the operating systems).I'll give you the steps for installing IE4 in NT (for Win95 systems, change thefilenames and descriptions accordingly).

At the server, download the compressed installation file from Microsoft(ntie40.exe). Create a new folder (NTIE4) under the Install share you createdpreviously. Execute the downloaded file, and extract the files to the new NTIE4folder. Edit the apps.inf file, and add the following line under the[appinstalllist] section (replacing \server1 with the name of your server), asshown in Screen 5:

Internet Explorer 4.0 for NT=\server1installNTIE4setup.exe

Go to the Add/Remove Programs

applet in the Control Panel of one of your workstations and select theNetwork Install tab, as shown in Screen 6. Highlight Internet Explorer 4.0 forNT, and click Install.

Unlock the Potential
Using a simple Registry change can unlock an undocumented feature of NT 4.0and Win95. Installing software with this tip is very fast, and very easy. Itcertainly doesn't do everything SMS and other software-management packages cando, but the cost is right.

RELATED ARTICLES IN WINDOWS NT MAGAZINE
Christa Anderson,
- "Designing Unattended NT Installations," March 1997
Nathaniel Bowman,
- "SMS Server and Client Setup," June 1996
- "SMSServer and Client Setup, Part 2," July 1996
Mark Eddins,
- Customizing Systems Management Server," January 1997
"- CustomGraphics for SMS Custom Inventory Objects," March 1997
Spyros Sakellariadis,
- "SMS: Inventory Your Desktop Systems, Part 1," May 1996
- "SMS:Inventory Your Desktop Systems, Part 2," June 1996
- "SMS:Inventory Your Desktop Systems, Part 3," July 1996