Installing the IntranetWare Client for Windows NT Workstation
Articles and Tips: article
World Wide Support
Novell Support Division
01 May 1997
Novell's IntranetWare Client for Windows NT features an improved installation process that allows easy initial installations as well as upgrades of previous client software. This AppNote gives instructions and examples of typical client installs and upgrades.
- Introduction
- Obtaining IntranetWare Client for Windows NT
- Attended Installation Examples
- Upgrading Windows NT Workstations with ACU
- Unattended Installation Examples
- Uninstalling the IntranetWare Client for Windows NT
Introduction
The IntranetWare Client for Windows NT features an improved installation process that allows easy initial installations as well as upgrades of previous Novell and Microsoft client software. The client can be installed locally at the workstation or over the network from an administrator's location. The IntranetWare Client installation program (SETUPNW.EXE)is integrated with the native Windows NT installation process,so it automatically detects system parameters such as disk space and software versions. It includes an Automatic Client Update (ACU) feature that enables you to update workstations through network login scripts or through the Novell Application Launcher. The IntranetWare Client can also be installed along with Windows NT itself through the NT unattended install facility. This eliminates the need for the administrator to travel to each workstation.
This AppNote covers the following aspects of installing IntranetWare Client for Windows NT:
How to obtain the IntranetWare Client for Windows NT software and prepare for installations using SETUPNW.EXE
Examples of performing attended installations of the IntranetWare Client for Windows NT
Upgrading the IntranetWare Client for Windows NT using the Automatic Client Update (ACU) option
Examples of performing an unattended installation of the IntranetWare Client for Windows NT and of both Windows NT and IntranetWare Client for Windows NT at the same time
Uninstalling the IntranetWare Client for Windows NT software
Obtaining IntranetWare Client for Windows NT
The IntranetWare Client for Windows NT can be installed from diskettes, from CD-ROM, from a local hard disk, or from a NetWare server. The files needed to install IntranetWare Client for Windows NT are provided on the IntranetWare Client Suite CD-ROM and are also generally available as downloadable files from the sources listed below.
Downloading IntranetWare Client for Windows NT
The downloadable version of IntranetWare Client for Windows NT is available in two forms: one for the diskette version, and one for the version that can be installed from a NetWare server or local hard drive.
|
Note: You should also download any patches and updates that are available for the IntranetWare Clientfor Windows NT. As of this writing, the latest version is 4.10,dated 970214. This is newer than the version that ships with IntranetWareand NetWare 4.11. No patches or updates to this version are currentlyavailable. |
From the Novell Support Connection Home Page. As of this writing, the IntranetWare Client for Windows NT can be found on the World Wide Web by setting your Web browser to the following URL (as always, the location of files online is subject to change):
From here, click on Product Support, then on IntranetWare Client 4.1 for Windows NT, then on File Updates to see a list of available files. Click on the appropriate filename to download.
The current Novell Client files are also available on the Minimum File Updates page at the following URL:
http://support.novell.com/misc/patlst.htm
From the Novell FTP Server. The IntranetWare Client for Windows NT software can also be downloaded by anonymous ftp from Novell's FTP server on the Internet. The path is:
ftp.novell.com: /pub/updates/nwos/iwclnt41
From NetWire on CompuServe. To access the IntranetWare Client for Windows NT software on CompuServe, type GO NWOSFILES at any CompuServe prompt. Select the NW CLIENT WIN NT library. Then select "IntranetWare Client 4.1 for Win NT" to download the software.
Extracting the Files
The files needed to install IntranetWare Client for Windows NT from a NetWare server or local hard disk are contained in the network installation version of the compressed file. After downloading the file, copy it to a directory on a NetWare server or local hard drive. To extract the IntranetWare Client for Windows NT files, go to the directory you copied the self-extracting file to and type the name of the file. As the file decompresses, it creates a full subdirectory structure that begins with an \I386 subdirectory. This subdirectory should contain the following structure:
SETUPNW.EXE LOCWIN32.DL NWSETUP.DL NWLANGID.DLL OEMSETUP.INF WORKMAN.REG ADMSETUP.EXE ADMNT_1 ADMNT_2 ADMNT_3 ADMNT_4 ADMNT_5 ADMNT_6 ADMNT_7 REDIR DIR NLS DIR LIBS32 DIR LIBS16 DIR LANDRV DIR NWADMNNT DIR NWSMGR32 DIR SYSTEM DIR NAL DIR
Making Floppy Diskettes
If you download the diskette version of IntranetWare Client for Windows NT, upon extraction the compressed file will create the files you need to make your own IntranetWare Client for Windows NT installation diskettes. You will need 14 blank, formatted diskettes. To create the diskettes, go to the directory where you extracted the files and type MAKEDISK <Enter<. Follow the onscreen prompts to insert and label the diskettes. (The compressed files require at least 512KB of available memory in a DOS box to extract properly.)
Requirements for IntranetWare Client for Windows NT
Before installing IntranetWare Client for Windows NT, ensure that your workstation and server meet the following hardware and software requirements:
Workstation
An Intel-based computer which meets the hardware and software requirements of Microsoft Windows NT 3.51, 4.0, or above.
The requirements for Windows NT can be found in the Windows NT documentation. If your workstation does not meet the minimum requirements for Windows NT, you should not install the IntranetWare Client for Windows NT.
12 MB of RAM, 16 MB is recommended
A hard disk with 10 MB of free storage space for Novell IntranetWare Client for Windows NT. This does not include the disk space requirements for Windows NT and any other software you might install on your workstation.
A network board installed in your workstation.
For information about installing the network board, refer to the board manufacturer's instructions. Novell IntranetWare Client for Windows NT software supports both Open Data-Link Interface (ODI) and Network Drive Interface Specification (NDIS) drivers.
A cable connection to the network.
Each type of network board requires unique cabling. See the board manufacturer's documentation for requirements. Token-ring network boards require a cable connection to the MAU before you can connect to the network after installing the Novell IntranetWare Client for Windows NT software. Otherwise, the driver will not load.
Server
NetWare 3.11, NetWare 3.12, NetWare 4.1, NetWare 4.11, or later
If you want to support long filenames on NetWare servers, one of the following name space modules should be loaded:
IntranetWare and NetWare 4.11: LONG.NAM
NetWare 3.11 to NetWare 4.1: OS2.NAM
On NetWare 3.11 servers, OS2OPNFX.NLM is also required for long filename support. This NLM is contained in the 311PTG.EXE file that is available on Novell's electronic services worldwide.
In addition, each NetWare volume needs to have the correct name space support (LONG or OS2) added to it via the ADD NAME SPACE console command. Be aware that each name space added to a volume requires additional server memory. If you add name space support to a volume and the server does not have adequate memory, that volume cannot be mounted. For more information about how to calculate the memory required for name space support, see Supervising the Network (for NetWare 4.x) or System Administration (for NetWare 3.x). Each name space also uses up to 252KB of disk space.
A Brief Overview of the SETUPNW Utility SETUPNW.EXE provides a flexible and intuitive means for installing Novell IntranetWare Client for Windows NT software. It allows the user to install the client software without using the Control Panel. SETUPNW.EXE allows you to perform an unattended installation, with options for specifying which template file to use and whether to prompt the user for default information.
SETUPNW also provides a way for the network supervisor to automatically install the client software through the Automatic Client Update (ACU) facility. It can be set to install the Novell Workstation Manager utility as well.
The syntax for SETUPNW.EXE is as follows:
SETUPNW.EXE [/U[:<path to unattended file<]] [/ACU] [/W:<trusted tree name(s)<][/?]
/USpecifies which UNATTEND.TXT file to use as the template for default client functionality. The default UNATTEND.TXT file is used if no alternative is presented with this option. /ACUSpecifies that the install is to check the version stamps of the installed client and the source. If the source is newer, it performs an Automatic Client Update using the defaults. If not all the values can be defaulted, you will be prompted only if absolutely necessary. If /ACU is used in conjunction with the /U option, the defaults are taken from the specified Unattended text file. /WInstalls the Novell Workstation Manager utility for the trees listed. /?Displays quick help information about using SETUPNW.EXE.
What SETUPNW.EXE Does During Installation. As it installs the IntranetWare Client for Windows NT, SETUPNW performs the following actions:
Removes any existing client software, such as the Microsoft Client Service for NetWare.
Installs Novell's IntranetWare Client for Windows NT.
In most cases, SETUPNW automatically detects what type of network adapter driver is installed and configures the IntranetWare Client software accordingly, without requiring user intervention. The IntranetWare Client files are copied to various folders on the workstation's hard disk. See Appendix B in this issue for a full listing.
Replaces Microsoft's logon interface (MSGINA.DLL) with Novell's IntranetWare Client graphical logon (NWGINA.DLL).
Updates the Windows NT system registry with information needed to start IntranetWare Client for Windows NT automatically each time Windows NT starts. See Appendix B in this issue for a listing of registry changes made.
Starting the SETUPNW Program
The procedure for starting the SETUPNW.EXE installation program varies depending on whether you are running it from diskettes, from a local hard disk or network drive, or from a CD-ROM.
From Floppy Diskettes. To run the SETUPNW.EXE installation program from the floppy diskettes, place the first diskette into drive A. From within Windows NT, chose Start | Run, and enter A:\SETUPNW.EXE. You can then follow the steps given in the first example below for a network server-based installation. The main difference is that you will be prompted throughout the procedure to insert the required diskettes.
From a Local Disk or Network Drive. The SETUPNW.EXE installation program is located in the \I386 subdirectory under the directory in which you extracted the IntranetWare Client for Windows NT files. Go to the directory in which you extracted the files, change to the\I386 subdirectory and type SETUPNW <Enter< (or double-click SETUPNW.EXE if you are browsing My Computer, Network Neighborhood, or Windows NT Explorer) to run the installation program. Then follow the steps given in the first example below to complete the installation procedure.
From the IntranetWare Client Suite CD-ROM. You can run the SETUPNW.EXE installation program directly from the Novell Integration Products for Windows NT & IntranetWare Client Suite CD-ROM (Part Number 132-017578-003, available in mid-May) by changing to the \PRODUCTS\WINNT \I386 subdirectory and running SETUPNW.EXE.
You can also run the SETUPNW.EXE program using the graphical interface provided on the CD-ROM. (This interface requires QuickTime to run certain multimedia elements and an Envoy Viewer to view documents. Both QuickTime and the Envoy Viewer are included on the CD-ROM. Refer to the README.TXT at the root of the CD-ROM for additional information.) To load the interface, run the CLIENTS.EXE program from the root of the CD-ROM. Once the "IntranetWare Clients" screen is displayed, click on Windows NT | Client Install | Install to install the IntranetWare Client. Follow the steps given in the first example below to complete the installation procedure.
Attended Installation Examples
This section presents several examples of running an attended installation of the IntranetWare Client for Windows NT (one in which user intervention is required).
Installing IntranetWare Client for Windows NT over the Microsoft Client Service for NetWare
First, we will describe how to install IntranetWare Client for Windows NT on a computer that already has Windows NT installed with the Microsoft Client Service for NetWare (CSNW) enabled. These steps assume you have already obtained the IntranetWare Client for Windows NT software and have followed the preparatory procedures described above. They also assume you will be running SETUPNW.EXE from a NetWare server. (Once you start the SETUPNW program, the procedure is very similar whether you are running it from a server, from a local hard disk, or from a CD-ROM. If you run the program from diskettes, you will be prompted to insert the required diskettes throughout the procedure.)
The exact procedure may vary from the steps outlined below, depending on what type of network adapter you have installed in the workstation and how it is configured.
Start Windows NT on the computer on which you want to install the IntranetWare Client for Windows NT. Verify that Microsoft's Client Service for NetWare is loaded by right-clicking on Network Neighborhood, selecting Properties from the menu, and then clicking on the Services tab of the Network dialog box. "Client Service for NetWare" should be listed as an installed service, as shown in Figure 1.
Figure 1: Verifying that Microsoft's Client Service for NetWare is installed.
The SETUPNW program will completely remove the Microsoft Client Service for NetWare. Once you have verified that the Microsoft Client Service for NetWare is installed, click on OK.
Start the IntranetWare Client for Windows NT SETUPNW.EXE program. Follow the instructions given under "Starting the SETUPNW Program" above for the type of installation you are running.
This example assumes that you are running SETUPNW from a NetWare server that the workstation is connected to through the Microsoft Client Service for NetWare. Drive H is mapped to the SYS:PUBLIC directory on that server.
Instead of using the Windows NT Start button, another method is to double-click on the following icons:
My ComputerDrive HClient folderWinnt folderI386 folderSETUPNW program
To start SETUPNW in this example, click on the Windows NT Start button and select Run. Type in the full directory path to where the IntranetWare Client for Windows NT installation files were copied. The SETUPNW.EXE file is in the \I386subdirectory:
H:\PUBLIC\CLIENT\WINNT\I386\SETUPNW.EXE
Press <Enter< or click on OK to continue.
After you consent to the software license agreement, you are notified that the Microsoft Client Service for NetWare will be removed, as shown in Figure 2.
Figure 2:Remove Microsoft Client Service for NetWare.
Click Yes to continue. While SETUPNW removes the existing client information from the Registry database, adds the new IntranetWare Client keys to the Registry, and copies the necessary files to the workstation, a window similar to the one shown in Figure 3 is displayed:
Figure 3: SETUPNW informs you of the installation program's progress.
See Appendix B in this issue for a listing of files copied and Registry keys changed during the IntranetWare Client installation.
Once the Registry keys have been updated and all files have been copied correctly, you will see the dialog box shown in Figure 4:
Figure 4: After the Client is installed, you must reboot the workstation for the changes to take effect.
At this point, you can either close the installation program or reboot the workstation. After rebooting the workstation, you should see a new IntranetWare Client window instructing you to press "Ctrl+Alt+Delete" to log in. After you press these keys, the Novell NWGINA login interface is displayed. See the AppNote entitled "Accessing IntranetWare Resources with NWGINA and the NetWare Provider" in this issue for additional information on logging in.
Upgrading from a Previous Version of the Novell Client for Windows NT
This next installation example describes the process of upgrading to the current version of the IntranetWare Client for Windows NT from a workstation running a previous version of the Novell Client for Windows NT.
These instructions assume you have the Novell NetWare Client for Windows NT installed on the Windows NT workstation. The exact procedure my vary from the steps shown below, depending on what type of network adapter you have installed and how it is configured.
At the workstation running Windows NT and the NetWare Client for Windows NT, log in to a NetWare server that has a copy of the IntranetWare Client for Windows NT installation files.
(Optional) Right-click on Network Neighborhood and select Properties from the resulting menu. Click on the Services tab to verify that "Novell NetWare Client for Windows NT" is listed as a network service, as shown in Figure 5.
Figure 5: Verifying that the Novell NetWare Client for Windows NT is installed.
Once you have verified that the Novell NetWare Client for Windows NT is installed, click on OK.
Start the SETUPNW.EXE program. To do this, click on the Windows NT Start button and select Run. Type the full directory path to where the IntranetWare Client for Windows NT installation files were copied. The SETUPNW.EXE program is in the \I386 subdirectory. For example, if drive H is mapped to the SYS:PUBLIC directory on that server, type:
H:\PUBLIC\CLIENT\WINNT\I386\SETUPNW.EXE
Another method is to click on the Browse... button and select each directory level one at a time until you see the SETUPNW icon. Double-click the SETUPNW icon to return to the Run dialog box.
When the correct path and filename appear in the entry box, press Enter or click OK to run the SETUPNW program.
The Novell IntranetWare Client Installation welcome dialog is displayed, as shown in Figure 6.
Figure 6: The IntranetWare Client Installation "welcome" dialog box.
To proceed with the installation process, click on Continue.
While SETUPNW removes the existing client information from the Registry database, adds the new IntranetWare Client keys to the Registry, and copies the necessary files to the workstation, a progress window (similar to the one shown in Figure 3 earlier in this AppNote) is displayed
Once the Registry keys have been updated and all files have been copied correctly, you will see the dialog box shown in Figure 7:
Figure 7: After the IntranetWare Client is installed, you must reboot the workstation for the changes to take effect.
At this point, you can either close the installation program or reboot the workstation. After rebooting the workstation, you should see a new IntranetWare Client window instructing you to press "Ctrl+Alt+Delete" to log in. After you press these keys, the Novell NWGINA login interface is displayed. See the AppNote entitled "Accessing IntranetWare Resources with NWGINA and the NetWare Provider" in this issue for additional information on logging in.
Installing from the Windows NT Network Control Panel
As a final example of attended installation, you can install the IntranetWare Client for Windows NT from the Network icon in the Windows NT Control Panel. This method does not use the SETUPNW utility.
Log in to the Windows NT workstation as an NT user who is a member of the Administrators group.
From the Start menu, choose Settings.
Choose Control Panel | Network and click on the Services tab.
Click on the Add button.
Click on Have Disk.
Enter the path to the IntranetWare Client for Windows NT installation files on the CD or network.
For example, if you have the IntranetWare CD and your CD-ROM drive is drive D, make sure the CD is in the drive and enter
D:\I386
Click on OK.
From the "Select OEM Option" dialog box, choose Novell IntranetWare Client for Windows NT and click on OK. The IntranetWare Client software and a network adapter driver will be installed on the workstation.
If a network adapter driver is not installed, you must install a LAN driver before you can establish a network connection.
After the IntranetWare Client for Windows NT is installed in this fashion, you must configure it. See the AppNote entitled "Configuring the IntranetWare Client for Windows NT" for information on IntranetWare Client configuration settings.
Upgrading Windows NT Workstations with ACU
In the past, when Novell released updates to the Novell client software, network administrators had to go to each workstation and manually upgrade the client software. To reduce this administrative burden and make it easier to distribute and install Novell client software, Novell has developed the Automatic Client Update (ACU) process to automate the process of upgrading Novell client software for users.
Overview of the ACU Process
Novell's Automatic Client Update (ACU) process for Windows NT workstations provides a way to automatically upgrade Novell IntranetWare Client for Windows NT software. In a typical scenario, the administrator places instructions in a login script to run the SETUPNW.EXE program--with the /ACU option added--if certain update conditions are met. Once the login script is set up properly and a special ACU installation directory is created on the server, ACU automatically upgrades the client software when users log in, without requiring any intervention from the user or the administrator.
SETUPNW /ACU uses version numbers to determine whether the client needs to be upgraded. ACU compares the version number of the currently installed client (stored in the Windows NT Registry) with the version number of the new client in the ACU installation directory. If the new client software version number is greater than the currently installed client version number, SETUPNW.EXE continues and installs the latest version. If the new client software version number is not greater, SETUPNW exits without installing any new software.
In addition to the version numbers mentioned above, the administrator can set a pair of internal version numbers in the UNATTEND.TXT file. These internal version numbers enable you to update the client software when, for example, network changes make it necessary to modify the client configuration even if the actual client version has not changed. See the section on "Updating Individual Files with ACU" below for more information.
You should consider the following points before using ACU:
The ACU process, like any other IntranetWare Client for Windows NT installation procedure, requires that the user doing the installation have NT Administrator privileges on the workstation where the client software will be installed. However, once the IntranetWare Client for Windows NT is installed with the Workstation Manager component, Workstation Manager will allow subsequent client updates to be made without this requirement.
You can run SETUPNW /ACU from any login script or profile script, provided that the proper drives are mapped and that all paths and filenames are specified using Universal Naming Convention (UNC) style (\\server\volume\path\filename).
Running SETUPNW /ACU
To install or upgrade the IntranetWare Client for Windows NT software using the Automatic Client Update (ACU) option, follow these steps:
Create an ACU installation folder where the Novell client software will be installed from.
In order for the Automatic Client Upgrade to work, the workstation needs access to a folder where all the client installation files are stored. To make this happen, the network administrator needs to do the following:
On a NetWare server, create an ACU install folder that can be accessed by all users to be upgraded. For example, create a directory called NT41ACUin the SYS:PUBLIC\CLIENT directory. Users need at least Read and File Scan rights to run SETUPNW.EXE. Placing the files in a subdirectory of SYS:PUBLIC ensures users will have those rights by inheritance.
Copy all the IntranetWare Client for Windows NT installation files into this ACU install folder.
Make sure that all clients scheduled for automatic upgrade have Read and File Scan rights to the ACU install folder. If you have created the ACU install directory somewhere other than under SYS:PUBLIC, you will have to manually assign these rights using the NetWare Administrator utility.
Modify the appropriate login script.
Depending on which login script is modified, the network administrator can allow different clients to upgrade.
If a user login script is modified, only that user will automatically upgrade.
If a container login script is modified, all users in that container can automatically upgrade.
If a profile login script is modified, all users using that profile login script can automatically upgrade.
Again, make sure that all clients running the Automatic Client Upgrade have Read and File Scan rights to the ACU folder you created in Step 1. Once this is done, add a command similar to the following at the beginning of the login script:
#\\servername\volume\...\setupnw.exe /acu
If your network has various Novell client platforms, you can use the OS or the PLATFORM identifier variable to distinguish Windows NT clients from other Windows clients. As an example, you could add the following lines to the login script:
IF OS = "WINNT" THEN #\\servername\volume\...\setupnw.exe /acu END
or
IF PLATFORM = "WNT" THEN #\\servername\volume\...\setupnw.exe /acu END
Note: The PLATFORM identifier variable is supported by the Novell Login(GUI Login) for Windows 3.x, Windows 95, and Windows NT, but it is not supported by the DOS LOGIN.EXE utility or the MicrosoftLogin utility. Any users running the DOS LOGIN.EXE utility mayget an error if the PLATFORM variable is encountered during theexecution of the login script. To avoid this problem with theDOS LOGIN.EXE utility, modify the above IF statement as shown:
IF "%PLATFORM" = "WNT" THEN#\\servername\volume\...\setupnw.exe /acuEND
If you want to configure the client with preset parameters, add the /U option to the login script command. This allows SETUPNW to set the client's configuration options according to the settings contained in the UNATTEND.TXT file. For example, the following command installs Novell IntranetWare Client for Windows NT using the ACU and the Unattended configuration options listed in the default UNATTEND.TXT file:
#\\servername\volume\...\setupnw.exe /acu /u
The unattended installation options are discussed later in this AppNote.
Have users log in to IntranetWare/NetWare.
If the IntranetWare Client is not yet installed, users will need to initially log in to IntranetWare using the Microsoft Client Service for NetWare.
When users log in to IntranetWare, the login script will run the SETUPNW /ACU command, and the Novell IntranetWare Client for Windows NT will be installed, provided the new client software version number is greater than the currently installed client version number.
Updating Individual Files with ACU
In some cases, you may want to update one or more individual files without upgrading the entire client. For example, suppose Novell releases a new version of a file and you decide that all your Windows NT clients need to use the additional functionality provided in this updated file. Because this isn't a new version of the IntranetWare Client for Windows NT, there isn't a client revision number for ACU to check. However, you can force the ACU process to run so that all users automatically receive the newer file when they log in.
In the UNATTEND.TXT file used for the unattended install (located in the \I386\NLS\<language< folder), there are two "internal" version number parameters:
Major Internal Version
Minor Internal Version
These version parameters can be any integer from 0 through 4,294,967,295. SETUPNW /ACU uses these version numbers to determine when to upgrade the client software. If either number is greater than the corresponding number stored in the Registry, the configuration settings in the UNATTEND.TXT file are written to the Registry and this number is stored as the new version number. Otherwise, no Registry changes are made. The first time the IntranetWare Client for Windows NT software is installed, no internal version numbers exist in the Registry. In this case, the internal version numbers are written to the Registry when the client is installed using the SETUPNW /U command.
To force an upgrade, increment either internal version number in the UNATTEND.TXT file so that it is higher than it used to be (for example, if the minor version number was 0, make it a 1). When ACU compares the version numbers upon user login, it detects the change and upgrades the workstation with the newer files.
Here is an example of how the UNATTEND.TXT file could be modified:
[NovellNetWareClientParameters] !MajorInternalVersion = 0 !MinorInternalVersion = 1
When SETUPNW /ACU compares the installed version with the version numbers specified above, it will determine that the installed client is older and will then proceed to update the client software.
The registry settings for these version numbers are stored in the following location:
MyComputer
HKEY_LOCAL_MACHINE
SOFTWARE
Novell
NetWareWorkstation
CurrentVersion
Within CurrentVersion, the following version identifiers are listed:
MajorVersion MinorVersion MajorInternalVersion MinorInternalVersion
Currently, MajorVersion has a value of 4 and MinorVersion has a value of 10. The values of MajorInternalVersion and MinorInternalVersion depend on the values set in the UNATTEND.TXT file. After SETUP /ACU is run, these values are changed to match those set in UNATTEND.TXT.
SETUPNW checks the version numbers in the order in which they are listed above. It first checks the MajorVersion and then the MinorVersion. If they match, SETUPNW proceeds to check the MajorInternalVersion and then the MinorInternalVersion.
Unattended Installation Examples
This section presents several examples of running an unattended installation of IntranetWare Client for Windows NT (one in which no user intervention is required). Unattended installations can save you time and reduce the administrative costs of installing IntranetWare Client software if you have a large number of workstations.
Overview of the UNATTEND.TXT File
Microsoft supplies a default preconfiguration file named UNATTEND.TXT with Windows NT. Novell includes its own version of this file with the IntranetWare Client for Windows NT software. You should use the Novell version instead of the one from Microsoft. The Novell version includes all of the options in the Microsoft version, but it adds parameters specific to the IntranetWare Client for Windows NT.
By specifying default values for client configuration settings in the UNATTEND.TXT file, you can simplify the installation of the IntranetWare Client for Windows NT. If you install the client software from an IntranetWare server, you can configure multiple workstations simultaneously using the same UNATTEND.TXT file. The UNATTEND.TXT file uses the Windows NT .INF file syntax. This configuration method is ideal for network administrators who want to install and configure the IntranetWare Client for Windows NT at the same time, who need to configure settings that can't be configured using the System Policy Editor, and who are somewhat familiar with the Windows NT .INF file syntax.
|
Note: Because complete standardization across a large organization is not always possible, more thanone Unattended text file may be created, each with specific parametersettings that will match the configurations for a particular groupof workstations. |
Where Is the UNATTEND.TXT File? Novell's UNATTEND.TXT file is located in the following directory on the IntranetWare Client installation CD-ROM:
drive: \I386\NLS\<language<
For example, if your CD-ROM drive is drive D and the language is English, the full path to the file is:
D:\I386\NLS\ENGLISH\UNATTEND.TXT
If you are installing the client software from diskette, UNATTEND.TXT is on the first diskette in the \NLS\ENGLISH directory.
What's In the UNATTEND.TXT File? The UNATTEND.TXT file that Novell supplies is a self-documenting file. It contains information about each parameter, including the default value and the range of values, as well as a brief explanation of what each parameter does. To change or set a parameter, read about the parameter in the UNATTEND.TXT file and then set the parameter value accordingly. If the parameter is commented out (has a semicolon at the beginning of the line), you will need to remove the semicolon to set the parameter.
If a parameter is precededby an exclamation point (!), do not remove it. The UNATTEND.TXTfile is an NT .INF file in which global INF variables are identifiedby a ! preceding them.
Before you attempt to edit the UNATTEND.TXT file, you should be familiar with the settings that are supported by Novell's IntranetWare Client for Windows NT. Some parameters from previous NetWare clients are no longer supported, other parameters have been changed, and new parameters have been introduced.
The Novell version of the UNATTEND.TXT file contains several sections that are relevant to installing the IntranetWare Client for Windows NT. These are described below, based on the the current version of the UNATTEND.TXT file (IntranetWare Client v4.10).
|
Note: For readability, spaces have been inserted between words in the parameter names; default values, if any, are also shown. |
[SetupNWInstallOptions] Section. This section contains parameters that allow you to preconfigure answers to the questions asked in the dialog boxes that are normally displayed during the SETUPNW.EXE program. By default, these parameters are set so that the initial screen and reboot prompt are not displayed. This is especially helpful if you are installing the IntranetWare Client for Windows NT on several workstations and you don't want the users to be able to overwrite your configuration choices.
Display Initial Screen=NO (if set to YES, the initial Welcome or ACU Upgrade screen is displayed)
Ask Reboot=NO (if set to YES, the final dialog telling the user that the computer needs to be rebooted is displayed)
[NovellNetWareClientParameters] Section. This section allows you to determine which other dialog boxes are displayed during IntranetWare Client for Windows NT installation, and preconfigure answers to various prompts users would normally encounter.
Major Internal Version=0 Minor Internal Version=0 Accept License Agreement=NO Ask Remove MS NetWare Client=NO Remove MS NetWare Client=YES Use NetWare GINA=YES Ask NetWareIP=NO Install NetWareIP=NO
Novell Client Services Parameters Section. This section, which is actually a continuation of the [NovellNetWareClientParameters] section, contains parameters used to configure the client. Nearly all of these parameters can also be set in the Control Panel. However, setting them in UNATTEND.TXT before installation makes it possible to configure multiple workstations with the same parameters during installation, eliminating the need to configure them on each individual workstation.
All of the parameters on the IntranetWare Client and NetWare/IP property pages are included in the Novell UNATTEND.TXT file. Each parameter listed in this section has an overwrite option. If the overwrite option is set to NO, the value is updated only if it does not already exist in the Registry. If it is set to YES, the value is updated regardless.
The configuration parameters are listed below in the order in which they appear in the current version of the UNATTEND.TXT file:
Preferred Server Preferred Bindery Server Preferred Tree Tree and Default Context First Network Drive Display Connection Page Login to Tree Login to Server Bindery Connection Clear Current Connections Display Script Page Login Script Profile Script Display Results Close Script Results Automatically Run Scripts Display Variables Page Save Settings When Exiting Login Policy Path NetWare Storage Of Roaming Profiles Storage Type File System Pointer Path Bitmap Filename Welcome Screen Caption Receive Broadcast Messages DOS Name Large Internet Packets (LIP) LIP Start Size Long Machine Type LSL Max Buffer Size Minimum Time To Net Opportunistic Locking Burst Mode PBurst Read Window Size PBurst Write Window Size Signature Level Short Machine Type Remote Configuration NWIP Domain Name Auto Retries Auto Retry Seconds NSQ Broadcast NWIP 1.1 Compatibility Use Custom Port Port Number Nearest NWIP Server Preferred DSS Enable Workstation Manager Workstation Manager Trusted Trees
Each of the above parameters is documented in the UNATTEND.TXT file itself and in the online help for IntranetWare Client for Windows NT. For additional configuration information, see the AppNote entitled "Configuring IntranetWare Client for Windows NT"in this issue.
Installing IntranetWare Client for Windows NT Using UNATTEND.TXT
You can install Novell IntranetWare Client for Windows NT on multiple workstations by using the unattended install feature. This feature can significantly reduce the time and effort required to install and configure NT workstations. Remember that all workstations being configured with the same UNATTEND.TXT file should have identical configuration requirements.
To perform a manual unattended install, follow these steps:
Copy the IntranetWare Client for Windows NT installation files to the network.
Open the Novell IntranetWare Client for Windows NT UNATTEND.TXT file.
The UNATTEND.TXT file is located in the I386\NLS\<language< directory once the network version of the installation files is extracted, or in the NLS\<language< directory on the first installation diskette.
Edit UNATTEND.TXT to set your preferences.
By default, all Novell IntranetWare Client for Windows NT parameters are commented out with a semicolon. Remove the semicolons from any parameters you want to change and edit the parameter settings. Do not remove any exclamation points (!) that precede any of the parameters. These parameters will then be set automatically during the installation of the client software.
Save the UNATTEND.TXT file.
You can save the file with any filename you want to use. For example, you could rename the file to NOVELL.TXT and save it in the SYS:PUBLIC\ NTCLIENT directory.
At each workstation on which the IntranetWare Client is to be installed, log in to the network.
To start the IntranetWare Client installation,enter the following command at the command line:
SETUPNW /u:<path to unattend file<
For example:
SETUPNW /u:f:\public\ntclient\novell.txt
The IntranetWare Client software will be installed and configured on each workstation according to the settings in your edited NOVELL.TXT file. As stated previously, this process can be automated by using the /ACU parameter. For example:
SETUPNW /acu /u:f:\public\ntclient\novell.txt
Installing Both Windows NT and IntranetWare Client for Windows NT
You can perform an unattended installation of both Windows NT and Novell's IntranetWare Client for Windows NT at the same time. This can save a tremendous amount of time if you are installing the software on a number of workstations.
Copy the Windows NT CD to an existing server on the network.
Refer to your Windows NT documentation for more information.
Under the \I386 directory, make a subdirectory called $OEM$.
Under the \$OEM$ directory, make a subdirectory called NET.
Under the \NET directory, make another directory to hold the IntranetWare Client software.
You can name this directory whatever you want. For example, you might want to name the directory based on the date of the version you're installing or the name of the group you are installing for. In this example, this directory is called NTCLIENT.
Open the Windows NT UNATTEND.TXT file.
The Windows NT UNATTEND.TXT file is located in the \I386 directory on the Windows NT 4.0 installation disk, whether you are using a CD or the network.
In the [Network] section, add or configure the following line:
InstallServices = ServicesList
At the end of the UNATTEND.TXT, add or configure the following lines:
[ServicesList]NWFS = NovellNetWareClientParameters,\$OEM$\NET\NTCLIENT
If you named the directory in Step 4 something other than NTCLIENT, substitute that name for NTCLIENT in the above example.
Save the Windows NT UNATTEND.TXT file.
You can name the file anything you want and save it in any directory you'll be able to access when you run the installation program. For this example, the file is named NOVELL.TXT and is saved in the NTCLIENT directory.
Copy the Novell Client files to the network.
Copy or extract the files to the same directory you created in Step 4 ("NTCLIENT" in this example).
Open the default Novell IntranetWare Client for Windows NT UNATTEND.TXT file.
This file is located in the I386\NLS\<language< directory once the network version of the Client installation files is extracted.
Highlight and copy the entire contents of the [NovellNetWareClientParameters] section in this UNATTEND.TXT file and paste them into the end of the document you created in Steps 5 through 8 (NOVELL.TXT in this example).
Edit NOVELL.TXT (or whatever you named your file) so that your preferences are configured.
By default, all Novell IntranetWare Client for Windows NT parameters are commented out with a semicolon. Remove the semicolons and edit the parameter settings you want to set when you install Novell IntranetWare Client for Windows NT.
Save the file.
Log in to the network from each of the new computers. They should be able to access the server on which you copied the installation files.
To start the installation, change to the directory on the Windows NT installation disk where WINNT.EXE is located, and then enter the following on the command line from the Windows NT installation directory:
WINNT /s:{source path> /b /u:>path to unattend file>For example:
WINNT /s:f:\i386 /b /u:f:\public\winnt40\i386\$oem$\net\ntclient\novell.txt
Uninstalling the IntranetWare Client for Windows NT
To uninstall the IntranetWare Client for Windows NT, you simply remove it via the Windows NT Network Control Panel. No separate uninstall utility is needed. The steps are as follows:
In Windows NT, select Control Panel | Network.
Select the Services tab.
Select Novell IntranetWare Client for Windows NT.
Click the Remove button. This will completely remove the IntranetWare Client for Windows NT software.
* Originally published in Novell AppNotes
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.