![[Intel Navigation Header]](/CONTENT/PIX/HEADER.GIF)
LANDesk(R) Management Suite v2.01 Installation Recommendations
LANDESK(R) MANAGEMENT SUITE V2.01 INSTALLATION RECOMMENDATIONS
LANDesk(R) Management Suite v2.01 Installation Recommendations for a
Successful Procedure.....
1. The File Server should be Novell Netware* v3.11,v3.12, v4.02 or
v4.10. It should have a minimum of 16 MB of RAM (24 MB would be
better if the file server is also being used for other products).
Use 6.10c BTRIEVE.NLM, BSPXCOM.NLM, AFTER311.NLM (in F:\SYSTEM
directory) This is the version that ships with Novell Netware
v3.12. Do not install LANDesk Management Suite software if you are
using any other version of BTRIEVE*.
Note: LANDesk Management Suite ships the latest Btrieve 6.10 files
in a compressed file named BTR61.EXE.
Supervisor Workstation Requirements:
2. The workstation that you will be installing on must have at least 8
MB of RAM, 10 MB of free disk space, a VLM and IPXODI compatible
driver/NIC and Microsoft Windows* v3.1 orv 3.11.
Note: LANDesk Management Suite ships a recent Novell client driver
kit on the CD-ROM for LANDesk Management Suite v2.01 in the
directory NWCLIENT\DOSWIN. See Step 11 for more information.
3. The "installing" workstation should be logged into the primary File
Server that LANDesk Manager will be installed to. Your login should
be either Supervisor or a login name that has Supervisor Equivalent
rights.
4. Once you're logged in with Supervisory rights, start Windows from
the local C:\ drive. When Windows has started, shut down all
"other" applications that may be running ( like E-Mail etc... ) to
maximize system resources available.
Starting the Installation Process:
5. From the Program Manager in Windows, select File and then Run.
Type D:\DISK1\SETUP.EXE on the File/Run command line, then click
the OK button. (where D: is the drive for your CD-ROM)
6. As the install process takes place, you will be prompted to choose
certain items or directories. At each step, confer with your
network adminstrator/customer as to what choices they want to make.
7. Selecting directories: As part of the install process, you will be
asked to put the LANDesk Management files in certain areas on the
File Server. It is important that these files go in certain
places:
F:\LANDESK....
This is where the bulk of the LANDesk Manager files go. It is
preferred to have them in the F:\ or Root directory, but you can
place them on another drive letter or volume if the network
administrator does not have space on F:\ or wants to put it in an
\APPS area.
F:\LOGIN\LANDESK...
These files must go here! They are the files that are used at
Login and therefore must reside in a new directory created under
the LOGIN directory.
C:\LANDESK....
This directory is created on the local Supervisor's workstation
ONLY. It is where certain EXEs and RPTs will be kept. This must
be a local drive and not out on the network.
Note: A supervisor's shared area out on the network as local
disk will not be recognized.
Continue from here through the file server acceptance screen.
Select the applications you want to load from the selection screen
and then go through the serialization process (automatic).
Changes to Script, .INI, .NCF files...
8. Accept the changes to the SYSTEM.INI, AUTOEXEC.BAT, Login script,
and other files as is. These changes will allow:
a. the Traffic and Application Monitors to view up to 5000 packets
per second while in Windows (SYSTEM.INI changes )
b. an automatic load of BREQUEST.EXE at Login, to run the Inventory
Manager ( AUTOEXEC.BAT changes).
c. workstations that log in and are members of the LANDESKGROUP
created by LANDesk Management Suite to be inventory scanned and
enabled for management. The changes are encapsulated within a
separate NCF file that is executed during login time if people
belong to the LANDESKGROUP. With respect to the Login Script,
our program is intelligent enough to place itself in the script
before the last Exit statement, so usually no editing within the
script is required.
9. The program will continue through the install process, setting
up the icons. You will then be prompted to select either a view
TODO list or EXIT. Select the TODO list and print it out for
reference later on to install the NLMs from RCONSOLE.
This is useful reference printout because it keeps track of
everything it did. Now exit the install and go back to Windows.
Shutdown Windows entirely and go back to the DOS prompt ( C:\> or
F:\>).
10. It might be desirable to go to the PUBLIC directory of the
server you installed LANDesk Management Suite to and edit the
LD_LOGIN.DAT file.
You can edit certain line item statements to optimize the system
if desired. They are as follows:
#L:LOADTSR /SMARTTSR L:USERTSR /LOADHIGH /STEALTH
/LOADHIGH will try to load the 6.5K TSR high if available
/STEALTH hides the blue USER Utility box and control information
from the user.
#L:LOADTSR L:POPUPTSR . . .
This TSR can be remarked out if you don't want to load the file
transfer and chat portion of LANDesk Management Suite under DOS.
To remark out the command, add REM in from of the LOADTSR
command, for example:
REM #LOADTSR /LANSEL
11. Since Intel ships the Novell client drivers with LANDesk Management
Suite, it is recommended that these files be used to update DOS and
Windows workstations.
These files can be found on the CD-ROM in the directory NWCLIENT\DOSWIN.
The installation can be run from DOS by typing INSTALL. The
configuration program will automatically sense many popular network
interface cards and will automatically prepare the workstations to load
the VLM drivers and configure Windows properly for use with NetWare.
In the majority of cases, the reason a workstation might be having
trouble being managed by LANDesk Management Suite is that the network
client drivers are old, out of date, or improperly installed. The
NetWare client kit will resolve these issues.
Trademark information