*****************************************************************************

                         INTEL LANDESK MANAGER

                         INSTALLATION CHECKLIST

*****************************************************************************


IMPORTANT: Before installing LANDesk Manager, please read the following
           information.

LANDesk Manager is a comprehensive suite of network management tools. To
enable LANDesk Manager's powerful functionality, the Setup program asks you
to confirm modifications to your workstation's SYSTEM.INI and AUTOEXEC.BAT
files, to the file server's AUTOEXEC.NCF file, to the system login script,
and to your clients' workstation configurations.

Installing LANDesk Manager is easiest if you complete the following checklist.
Many of these items are not strictly necessary, but all of them are highly
recommended. Information on how these items support your installation can be
found in the LANDesk Manager User's Guide and the LANDesk Manager Setup Guide.

Check each of the following. Then, refer to your LANDesk Manager Setup Notes,
and begin to install LANDesk Manager from Disk 1.

    Before running the LANDesk Manager Setup program, determine where you
     want to place LANDesk Manager files. Map network drives to these volumes.
     For information about the amount of disk space required and what files
     are placed where, see your LANDesk Manager Setup Guide. Do not try to map
     logical drives from a Windows DOS box. Also, do not use map-rooted drives
     (example: DRIVE H: = SERVERNAME\SYS:  \APPS\CCMAIL).

    If you are using Compaq's 32-bit NetFlex card with any of the following
     drivers do not try to load Server Monitor's MONIT386.NLM until you
     upgrade your driver to CPQETHER.LAN version 2.1 or CPQTOKEN.LAN version
     2.1 (available on CompuServe or from your local vendor): CPQETHNW.LAN 1.0
     or 1.1, CPQTOKNW.LAN 1.2 or 1.3, CPQTOKEN.LAN 2.0, or CPQETHER.LAN 2.0.

    LANDesk Manager was developed for NetWare 3.11, 3.12, and 4.01 in bindery
     emulation mode. Make sure you do not have files in your SYSTEM or LOGIN
     directories that came from earlier versions of NetWare.

    Inventory Manager requires Btrieve version 5.15 or 6.10. Check the
     following files and dates to determine if you are currently loading a
     compatible version of Btrieve.

     Btrieve 5.15                         Btrieve 6.10
     ------------                         ------------
     BTRIEVE.NLM	  02-19-91	(v5.15)	   BTRIEVE.NLM	   05-24-93	(v6.10a)
     CLIB.NLM  	  02-14-91	(or later)	CLIB.NLM		   12-16-92	(or later)
     BSPXCOM.NLM    01-24-91	      		BSPXCOM.NLM	   05-05-93
     BREQUEST.EXE   02-12-91	(v5.16)		BREQUEST.EXE	05-13-93	(or later)
     WBTRCALL.DLL   06-28-91	(v5.17)		WBTRCALL.DLL	05-13-93
                                          WBTRVRES.DLL	01-30-93

     Do not use BSTART.NCF to load the Btrieve NLMs or manually load the NLMs.
     LDINV.NLM will automatically load BTRIEVE.NLM and BSPXCOM.NLM with the
     necessary parameters. The DLLs need to be in the administrator's
     directory (usually SYS:LANDESK). For more information, download FaxBACK
     document #5566 from (800) 525-3019.

    Use a version of LOGIN.EXE that shipped with NetWare 3.11, 3.12, 4.0, or
     4.01. LANDesk Manager was not tested with locally developed login
     programs.

    Use NETX version 3.26 or later, and make sure your Windows installation
     is configured to use NetWare shells version 3.26 or later.

    Before installation, close ALL applications except Windows Program
     Manager.

    Use the latest drivers for your network interface cards (NIC). ODI
     drivers version 2.0 (or later) are best.

     LANDesk Manager Setup and WKSTACFG.EXE update Novell's VIPX.386 driver.
     Current versions of this driver may be incompatible with IPX.COM. You may
     need to switch IPX network device drivers to IPXODI drivers.

     Software Probe requires an ODI driver that supports promiscuous mode. If
     you want to gather data for Traffic Monitor or Application Monitor from
     the administrator's NIC, it also requires an ODI driver that supports
     promiscuous mode. For more information about promiscuous mode ODI
     drivers, see "Loading a promiscuous mode ODI driver."

    We recommend that the LANDesk Manager administrator's workstation is at
     least a 486/33 CPU based PC.

    We recommend that the LANDesk Manager administrator's workstation have
     at least 8 megabytes of system memory.

    Before loading USER.COM or running Windows, load a DOS mouse driver on
     the LANDesk Manager administrator's workstation and on all workstations
     that may be remotely controlled with Desktop Access.

    Make sure you load network drivers before you load any LANDesk Manager
     TSRs.

    Token Ring cards based on the Tropic Chip Set do not support promiscuous
     mode. You cannot use a Token Ring card based on the Tropic Chip Set to
     gather data for Traffic Monitor and Application Monitor.

Post-installation checklist

    Inventory Manager may conflict with other programs based on the Btrieve
     database. If you experience problems, see your Novell Btrieve
     Installation and Operation manual. Check to see that Btrieve is operating
     with at least the default values for the Btrieve parameters.

    If you cannot control the keyboard on a file server with Desktop Access,
     load USER.NLM with an /OLDKB switch.

    TSRs, configuration utilities, or other agents designed to directly
     access network functions may be incompatible with LANDesk Manager. If you
     encounter any problems, first try to isolate programs that involve TSRs,
     configuration utilities, or other agents that directly access network
     functions.

    Check the placement of the LANDesk Manager section in the system login
     script. This section should appear after the commands to map a search
     drive to the PUBLIC directory and any network Windows installations but
     before the first EXIT statement. For more information, see "Confirming
     changes to the file server" in the LANDesk Manager Setup Guide.

    If you use the NIC in your LANDesk Manager administrator's workstation
     (instead of Software Probe) to gather data for Traffic Monitor or
     Application Monitor, your CPU may not be able to process the data and
     keep up with the Windows screen refresh demands. If you have trouble
     using your administrator's workstation to gather data, consider using
     Software Probe.

     The following table indicates the peak levels at which various CPUs seem
     to have problems.

     CPUs	   Packets per second
     ----      ------------------
     386/33    2000
     486/25SX  2000
     486/33    2500
     486/66    3000

     The peaks listed above are estimates. If your network traffic becomes
     more than your CPU can handle, Ctrl+Alt+P toggles your network interface
     card out of (and into) promiscuous mode.
