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

                         INTEL LANDESK MANAGER

                              SETUP NOTES

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


Getting started
---------------
NOTE:  LANDesk Manager Setup asks you to confirm changes to system files
before making them. Changes made by LANDesk Manager Setup to the AUTOEXEC.BAT,
AUTOEXEC.NCF, and system login script (NET$LOG.DAT) files have the following
header and footer (which you should not remove):

REM *** BEGIN Intel LANDesk Manager Section ***
...Commands...
REM ***  END Intel LANDesk Manager Section ***

1.	Before proceeding, read the Installation Checklist.

2.	Log in as supervisor or equivalent to the server on which you want to
   install LANDesk Manager.

3.	From Microsoft Windows, run SETUP.EXE from Intel LANDesk Manager Disk 1 of
   5.

4.	Complete the installation as prompted by the Setup program. For more
   information on the changes you are asked to make, check the online help,
   this card, or the LANDesk Manager Setup Guide.


Administrator workstation changes
---------------------------------
Setup copies the following Windows drivers and modifies the [386Enh] section
of the SYSTEM.INI file to load them:
   VUSER.386
   VMON.386

Setup also adds parameter lines to the [386Enh] section of the SYSTEM.INI file
for the VMON.386 driver: 
   VmonVirtualizeIRQs=no
   VmonPacketHeap=5000
   VmonFilterHeap=4096
   TimerCriticalSection=10000

Setup modifies the administrator's AUTOEXEC.BAT file to load one
terminate-and-stay-resident program (TSR). BREQUEST /r:26 loads a 29K TSR that
is necessary to run Inventory Manager. BREQUEST must be loaded after you have
logged in to the network. Previous versions of LANDesk Manager also required
another TSR, APV.EXE. This TSR is no longer necessary. If you are upgrading,
you can remove the lines that load APV from your AUTOEXEC.BAT and you can
delete the APV.EXE file.


Client workstation changes
--------------------------
For Desktop Access, File Transfer, or Chat to access other workstations, each
workstation must be configured by WKSTACFG.EXE. This program replaces outdated
versions of USER.COM on local drives, copies necessary files to the Windows
directories, and modifies the SYSTEM.INI and WIN.INI files. For more
information about WKSTACFG.EXE, see the LANDesk Manager Setup Guide.

To enable the client elements of Chat, File Transfer, Virus Scan, and Network
Printer Manager, each workstation must run WSSETUP.EXE from Windows. For more
information about WSSETUP.EXE, see the LANDesk Manager Setup Guide.


File server changes
-------------------
Setup modifies the AUTOEXEC.NCF file to load NLMs required by LANDesk Manager
tools. The Server Monitor NLMs do not function on a NetWare 4.x server. Setup
does not modify the AUTOEXEC.NCF file of a NetWare 4.x server with command
lines to load the Server Monitor NLMs, and you should not try to manually load
the Server Monitor NLMs on a NetWare 4.x server.

    LOAD LDINV FILE=<SYS:LANDESK> loads the Inventory Manager NLM with its
     data file.

    LOAD LDISCAN INV_SERV=<SERVERNAME> FILE=<SYS:LANDESK> loads the Inventory
     Scan NLM.

    LOAD USER loads the NLM required by Desktop Access.

    LOAD CONTROL loads an NLM required by Server Monitor.

    LOAD MONIT386 loads an NLM required by Server Monitor.

Setup modifies the system login script (NET$LOG.DAT) to include commands for
the following:

    LDISCAN initiates a hardware/software inventory scan of each station at
     login.

    WKSTACFG executes a one-time setup that configures each station for
     access by LANDesk Manager.

    USER loads the Intel User Agent, a 6.5K TSR, on each workstation at
     login.

    LANSEL loads a 5.5K TSR that enables popup windows on DOS-only
     workstations.

Users must log in to a NetWare 4.x server as a bindery object
(login <username> /b) to execute the above system login script modifications.
Or, you can add these commands to an NDS login script.


Using NetWare's SYSCON to control your installation
---------------------------------------------------
Most of the changes LANDesk Manager requires are local. However, if you choose
to install Chat, File Transfer, Desktop Access, or Inventory Manager, LANDesk
Manager Setup asks to modify the system login script (NET$LOG.DAT). Because
modifications to the system login script can affect anyone who logs in to the
server, the added lines are controlled by a conditional statement
(If <condition> then <action>...).

Before you confirm the modifications to your system login script, you are
asked to indicate which user group you would like the changes to affect:
LANDESK or EVERYONE. If you select the LANDESK group, the Setup program
creates a LANDESK group and adds your login name to this group. If you select
this group, the only workstations that will be configured are those you log in
on. 

After Setup is finished, you can run SYSCON and add other users to the LANDESK
group. As you do so, they will also be affected by the modifications to the
system login script as they log in. This ensures that you control which
workstations are affected by the changes to your system login script.


Software Probe
--------------
Traffic Monitor and Application Monitor require large amounts of data. To
gather this data remotely without impacting the performance of your
workstation, use Software Probe. You can install Software Probe on
workstations as needed to obtain network traffic statistics for all segments
of your LAN. See the LANDesk Manager Setup Guide for more information about
installing and configuring Software Probe.
