Installing Clients from the Network

You can install Novell Client software on multiple workstations from the network by copying files to the server and modifying the login script. This installation is sometimes referred to as an Automatic Client Upgrade (ACU).

HINT:  You can install the Novell Client using the Application Launcher component of ZENworks. Application Launcher lets you distribute applications such as the client software to workstations and manage those applications as objects in the NDS tree. For more information, see the ZENworks for Desktops documentation.

On Windows XP, you can install the client software from the network on workstations running the Microsoft Client Service for NetWare. Run the install by logging into the server using bindery emulation.

You can install and upgrade the client software on all platforms when users log in. The process involves six tasks:

  1. Creating a folder on the server.
    2.
  2. Copying Novell Client files and other required files to the new folder. Workstations can then read the files during login.
    3.
  3. Granting rights to the new folder.
    4.
  4. Modifying the ACU configuration file.
    5.
  5. (Optional) Creating or update the platform-specific configuration files.
    6.
  6. Creating or modifying the login script. (A sample login script is included.)
    7.

When the login script runs, ACU.EXE determines if the client needs to be upgraded. This initial check saves network bandwidth during login because the setup utility is run only if the client needs to be updated.


Creating a Folder

  1. Log in to a server as Admin or as a user with Admin equivalence.

    Make sure that you have rights to copy files to a network folder that all users can access, as well as rights to modify login scripts.

    2.

  2. Create a folder in SYS:PUBLIC.

    For example:

    SYS:\PUBLIC\CLIENT

    3.

Copying Files

  1. Do one of the following:

    • From the Novell Client CD, copy the WINNT or WIN95 directories to the new folder.

      If you are installing only one platform, you need to copy only the platform directory (WINNT or WIN95) for the platform you will install.

      If you are installing the client in only one language or if your network does not have enough space to accommodate multiple language directories, you can delete the language directories that you do not need from the NLS directory under each client directory. To ensure that you have all necessary files, copy the entire client directory and then delete only the extra language directories.

      •

    • Copy the downloaded Novell Client software files to the new folder.

      See Downloading the Latest Client Software.

    2.

  2. (Conditional) If you are installing Novell Client for Windows 95/98, copy the Windows 95 and/or Windows 98 .CAB files to the WIN95 directory.

    The files are on the Microsoft Windows 95 or Windows 98 CD (and Upgrade CD) in the respective WIN95 or WIN98 folder.

    3.

Granting Rights

  1. Create a Group object in the NDS tree.

    2.

  2. Place into that group users whose workstations need to be installed or upgraded.

    3.

  3. Make sure that the group has the Read and File Scan rights to the folder that you created.

    If you created a folder in SYS:PUBLIC, the new folder should have Read and File Scan rights already associated with it, but you should make sure that these rights have not been changed.

    4.

  4. (Conditional) If you want the results of the installation to be added to a status log file, make sure that the group has the Write right to that file.

    A status log file records the success or failure of the installation. As each workstation completes its installation, the status log file is appended to include information on that workstation. Enable status logging in the ACU configuration file.

    If you did not create the status log file prior to running the network installation, you must give users the Create and Write rights to the directory.

    5.

Modifying the ACU Configuration File

The Automatic Client Upgrade utility (ACU.EXE) determines whether the client needs to be updated and allows you to specify several installation options.

Option Description Settings

[LAUNCHINSTALL]

Specifies whether the platform-specific setup utility will be launched once ACU.EXE determines that the installation is necessary.

Launch=Yes | No
(default: Yes)

[DISPLAYDIALOG]

Specifies whether users will be prompted to begin the upgrade.

Display=Yes | No
(default: Yes)

[UNATTENDFILE]

Specifies whether a platform-specific configuration will be used and where it is located.

Use=Yes | No
(default: No)

File=configuration_file_path

[STATUS LOGGING]

Specifies whether a status log will be created and where it will be located.

If you did not create a status log file prior to installation, it will be created and placed in the installation directory on the network or in the directory specified in the File setting.

Use=Yes | No
(default: No)

File=log file path

[ADMINISTRATORMESSAGE]

Specifies additional text that will appear when the user is prompted to start an ACU.

Message=the message you want to appear

[CLIENTLOCAL
INSTALL]

Specifies whether the installation will be copied to a specified local directory and run locally.

LocalInstall=Yes | No (default: No)

LocalDirectory=directory where you want the installation copied
(default: C:\Novell\ClientLocalInstall)

DeleteLocalInstall=Yes | No (default: No)

HINT:  If you want to delete the files after the installation is complete, set the DeleteLocalInstall parameter to Yes.

To customize ACU, do the following:

  1. Open the ACU.INI file located in the folder that you created on the server.

    2.

  2. Modify the configuration options.

    3.

IMPORTANT:  We recommend that you use the ACU.INI file instead of the command line switches used in previous versions of Novell Client. ACU.INI simplifies the installation process. If you choose to use switches, they will override ACU.INI options.


Updating the Platform-Specific Configuration Files

NOTE:  If you are installing the client with the default settings, you do not need to create or modify the configuration files. Skip this process and proceed to Setting Client Properties.

IMPORTANT:  If you use a platform-specific configuration file to configure Novell Client and you are using ACU.EXE, you must change the [UNATTENDFILE] option to Yes in the ACU.INI file.

Each platform-specific installation utility reads a configuration file generated by Novell Client Install Manager in order to configure the client properties. This file provides information such as where to copy drivers during installation and the most recent version number. This file must be placed in the same folder as the installation utility.

IMPORTANT:  If you are configuring Windows 95/98 workstations, options that were set in the NWSETUP.INI file or on the command line in previous versions of Novell Client (such as Display First Screen or CAB FIX) are now set up in Novell Client Install Manager.

To create a configuration file, do the following:

  1. Start Novell Client Install Manager (NCIMAN.EXE).

    Windows 95/98: Novell Client Install Manager is located in the WIN95\IBM_language \ADMIN folder that you copied to the server.

    Windows NT/2000/XP: Novell Client Install Manager is located in the WINNT\I386\ADMIN folder that you copied to the server.

    2.

  2. Click File > New, select the platform, and then click OK.

    3.

  3. Modify the installation options as needed.

    1. In the Installation Options list box, double-click the configuration option that you want to modify.

      2.

    2. In the property pages, set the parameters and then click OK.

      The values that you set appear in the right list box.

      3.

    HINT:  You can import the settings from a workstation that has been previously configured and save them to the configuration file. Once you set up the workstation, click File > Import Registry to import the settings.

    4.

  4. Click File > Save.

    You can use any filename (for example, UNATT_95.TXT or UNATT_NT.TXT).

    5.

  5. Copy this file to one of the following directories:

    Windows 95/98: WIN95\IBM_language

    Windows NT/2000/XP: WINNT\I386

    IMPORTANT:  The path to the text file cannot contain long filenames.

    6.

Creating or Modifying the Login Script

You need to modify login scripts for users whose workstations will be upgraded.

To upgrade workstations for users in a container, modify that container's login script.

To upgrade workstations for users in a profile, modify that profile's login script.

To upgrade specific users' workstations, modify those users' login scripts.

To upgrade a workstation running bindery-based client software (such as Microsoft Client for NetWare Networks which ships with Windows 95 or Windows 98), edit the system login script (SYS:PUBLIC\NET$LOG.DAT).


Creating or Modifying a Login Script Using ConsoleOne

  1. Double-click the object whose login script you want to create or modify.

    2.

  2. Click Login Script.

    3.

  3. Enter the login script commands and information into the login script text box.

    For a sample of the login script commands that you need to add to the scripts, see Sample Client Installation Login Script.

    IMPORTANT:  Make sure that you edit the sample login script to match the server names, directory paths, and specifications of your own network.

    For additional information on all login script commands, see Login Script Commands and Variables.

    4.

  4. To save the login script and close the Details dialog box, click OK.

    If the login script that you just created was a container or user login script, you're finished and the client software will be installed or updated the next time users log in.

    If the login script that you just created was for a Profile object, you must associate the User object with the Profile object and make the User object a trustee of the Profile object.

    For additional information on all login scripts, see Creating or Modifying Login Scripts.

    5.

Sample Client Installation Login Script

The following sample shows the commands that you add to the login script in order to install the client software from the network. The sample includes text for installing across an internal network.

HINT:  In this sample, the text that is necessary to the script is represented in uppercase letters. The information that you should customize for your network is in lowercase letters.

REM *****  Windows 95/98 *****
IF (OS = "WIN95") OR (OS = "WIN98" AND OS_VERSION <> "V4.90") THEN
   WRITE "Updating Novell Client for Windows 95/98."
   #\\server1\sys\public\client\win95\ibm_enu\acu.exe
   IF "%ERROR_LEVEL" = "1" THEN
        EXIT
   END
END

REM ***** Windows NT/2000/XP *****
IF OS = "WINNT"
   WRITE "Updating Novell Client for Windows NT/2000/XP."
   #\\server1\sys\public\client\winnt\i386\acu.exe
   IF "%ERROR_LEVEL" = "1" THEN
        EXIT
   END
END

NOTE:  If you are using this sample script to replace the Microsoft Client with Novell Client for Windows95/98, some user intervention is necessary. Due to Microsoft Client's limited scripting capabilities, users must close an open DOS box before the workstation is rebooted and the installation is completed.


What Users See

If this is a new client software installation, or if it is an upgrade from older client software, the software is installed or upgraded when users log in and restart the workstation. Users might see system messages as their workstations are upgraded, depending on how you set up the installation.



Previous | Next