4.3 Novell Client Installation Procedures

This section contains detailed information about the specific procedures required to complete various types of network server and Web server installations of the Novell Client. Because each of these procedures might apply to several installation types, each process is described separately. For more information on how to combine these procedures into a complete installation solution, see Section 4.2, Understanding Which Installation Process to Use.

4.3.1 Setting Up the Novell Client Install on a NetWare Server

  1. On a NetWare server, 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. Create a folder in sys:public.

    For example:

    sys:\public\client

  3. Copy the contents of the directory where you unzipped the download file to the folder.

    See Section 2.4, Locating the Latest Client Software.

    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.

  4. Create a Group object in the eDirectory tree.

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

  6. 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.

  7. (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 and enable status logging in the acu.ini or cuagent.ini file (see Modifying the ACU Configuration File or see Creating the Configuration File (Unattend 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.

    A status log file records the success or failure of the installation. when each workstation completes its installation, the status log file is appended to include information on that workstation.

  8. Complete any additional procedures outlined in the installation type you selected.

    For more information on selecting the type of installation needed, see Section 4.2, Understanding Which Installation Process to Use.

4.3.2 Setting Up the Novell Client Install on a Web Server

Before you can distribute the Novell Client from a Web Server, you must first set up the installation directory on the Web server.

  1. Create an installation directory on the HTTP Web server where you want users to install from.

  2. Do one of the following:

    • Full Novell Client Installs or Upgrades: Copy the context of the directory where you unzipped the download file to this directory. For more information on locating the latest Novell Client software, see Section 2.4, Locating the Latest Client Software.

    • For Support Pack Installs: Create the following directory structure:

      \sp

      and place the Support Pack files in that sp directory.

      The IP address specified in the WriteIP utility must be a location on a Web server that contains the Support Pack files. If the IP address specified in the WriteIP utility is a location on a Web server that contains both the client and the Support Pack files (in an overlay), both the client and Support Pack files are downloaded; however, only the Support Pack install launches. Creating a directory called sp and placing the Support Pack files in that sp directory avoids unnecessary download of Client files. The Web download utility downloads only the files in the sp directory and launches the Support Pack install.

      You can copy the files to up to five different Web servers in order to provide access during peak times.

      IMPORTANT:Ensure that you preserve the case, date, and time of the directories and files that are copied to the Web server. This is especially important on Web servers that are case sensitive, such as Linux servers.

  3. Complete any additional procedures outlined in the installation type you selected.

4.3.3 Creating the setupip.exe Download Executable

You can install the Novell Client software from a Web server. Using the WRITEIP utility, you can create a small executable called setupip.exe that downloads the Novell Client install files from a Web server and launches the Novell Client install.

  1. Run the writeip.exe utility located in the admin directory in the directory where you unzipped the download file.

    For more information on downloading Novell Client, see Section 2.4, Locating the Latest Client Software.

  2. Specify the IP address or DNS name of the Web server and the path to the client files.

    You can specify up to five locations. Each location is checked in the order in which they are listed until a connection is made. If you select Choose IP Address at Random, the order in which the locations are checked is selected randomly. This balances the load across the Web servers.

    For example:

    http://111.111.11.1/client
    

    or

    http://mycompany.com/client
    
  3. Specify download options, such as the location for downloading the client installation files.

    Files can be downloaded to a temporary or specific directory.

    If you select Allow User to Change the Download Directory, the user is prompted for the location of the download directory and can change the default location.

    If you do not select Delete Install Files after Install Is Compete, the Novell Client installation files remain on the workstation in the specified path or temporary directory.

  4. Specify client install launch options.

    Support Pack Install: Only the Support Pack software is downloaded and installed, if needed. For specific information on setting up the directories correctly on the Web server, see Section 4.3.2, Setting Up the Novell Client Install on a Web Server.

    Automatic Client Upgrade: The client install runs only if the client software is a later version than the one currently installed on the workstation. For more information, see Modifying the ACU Configuration File.

    Unattend File: The installation reads the configuration file in order to configure the client properties. This file should be placed in the same folder as the installation utility. For more information, see Creating the Configuration File (Unattend File).

  5. Click OK.

    Setupip.exe is created. Writeip.ini, which stores the options you selected in writeip.exe, is also created.

  6. Complete any additional procedures outlined in the installation type you selected.

    For more information on selecting the type of installation needed, see Section 4.2, Understanding Which Installation Process to Use.

4.3.4 Distributing setupip.exe

Distribute setupip.exe by placing it on a Web site, sending it through e-mail, or distributing it on a diskette.

When users double-click setupip.exe, the executable downloads the client install files from the specified IP address and launches the Novell Client installation.

setupip.exe determines what language version of the client to install based on the settings in the Regional and Language Options (Windows XP) or the Regional Options (Windows 2000) dialog box in the Control Panel. If the Novell Client supports the language, setupip.exe downloads the /NLS language files for that language. If the Novell Client does not support the language (that is, the /NLS files are not available for download), the copy fails with a message to contact the system administrator. If the language is not supported by the Novell Client, the English /NLS files must be available. For example, this means that you cannot use setupip.exe to force an English language version of the Novell Client onto a workstation with German regional settings.

4.3.5 Setting Up the Novell Client Update Agent

IMPORTANT:This procedure is just one of the tasks required to complete installation of the Novell Client on multiple workstations. For more information on how this procedure combines with other procedures to create an install method, see Section 4.2, Understanding Which Installation Process to Use.

You can simplify future client software upgrades by enabling the Novell Client Update Agent. The Update Agent can be run manually at any time from the Red N menu or can be run automatically when users log in to the network.

If it is run automatically, the Update Agent determines if the preconfigured number of days have elapsed since the last upgrade check and then checks the specified location for a newer version of the client. If a newer version is found, the new install is launched. You can preconfigure the interval of days as well as the location of the newer client version.

IMPORTANT:Before workstations can check to see if updates are available, the Update Agent must be configured during a software installation or by using Automatic Client Upgrade (ACU). Or, you can configure the Update Agent on each machine locally through the Novell Client property pages. For more information, see Section 4.3.7, Enabling the Novell Client Update Agent.

  1. Create a configuration (unattend) file by running the Novell Client Install Manager utility (nciman.exe).

    See Creating the Configuration File (Unattend File).

  2. Click Client, then click the Update Agent tab.

  3. (Optional) Select the Enable Automatic Update Agent option and set the launch interval.

  4. Select the Update Location option and specify the Update Location path (mapped drive, UNC path or URL).

  5. (Optional) Select the Previous Install Location option.

    This causes the previous install location to be used if the update location cannot be found. If the Update Agent should use only the previous install location, deselect the Update Location option.

  6. (Conditional) If the user does not have the Administrator right on the workstation, select the Administrator Rights option.

    Novell Client must be installed by a user that has administrative rights on the workstation. If this option is selected, the Update Agent runs as a user with administrative rights and the installation is completed. If this option is not selected and the user does not have administrative rights, the Update Agent does not run and the user is notified that he or she does not have the correct rights.

  7. To save the file in the correct location, complete the steps in Creating the Configuration File (Unattend File).

  8. Complete any additional procedures outlined in the installation type you selected.

    For more information on selecting the type of installation needed, see Section 4.2, Understanding Which Installation Process to Use.

4.3.6 Modifying the Update Agent Configuration File

  1. Locate the cuagent.ini file in the admin directory.

  2. Modify the cuagent.ini file settings, then save the file.

    The cuagent.ini file enables you to configure the following settings:

    Option

    Description

    Settings

    [AgentStatus]

    Specifies whether the Update Agent is configured. If configured, the rest of the .ini file is read. If disabled, the Agent does not look for an update to the Client

    Disabled=Yes | No (Default: No)

    [LaunchUpdate]

    Specifies whether the Client Install is launched. When this option is set to Yes, the Update Agent determines if an update is needed and then launches the necessary update. When it is set to No, the Update agent determines if an update is needed but does not launch the necessary update.

    Launch=Yes | No (Default: Yes)

    [Redirection]

    Specifies a path to redirect the Update Agent to a different location for Novell Client files. This is useful if you need to locate the files on a different server.

    The path can be a mapped drive, UNC path, or URL.

    You can redirect the Update Agent five times (once in each of five different cuagent.ini files located in different locations).

    Location=path_to_update

    [UpdatePrompt]

    Specifies whether users are prompted to begin the update and are notified about the location the update will run from.

    Display specifies whether users are prompted to update Novell Client.

    Display Location specifies whether users are notified about the location that the update is to run from.

    Administrator Message specifies additional text that appears when the user is prompted to start an update.

    Display=Yes | No

    DisplayLocation=Yes | No (Default: No)

    AdministratorMessage= message_from_administrator

    [AgentFiles]

    Specifies whether the Update Agent software should be updated before the Novell Client update occurs.

    This option lets you update the Update Agent if newer software is available with features that you want to use or if the Update Agent has a defect. Then, the newer Update Agent completes the Client software update.

    Update=Yes | No (Default: No)

    [AgentSettings]

    Specifies settings located on the Novell Client Update Agent property page. If you change settings in the cuagent.ini file, these changes are made in the Registry and appear in the Novell Client Update Agent property page. These changes go into effect the next time the Update Agent is run.

    Update specifies whether the settings are transferred from the .ini file to the workstation’s registry.

    Enable Automatic Update Agent specifies whether the Update Agent is launched automatically. The Update Agent checks for a new version of the Novell Client at the designated interval and from the designated locations. The Update Agent is launched as a part of the login process.

    Update Agent Launch Interval sets the interval (in days) that the Novell Client Update Agent checks for a new version of the Novell Client.

    Enable Update Location specifies whether the Novell Client Update Agent looks for a new version of the Novell Client in the designated update location.

    The Update Agent checks for updates in the following order of configured locations: 1) Update Location, 2) Previous Install Location.

    The Update Agent looks in each configured location for valid file types and stops when it locates any. Ensure that you have the latest files in the first location that the Update Agent searches.

    Update Location specifies the update location (mapped drive, UNC, or URL).

    Enable Previous Install Location specifies whether the Novell Client Update Agent looks for a new version of the Novell Client in the previous install location.

    Administrator Rights specifies whether the Novell Client Update Agent has administrative rights on the workstation. The Update Agent must have these rights to update the Novell Client. This is useful when the user who logs in to the workstation is not the workstation Administrator user. If this setting is set to No, the Update Agent is launched with the rights of the currently logged-in user.

    Update=Yes | No (Default: No)

    EnableAutomaticUpdateAgent= Yes | No

    UpdateAgentLaunchInterval= interval_in_days

    EnableUpdateLocation=Yes | No

    UpdateLocation=update_location_path

    EnablePreviousInstallLocation= Yes | No

    AdministratorRights=Yes | No

    [ClientSettings]

    Update specifies whether the Novell Client Update Agent looks for Novell Client property page updates.

    Unattend File specifies the name of the configuration (unattend) file that contains property page settings. This file should be in the same location as the Update Agent.

    Display Prompt specifies whether users are prompted to update client settings.

    Display Location specifies whether users are notified about the location from which the update will run.

    Administrator Message specifies additional text that appears when users are prompted to update.

    Update=Yes | No (Default:No)

    UnattendFile=lfile_name

    DisplayPrompt=Yes | No (Default: No)

    DisplayLocation=Yes | No (Default: No)

    AdministratorMessage= message_from_administrator

    [StatusLogging]

    Specifies whether a status log is created and where it is located.

    Use=Yes | No (Default: Yes)

    File=log_file_path

  3. Copy this file to the directory where you unzipped the download file.

  4. Complete any additional procedures outlined in the installation type you selected.

    For more information on selecting the type of installation needed, see Section 4.2, Understanding Which Installation Process to Use.

4.3.7 Enabling the Novell Client Update Agent

Enabling the Novell Client Update Agent During a Client Install or Upgrade

  1. Select your type of the Novell Client installation.

    You must select an install process that allows you to modify the client properties (meaning it cannot be a default install type, because the default installs do not modify any configuration files or settings).

    For more information on selecting an installation type, see Section 4.2, Understanding Which Installation Process to Use.

  2. During the installation process, create a custom configuration (unattend) file to modify the properties.

    For more information, see Creating the Configuration File (Unattend File).

  3. In the Novell Client Install Manager (nciman.exe), double-click Client, click the Update Agent tab, then make the following changes:

    1. Select Enable Automatic Update Agent.

    2. (Optional) To launch the Update Agent automatically at a set interval, select Enable Automatic Update Agent and then set the launch interval (in days).

      If the Update Agent is not set to launch automatically, users can still launch it from the Red N menu whenever an update needs to be run.

    3. Specify an update source location.

      You can select either a specific location on the network or the previous install location (if you intend to place updates in the same location as the last install). The Update Agent always looks in the specified location for new files.

  4. Continue changing additional configuration settings to create your custom configuration (unattend) file, then click OK.

  5. Complete any additional procedures outlined in the installation type you selected.

    For more information on selecting the type of installation needed, see Section 4.2, Understanding Which Installation Process to Use.

Enabling the Novell Client Update Agent by Using ACU Without Installing Novell Client Software

  1. Modify the acu.ini file so that the [UpdateAgentSettings] section of the .ini file is set to UPDATE=YES.

    See Modifying the ACU Configuration File for more information.

  2. Change the desired Update Agent settings in the [UpdateAgentSettings] section of the acu.ini file.

  3. Run ACU through the login scripts.

    See Distributing the Novell Client by Using Login Scripts.

The next time users log in, ACU runs and changes to the Update Agent settings are made. The Update Agent is configured and checks for updates as specified in the settings.

Enabling the Novell Client Update Agent on a Local Workstation

  1. At the user's workstation, right-click the Red N icon in the notification area.

  2. Click Novell Client Properties.

  3. Click the Update Agent tab.

  4. Set the properties that you want to change.

    HINT:Help for all the Property pages is available directly on the property pages by clicking the Question Mark (?) or right-clicking and then selecting What's This? Also, this information and additional information on other settings is available in the August 2004 AppNotes® article Novell Client 4.9 SP2: initialization, Login and Settings.

  5. Click OK to make the changes and close the property pages.

4.3.8 Installing Support Packs

The Support Pack installs only a subset of client files and does not require a version change for the Client. Support Packs can also be added to the Client (in an overlay manner) to allow the installation of both the Client and the Support Pack in one step. Depending on the installation option you use to deploy Support Packs, the process differs slightly.

For example, if you choose one of the Web Server installation options, the IP address specified in the WriteIP utility must be a location on a Web server that contains the Support Pack files. If the IP address specified in the WriteIP utility is a location on a Web server that contains both the Client and the Support Pack files (in an overlay), both the client and Support Pack files are downloaded; however, only the Support Pack install launches. Creating a directory called sp in the directory where you unzipped the download file and placing the Support Pack files in that sp directory avoids unnecessary download of client files. The Web download utility downloads only the files in the sp directory and launches the Support Pack install.

In addition, Novell Client property page settings cannot be changed through the default Support Pack installation because only a subset of the Novell Client files are changed. If you need to install a Support Pack and update properties, you must either complete a full client installation that has the Support Pack files in an overlay or use the Update Agent to run both the Support Pack installation and update the Novell Client properties.

For more information on selecting an installation option, see Section 4.2, Understanding Which Installation Process to Use.

4.3.9 Modifying the ACU Configuration File

IMPORTANT:This procedure is just one of the tasks required to complete installation of the Novell Client on multiple workstations. For more information on how this procedure combines with other procedures to create an install method, see Section 4.2, Understanding Which Installation Process to Use.

The Automatic Client Upgrade utility (acu.exe) determines whether the client needs to be updated and lets you specify several installation options.

  1. Open the acu.ini file located in the folder that you created on the server.

  2. Modify the configuration options.

    IMPORTANT:If you use a configuration (unattend) file to configure the Novell Client and you are using acu.exe, you must change the [UNATTENDFILE] option to Yes in the acu.ini file.

    Option

    Description

    Settings

    [LaunchInstall]

    Specifies whether Setup is launched after acu.exe determines that the installation is necessary.

    Launch=Yes | No (Default: Yes)

    [DisplayDialog]

    Specifies whether users are prompted to begin the upgrade.

    Display=Yes | No (Default: Yes)

    [UnattendFile]

    Specifies whether a configuration (unattend) file is used and where it is located.

    Use=Yes | No (Default: No)

    File=configuration_file_path

    [StatusLogging]

    Specifies whether a status log is created and where it is located.

    If you did not create a status log file prior to installation, it is now 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 appears when the user is prompted to start an ACU.

    Message=the_message_ you want_to_appear

    [ClientLocalInstall]

    Specifies whether the installation is 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 DeleteLocalInstall=Yes.

    [UpdateAgentSettings]

    Specifies the Novell Client Update Agent property page settings.

    IMPORTANT:Use this section to set the Update Agent settings if you do not already have the Update Agent installed and configured. If it is installed and configured, make changes in the cuagent.ini file.

    If you change settings, these changes are made in the Registry and appear in the Novell Client Update Agent property page. These changes go into effect the next time the Update Agent is run.

    Update specifies whether the settings are transferred from the .ini file to the workstation’s registry.

    Enable Update Agent specifies whether the Update Agent is configured. This setting specifically applies to workstations running Novell Client version 4.90 SP2 that are upgrading Novell Client software. Selecting this option enables the Update Agent to perform the software update.

    Enable Automatic Update Agent specifies whether the Update Agent is launched automatically. The Update Agent checks for a new version of the Novell Client at the designated interval and from the designated locations. The Update Agent is launched as a part of the login process.

    Update Agent Launch Interval sets the interval (in days) that the Novell Client Update Agent checks for a new version of the Novell Client.

    Enable Update Location specifies whether the Novell Client Update Agent looks for a new version of the Novell Client in the designated update location.

    The Update Agent checks for updates in the following order of configured locations: 1) Update Location, 2) Previous Install Location.

    Update=Yes | No (Default: No)

    EnableUpdateAgent= Yes | No

    EnableAutomaticUpdateAgent=Yes | No

    UpdateAgentLaunchInterval= interval_in_days

    EnableUpdateLocation= Yes | No

    UpdateLocation= update_location_path

    EnablePreviousInstallLocation=Yes | No

    AdministratorRights=Yes | No

    [UpdateAgentSettings] continued...

    The Update Agent looks in each configured location for valid file types and stops when it locates them. Ensure that you have the latest files in the first location that the Update Agent searches.

    Update Location specifies the update location (mapped drive, UNC, or URL).

    Enable Previous Install Location specifies whether the Novell Client Update Agent looks for a new version of the Novell Client in the previous install location.

    Administrator Rights specifies whether the Novell Client Update Agent has administrative rights on the workstation. The Update Agent must have these rights to update the Novell Client. This is useful when the user who logs in to the workstation is not the workstation Administrator user. If this setting is set to No, the Update Agent is launched with the rights of the currently logged-in user.

     

    [Uninstall]

    Specifies which network components are uninstalled. Users are prompted to reboot after the uninstall is complete.

    IPX specifies whether IPX™ is uninstalled.

    CMD specifies whether Compatibility Mode is uninstalled.

    Client specifies whether the Novell Client is uninstalled.

    NDPS specifies whether Novell Distributed Print Services™ is uninstalled.

    Workstation Manager specifies whether Workstation Manager, a component of ZENworks®, is uninstalled.

    NAL specifies whether Novell Application Launcher™, a component of ZENworks, is uninstalled.

    Imaging Service specifies whether Imaging Service, a component of ZENworks, is uninstalled.

    Remote Management specifies whether Remote Management, a component of ZENworks, is uninstalled.

    NICI specifies whether Novell International Cryptographic Infrastructure (NICI) is uninstalled.

    NMAS specifies whether Novell Modular Authentication Services (NMAS™) is uninstalled.

    NetIdentity specifies whether NetIdentity is uninstalled.

    Administrator Message specifies additional text that appears when the uninstall begins.

    IPX=Yes | No (Default: No)

    CMD=Yes | No (Default: No)

    Client=Yes | No (Default: No)

    NDPS=Yes | No (Default: No)

    WorkstationManager=Yes | No (Default: No)

    NAL=Yes | No (Default: No)

    ImagingService=Yes | No (Default: No)

    RemoteManagement=Yes | No (Default: No)

    NICI=Yes | No (Default: No)

    NMAS=Yes | No (Default: No)

    NetIdentity=Yes | No (Default: No)

    AdministratorMessage= message_from_administrator

  3. Complete any additional procedures outlined in the installation type you selected.

    For more information on selecting the type of installation needed, see Section 4.2, Understanding Which Installation Process to Use.

4.3.10 Creating the Configuration File (Unattend File)

IMPORTANT:This procedure is just one of the tasks required to complete installation of the Novell Client on multiple workstations. For more information on how this procedure combines with other procedures to create an install method, see Section 4.2, Understanding Which Installation Process to Use.

The Novell Client installation reads a configuration (unattend) file generated by the Novell Client Install Manager in order to customize the installation process and to configure the Novell Client settings.

Figure 4-9 Novell Client Install Manager

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

The configuration (unattend) file created by the Novell Client Install Manager provides information such as property page settings and installation settings. This file should be placed in the same folder as the installation utility.

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 Section 5.0, Setting Client Properties.

  1. Start Novell Client Install Manager (nciman.exe).

    Novell Client Install Manager is located in the \admin folder in the directory that you copied to the server.

  2. Modify the installation options as needed:

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

    2. On the selected property page, set the parameters and then click OK.

      Novell Client Install Manager Installation Configuration Property Page

      The values that you set appear in the Novell Client Install Manager's right list box after you close the property page so that you can see a list of all parameters that have been modified.

  3. Modify the Client Properties as needed.

    For example, if your network uses LDAP, you can enable contextless login. Or, you might want to change the welcome screen bitmap.

    For more information on the Client Properties, see Section 5.0, Setting Client Properties and Section 7.0, Managing Login. Or, right-click any property to view its help information.

  4. Click File > Save.

    You can use any filename (for example, unatt_xp.txt).

  5. Copy this file to the directory where you unzipped the download file.

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

  6. Complete any additional procedures outlined in the installation type you selected.

    For more information on selecting the type of installation needed, see Section 4.2, Understanding Which Installation Process to Use.

4.3.11 Modifying the Support Pack Configuration File

IMPORTANT:This procedure is just one of the tasks required to complete installation of the Novell Client on multiple workstations. For more information on how this procedure combines with other procedures to create an install method, see Section 4.2, Understanding Which Installation Process to Use.

The Novell Client Support Pack utility lets you control how Support Packs are pushed out to workstations by modifying the setupsp.inf file to define install custom settings.

  1. Open the setupsp.ini file located in the folder that you created on the server.

  2. Modify the Support Pack options section only.

    IMPORTANT:Do not change the Client Version and Support Pack Version settings.

    Option

    Description

    Settings

    Reinstall

    Specifies whether setupsp.exe reinstalls the already installed Support Pack on the workstation.

    Yes: Setupsp.exe runs and reapplies updates even when the workstation already has the current Support Pack applied.

    No: Setupsp.exe checks to ensure that the Support Pack on the workstation is the most current one and does not reinstall if it is current.

    Reinstall=Yes | No (Default: No)

    DisplayInstallPrompts

    Specifies whether users are prompted during the Support Pack installation.

    This setting does not affect RebootOnCompletion or PromptOnCompletion.

    DisplayInstallPrompts= Yes | No (Default: Yes)

    UpdateNICI

    Specifies whether Novell International Cryptographic Infrastructure (NICI) is updated.

    UpdateNICI=Yes | No (Default: YES)

    UpdateNMAS

    Specifies whether Novell Modular Authentication Services (NMAS) is updated.

    UpdateNMAS=Yes | No (Default: Yes)

    UpdateNetIdentity

    Specifies whether NetIdentity is updated even if an older version is detected.

    UpdateNetIdentity=Yes | No (Default: Yes)

    RebootOnCompletion

    Specifies whether the workstation is rebooted after the Support Pack install is completed.

    Prompt: Users are prompted to decide whether or not to reboot the workstation.

    NOTE:The PromptUserOnCompletion setting has no affect if RebootOnCompletion is set to Prompt.

    Yes: The workstation is rebooted upon completion. This setting can be used in conjunction with the PromptUserOnCompletion setting to force the reboot and alert users that the reboot must occur.

    No: The workstation is not rebooted upon completion. This setting can be used in conjunction with the PromptUserOnCompletion setting to advise the user that the update is complete. However, there is no forced or prompted reboot of the workstation.

    RebootOnCompletion= Prompt | Yes | No (Default: Prompt)

    PromptUserOnCompletion

    Specifies whether users are prompted that a update has occurred and (optional) that the workstation needs to be rebooted.

    Yes: Displays a prompt explaining that the update is completed. If this setting has been used in conjunction with RebootOnCompletion=Yes, the workstation is rebooted when the user clicks OK.

    No: Does not display a prompt for users. If this setting has been used in conjunction with RebootOnCompletion=Yes, the workstation is rebooted without warning.

    PromptUserOnCompletion= Yes | No (Default: Yes)

  3. Complete any additional procedures outlined in the installation type you selected.

    For more information on selecting the type of installation needed, see Section 4.2, Understanding Which Installation Process to Use.

4.3.12 Selecting a Network Server Distribution Option

After you have set up your network installation of the Novell Client, you must decide how to distribute the install files. You can modify the login script to launch installation files, distribute the files through ZENworks, or use another method you have available on your network.

For more information on using login scripts, see Distributing the Novell Client by Using Login Scripts. For more information on using ZENworks, see the documentation associated with the installed version of ZENworks.

Distributing the Novell Client by Using Login Scripts

IMPORTANT:This procedure is just one of the tasks required to complete installation of the Novell Client on multiple workstations. For more information on how this procedure combines with other procedures to create an install method, see Section 4.2, Understanding Which Installation Process to Use.

Keep in mind the following considerations as you work with login scripts:

  • You need to modify login scripts for users whose workstations are 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).

You can create or modify a user login script using either ConsoleOne® or iManager.

Using iManager
  1. Click Roles and Tasks > User Management > Modify User.

  2. Specify a username and context, then click OK.

  3. Click General > Login Script.

  4. Type the login script commands and information in 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 the Novell Login Scripts Guide.

  5. To save the login script, click OK.

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

  2. Click Login Script.

  3. Type 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 the Novell Login Scripts Guide.

  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 installs or updates 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. See Getting Around the One User and One Profile Login Script Restriction in the Novell Login Scripts Guide.

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.

NOTE: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 2000/XP *****
IF OS = “winnt”
   WRITE “Updating Novell Client for Windows 2000/XP.”
   #\\server1\sys\public\client\acu.exe
   IF “%ERROR_LEVEL” = “1” THEN
        EXIT
   END
END