[Intel Navigation Header]

    LANDesk(R) Manager 1.51: Installation Usage Tips

    Contents:

    • GENERAL NETWARE* ENVIRONMENT
    • WORKSTATION CONFIGURATION
    • DOS ENVIRONMENT
    • WINDOWS* ENVIRONMENT
    • CALL TO UNDEFINED DYNALINK (NO ICONS IN CONTROL PANEL)
    • THE LOGIN PROCESS
    • UPGRADING FROM UNINSTALLED V1.X
    • INSTALLING LANDESK(R) MANAGER TO MULTIPLE FILE SERVERS
    • INSTALLING LANDESK(R) MANAGER WITH NETWARE* V4.X
    
    

    GENERAL NETWARE* ENVIRONMENT

    
       LANDesk(R) Manager is Novell-certified for NetWare* v3.11 and NetWare
    
       v3.12. LANDesk  Manager v1.51 officially supports NetWare v4.01 (bindery
    
       emulation) with the  exception of Server Monitor--its 2 NLMs only
    
       function with NetWare v3.11 and  NetWare v3.12 file servers. All 5 NLMs
    
       take less than 200 KB file server memory.  See  documents 5540 and 5536
    
       for more information Desktop Access and Server Monitor, respectively.
    
    
    
       We will officially support NetWare v4.1 as soon as possible. Do not load
    
       Inventory Manager NLMs (LDINV.NLM or LDISCAN.NLM) on a NetWare v4.1 file
    
       server.
    
    
    
    

    WORKSTATION CONFIGURATION

    
       Use LSL and IPXODI v2.0 or higher and NETX v3.22 or higher. LANDesk(R)
    
       Manager  v1.5 was successfully tested with v1.0x VLMs (May or September
    
       1993), and  LANDesk Manager v1.51 was successfully tested with v1.1
    
       VLMs.
    
    
    
    

    DOS ENVIRONMENT

    
       Using MS-DOS v5.0 or v6.x, the following environment leaves about 600KB
    
       of  conventional memory for the largest executable program size. If you
    
       can,  temporarily have a largest executable program size of at least 580
    
       KB to  give the generic Microsoft install routine enough memory to run
    
       completely.
    
    
    
       Note:     Ifyou are having problems with a memory manager besides EMM386
    
       (for  example, QEMM or 386MAX), use EMM386 instead.
    
    
    
       CONFIG.SYS:
    
    
    
       device=c:\windows\himem.sys
    
       device=c:\windows\emm386.exe noems
    
       dos=high, umb
    
       devicehigh=c:\dos\ansi.sys
    
       buffers=20
    
       files=40
    
       shell=c:\command.com c:\ /p /e:1024
    
       stacks=9,256
    
    
    
       AUTOEXEC.BAT
    
    
    
       @echo off
    
       prompt $p$g
    
       path c:\windows;c:\dos
    
       lh c:\mouse\mouse
    
       set temp=c:\temp
    
       lh lsl    lh exp16odi
    
       lh ipxodi
    
       lh netx
    
       f:
    
       login servername/username
    
       REM *** BEGIN Intel LANDesk Manager Section ***
    
    
    
       REM The following line loads the Btrieve* TSR (29kbytes)
    
       REM required by Inventory Manager.
    
       brequest /r:26
    
       REM ***   END Intel LANDesk Manager Section ***
    
    
    
    

    WINDOWS* ENVIRONMENT

    
       LANDesk(R) Manager requires the administrator's workstation to be
    
       configured  for NetWare*. Use Windows'* SETUP.EXE and install the
    
       network option (i.e.,  NETX v3.26 and above), which requires Windows'
    
       diskette #2 and supplies the  necessary NETWARE.DRV (125,712 bytes,
    
       3-10-92 3:10am).
    
    
    
       To make sure LANDesk Manager Setup has enough memory to build the
    
       LANDesk  Control Panel, press Ctrl+Esc before running Setup on the
    
       LANDesk Manager  administrator workstation and verify that only Program
    
       Manager is running.  Use the EMM386.EXE memory manager as documented in
    
       the DOS Environment  section. If you encounter an Undefined Dynalink
    
       error, see the next section.
    
    
    
       If you experience problems with Windows, make sure your Windows 
    
       environment accesses the files listed below (all time stamped 12:00
    
       a.m.)  that are supplied with LANDesk Manager. We update any older
    
       versions found  and rename them with a .LD extension. These files are
    
       also in the  administrator's network directory (default SYS:LANDESK).
    
       Some of the files  are unexpanded as on the diskettes (for example,
    
       NETAPI.DL_). Windows'  EXPAND.EXE makes them the same size with a
    
       different date. SYSTEM.INI  should be as documented on page 17 of the
    
       LANDesk Manager Setup Guide.
    
    
    
       LANDesk Manager         LANDesk Manager v1.51
    
       CTL3D.DLL      20976    08-16-93   CTL3D.DLL     20976   08-16-93
    
       I3DCTRLS.DLL   23552    07-15-93   I3DCTRLS.DLL  23552   07-15-93
    
       IDISPLAY.DLL   110608   09-30-93   IDISPLAY.DLL  110608  10-28-93
    
       NWIPXSPX.DLL   32176    03-10-93   NWIPXSPX.DLL  38544   11-02-93
    
       NWNETAPI.DLL   106047   01-23-92   NWNETAPI.DLL  106884  01-07-93
    
       VIPX.386       23850    05-11-93   VIPX.386      23855   10-11-93
    
       VMON.386       30822    11-04-93   VMON.386      30822   11-04-93
    
       VNETWARE.386   15133    06-29-93   VNETWARE.386  15133   11-19-93
    
       VUSER.386      11242    11-04-93   VUSER.386     12077   01-28-94
    
       WLS.DLL        36368    08-12-93   WLS.DLL       36368   03-02-94
    
       WUSER.EXE      67600    11-04-93   WUSER.EXE     67600   11-18-93
    
    
    
    

    CALL TO UNDEFINED DYNALINK (NO ICONS IN CONTROL PANEL)

    
       Windows* uses resources called DynaLink Libraries. These files most
    
       often have a .DLL extension, but some developers give them a .DRV
    
       extension. When an application (for example, LANDesk(R) Manager's
    
       SETUP.EXE or TM.EXE) makes a call to Windows for a resource, Windows
    
       searches in the following order/steps:
    
    
    
         1. Windows looks to see if the DLL is already loaded in memory. If the
    
            DLL is already loaded, Windows increments the 'in-use' count of the
    
            DLL, and uses the loaded DLL. If it is the wrong version, an error
    
            message is generated. If the DLL isn't loaded, Windows moves to
    
            Step 2.
    
    
    
         2. Windows searches the Windows directory (i.e., C:\WINDOWS or
    
            F:\USER\USERNAME\WIN31, the location of WIN.COM, WIN.INI,
    
            SYSTEM.INI, etc.)
    
    
    
         3. Windows searches the Windows SYSTEM directory (i.e.
    
            C:\WINDOWS\SYSTEM); this directory does not exist in a network
    
            installation of Windows--the files are stored in the network shared
    
            Windows directory.
    
    
    
         4. Windows searches the directory from which Windows was launched
    
            (where your command line prompt was at the time WIN.COM was
    
            executed).
    
    
    
         5. Windows searches the current directory where the executable ran.
    
    
    
         6. Windows searches the DOS search path.
    
    
    
         7. Windows searches the network search path.
    
    
    
       The undefined dynalink error usually means an older .DLL was already in
    
       memory. In a rare circumstance, it means the .DLL could not be found. If
    
       the error occurs the installation file-copy process, then it is entirely
    
       a  Microsoft issue--during this phase, we hand everything over to a
    
       generic MS install routine. You may solve the problem by removing any
    
       MS*.DLL files from the Window's search path directories listed above. If
    
       the error occurs outside of the file copy process, remove NWCALLS.DLL,
    
       NWNETAPI.DLL, NWIPXSPX.DLL, and CTL3D.DLL from the Windows search path
    
       before running SETUP.EXE again.
    
    
    
       Perhaps the quickest and most reliable approach to overcome the
    
       Undefined Dynalink Error is to use a fresh copy of Windows to install
    
       LANDesk Manager to the network. This builds the LANDesk Control Panel
    
       icons. You can then return to the original copy of Windows and run
    
       SETUP.EXE from the administrator's LANDESK directory (default is
    
       SYS:LANDESK) to set up that copy of Windows as a LANDesk Manager
    
       administrator workstation.
    
    
    
    

    THE LOGIN PROCESS

    
       Intel Corporation provides LOGIN.COM to allow
    
       terminate-and-stay-resident  (TSR) programs to load from the system or
    
       user login scripts. By default,  LANDesk(R) Manager loads the USER and
    
       LANSEL TSRs during the login process. To  make sure LOGIN.COM is
    
       executed from a file server where LANDesk Manager is  installed, place
    
       PREFERRED SERVER=servername in the NET.CFG or use the  parameter
    
       PS=servername when loading NETX. Page 21 of the LANDesk Manager  Setup
    
       Guide shows our default system login script modifications. Pages 32-36 
    
       provide additional information on the login process, TSR options, etc.
    
    
    
       LANDesk Manager loads two TSRs from the system login script. First,
    
       USER.COM allows (among other things) workstations to be viewed.
    
       LANSEL.EXE,  the second client agent, enables (among other things) Chat
    
       and File  Transfer to run. Without LOGIN.COM, TSRs that are required to
    
       be loaded at  login time are typically loaded from batch files that are
    
       invoked with an  EXIT "<batch file>" command from a login script.
    
    
    
       Because it would be  difficult for the Setup program to locate all the
    
       batch files that are  loaded on a network, we use the supplement
    
       LOGIN.COM and load the client  agents from the system login script.
    
    
    
       Because a .COM file runs before an .EXE file, when a user types LOGIN,
    
       the LOGIN.COM program will run if it is present and do the following:
    
    
    
            * Allocate the rest of base memory MINUS the size of LOGIN.EXE.
    
            * Load LOGIN.EXE into the remaining memory.
    
            * Deallocate the rest of base memory.
    
            * Execute LOGIN.EXE.
    
    
    
       When the TSR "terminates and stays resident," the memory used by
    
       LOGIN.EXE  is not trapped or wasted. After LOGIN.EXE finishes, the TSRs
    
       are loaded.
    
    
    
       Sabre Systems' login supplement could conflict with LOGIN.COM. One
    
       customer  had LOGIN.COM working successfully with Sabre by using NETX
    
       v3.22, but NETX  v3.22 doesn't support COMSPEC commands in login
    
       scripts, which may affect  LOGIN.COM. Since Sabre can execute batch
    
       files after logging in, many Sabre  users avoid LOGIN.COM and load the
    
       TSRs in batch files.
    
    
    
       Run LOGIN.COM from the same directory as the one containing LOGIN.EXE. 
    
       (LOGIN.COM only looks for LOGIN.EXE in the same directory.) With some 
    
       versions of LOGIN.EXE, diskless workstations cannot find COMMAND.COM
    
       after  logging in to the network. Check SHELL and COMSPEC settings in
    
       AUTOEXEC.BAT.
    
    
    
       If you don't want to use LOGIN.COM, since LOGIN.COM only allows TSRs to 
    
       load from a NetWare* login script, they can be loaded outside the login 
    
       process. If the LANDesk Manager client TSRs load from a batch file that
    
       is  invoked from a login script via the "EXIT" command or in the
    
       AUTOEXEC.BAT  file after logging into the network (or if they aren't
    
       loaded at all),  LOGIN.COM is not necessary. Rename (or delete)
    
       LOGIN.COM in both the  SYS:LOGIN and SYS:PUBLIC directories. In the
    
       system login script, REMark  out (or delete) the lines for OK4TSRS or
    
       LOADTSR, USER, LANSEL, warning  messages, and the pause used if
    
       LOGIN.COM is gone.
    
    
    
       The LANDesk Manager v1.5 Setup program placed a line in the system login
    
       script to call the program OK4TSRS.EXE (LOADTSR.EXE in v1.51), which
    
       reports if LOGIN.COM has run and if it's safe to load the LANDesk 
    
       Manager client agents (TSRs) into base memory from the login script.
    
       This  safety feature should prevent users from suddenly being 70-150K
    
       short on  memory and creating havoc on a workstation.
    
    
    
       PUSHPOP.EXE is new to LANDesk Manager v1.51 and supports NetWare v4.x's
    
       driver letter requirment for executing programs in a login script. 
    
       NetWare v3.11 and NetWare v3.12 don't require PUSHPOP.EXE.  Select any
    
       drive mapped to the same volume as the shared LANDESK directory to run
    
       LDISCAN.EXE, WKSTACFG.EXE, and the Desktop Access TSRs.  For example:
    
    
    
       rem #PUSHOP +L:\\SERVERNAME\SYS\LOGIN\LANDESK\SELTEMP
    
       rem MAP L:=\\SERVERNAME\SYS\LOGIN\LANDESK
    
       #sys:login\landesk\ldiscan /v /s=servername
    
    
    
       #sys:login\landesk\wkstacfg /o /l=sys:login/landesk/seltemp
    
       #sys:login\landesk\loadtsr user
    
       #sys:login\landesk\loadtsr lansel
    
       rem #PUSHPOP -L:\\SERVERNAME\SYS\LOGIN\LANDESK\SELTEMP
    
    
    
    

    UPGRADING FROM UNINSTALLED V1.X

    
       This section is for customers who registered or purchased a copy of
    
       LANDesk(R) Manager v1.0x but never installed it.
    
    
    
         1. Log in (or attach) as user SUPERVISOR to the file server you  want
    
            to serialize.
    
    
    
         2. Insert diskette #1 from a copy of LANDesk Manager v1.0x not
    
            currently serialized on any other file server.
    
    
    
         3. From Windows* Program Manager, choose File|Run and enter A:\SETUP 
    
            or B:\SETUP.
    
    
    
         4. Choose Continue on the Welcome to Intel LANDesk Setup window,  then
    
            choose the LANDesk Manager Setup option (the top icon).
    
    
    
         5. Choose Continue on the NetWare* LANDesk Group Information window 
    
            (only in the v1.02 installation).
    
    
    
         6. Set the installation paths to the proper drive mapping(s) on the 
    
            file server you are serializing, even though you do not intend to
    
            have  SETUP install any files. Confirm the file server selection.
    
    
    
         7. De-select all features in the Select LANDesk Manager Features 
    
            Window and remove diskette #1 from the drive before choosing
    
            Continue. The  Serializing LANDesk on server SERVERNAME window
    
            appears.
    
    
    
         8. Choose Cancel on the window about a missing diskette; then  choose
    
            Exit on the Insert Setup Disk window.
    
    
    
         9. Choose Exit then OK on the LANDesk Manager Setup windows  warning
    
            you of an incomplete installation.
    
    
    
       Now run SETUP.EXE from diskette #1 of your v1.5x upgrade as documented
    
       in  the LANDesk Manager Setup Guide.
    
    
    
    

    INSTALLING LANDESK(R) MANAGER TO MULTIPLE FILE SERVERS

    
       The best option for installing LANDesk(R) Manager v1.5x to multiple file
    
        servers is to run SETUP.EXE from diskette, following the instructions
    
       in  the LANDesk Manager Setup Guide. To distribute manually, do as
    
       follows:
    
    
    
         1. Log in (or attach) as user SUPERVISOR to the file server where  you
    
            want to install and serialize.
    
    
    
         2. Copy SERIAL.DLL from diskette #1 of a copy of LANDesk Manager 
    
            v1.5x that is not currently serialized on any other file server to
    
            the  administrator's network directory (default SYS:LANDESK).
    
    
    
         3. From Windows* Program Manager, choose File|Run 
    
            SYS:LANDESK\LDSERIAL.EXE.
    
    
    
         4. Select the file server, choose serialize, and exit LDSERIAL.EXE.
    
    
    
         5. Remember to make the following changes that SETUP.EXE would  have
    
            made for the new file server.
    
    
    
           *   Create the LOGIN directory and copy the files. Give rights to
    
              the  SELTEMP subdirectory with GRANT ALL TO EVERYONE. The
    
              administrator's  network directories do not have to be copied.
    
    
    
           *   Copy CONTROL.NLM, MONIT386.NLM, LDINV.NLM, LDISCAN.NLM, and 
    
              USER.NLM to SYS:SYSTEM.
    
    
    
               Note:  Page 43 in the LANDesk Manager Setup Guide  supplements
    
              these reminders for administrators who need to remove LANDesk 
    
              Manager before moving it to another file server.
    
    
    
           *   Modify NET$LOG.DAT and AUTOEXEC.NCF. See pages 22-23 in the 
    
              LANDesk Manager Setup Guide.
    
    
    
           *   Reference the LDSETUP.LOG file in SYS:LANDESK and copy the right
    
               files to SYS:PUBLIC. LOGIN.COM must be in SYS:LOGIN and
    
              SYS:PUBLIC to load  TSRs during the login process.
    
    
    
    

    INSTALLING LANDESK(R) MANAGER WITH NETWARE* V4.X

    
       LANDesk(R) Manager v1.5x supports NetWare* v4.x in bindery-emulation
    
       mode.
    
    
    
         *  Set the bindery context to the appropriate OU (Organizational Unit)
    
            for the file server where LANDesk Manager will be installed.  If
    
            this has not been done, you will not be able to install LANDesk
    
            Manager or login and use bindery calls which are required by v1.51.
    
    
    
         *  Have users log in using /B.  This will force bindery emulation and
    
            allow the administrator to control and receive information about
    
            user's workstations.
    
    
    
         *  Make sure all users belong to the same OU at the server were you're
    
            installing LANDesk Manager.  A configuration with users in separate
    
            OUs is not supported.
    
    
    
         *  Ensure the user installing LANDesk Manager has supervisory rights. 
    
            The user installing LANDesk Manager must be equivalent to Admin so
    
            the Network Operating System will recognize the user's rights. 
    
            Create a username "SUPERVISOR' in the same OU as the file server
    
            where LANDesk Manager is being installed.  Make SUPERVISOR
    
            equivalent to Admin.  Admin rights do not have to remain with the
    
            user after the installation is complete and the Security Access
    
            Rights for Desktop Access are set up. You may want to leave
    
            [SRWECMFA] rights with the SUPERVISOR user for changes to the SYS:
    
            volume on this server.
    
    

    Trademark information