[Intel Navigation Header]

    LANDesk(R) Manager 1.51: Desktop Access Usage Tips

    Contents:

    • GENERAL NETWARE* ENVIRONMENT
    • WORKSTATION CONFIGURATION
    • DOS ENVIRONMENT
    • WINDOWS* ENVIRONMENT
    • CREATING A DEFAULT SECURITY TEMPLATE
    • WUSER.EXE TROUBLESHOOTING TIPS FOR DESKTOP ACCESS AND LANSIGHT V4.0
    • MOUSE AND KEYBOARD CONTROL TROUBLESHOOTING TIPS
    • MISCELLANEOUS USAGE TIPS
    • WUSER.EXE, VIPX.386, OR USER.COM ARE REPORTED TO BE THE WRONG VERSION.
    • SVGA SUPPORT
    
    

    GENERAL NETWARE* ENVIRONMENT

    
       Desktop Access is Novell-certified for NetWare* v3.11 and NetWare v3.12.
    
        LANDesk(R) Manager v1.51 officially supports NetWare v4.0x (bindery
    
       emulation). NetWare v4.1 will be officially supported as soon as
    
       possible.
    
    
    
       Note:     With NetWare v4.0x, USER.NLM loads with 3 outdated API
    
       messages but functions perfectly. SFTIII NetWare is not officially
    
       supported, but many customers successfully control workstations.
    
       USER.NLM detects SFTIII and refuses to load, but Desktop Access can
    
       still control workstations.
    
    
    
    

    WORKSTATION CONFIGURATION

    
       This section details the Desktop Access workstation environment.
    
    
    
       The administrator and target PCs require ODI drivers with VLMs or NETX
    
       v3.22 or higher. Use the NetWare*/Windows* drivers previously called
    
       WINUP9, or later releases, now known as NWDLL?.EXE, VLMUP?.EXE,
    
       WINDR?.EXE, and NET33X.EXE (self-extracting zip files located in
    
       Novell's NetWire on CompuServe).
    
    
    
       Use a matching set of LSL.COM and IPXODI.COM files (using a version in
    
       the left column that doesn't match the version on the same line in the
    
       right column will cause problems with workstation control). The
    
       following versions of LSL.COM were released with the corresponding
    
       version of IPXODI.COM:
    
    
    
            LSL.COM   IPXODI.COM
    
            -------   ----------
    
            v2.00*    v2.00*
    
            v2.01*    v2.10*
    
            v2.02     v2.11
    
            v2.05/6   v2.12
    
            v2.12     v3.00
    
            v2.14     v3.01
    
    
    
            * Upgrade administrator and target PCs to at least LSL v2.02 and
    
            v2.11 supplied on the Spry Drivers diskette or later.
    
    
    
       Every target workstation must load USER.COM, a 5KB TSR, before Desktop 
    
       Access can take control of it. For full functionality, DOS workstations
    
       use LANSEL.EXE and Windows workstations use WUSER.EXE. LANSEL.EXE is a
    
       6KB DOS TSR, and WUSER.EXE is a Windows program. Intel supplies
    
       LOGIN.COM to allow the TSRs USER.COM and LANSEL.EXE to be loaded during
    
       the Novell login process. See document 5539 for more details on
    
       LOGIN.COM, PUSHPOP.EXE, or LOADTSR.EXE. Unlike LANSEL.EXE, USER.COM can
    
       be loaded into upper memory (/LH switch).
    
    
    
       DOS workstations need LANSEL.EXE if Desktop Access must generate a
    
       dialogue box for user input (for example, if Chat and File Transfer will
    
       be used or if user permission is required before controlling the target
    
       workstation).  Windows workstations require WUSER.EXE for super VGA
    
       support and faster screen refreshes. LANSEL.EXE is not required when
    
    
    
       Windows is loaded because WUSER.EXE generates any necessary dialogue
    
       boxes.
    
    
    
       Windows workstations must run the configuration program WKSTACFG.EXE in
    
       DOS before the PC can be controlled in Windows. WKSTACFG.EXE is a
    
       one-time program  (NOT a TSR) that runs by default in the system login
    
       script. WKSTACFG.EXE  details and changes are found on page 29 of the
    
       LANDesk(R) Manager Setup Guide.
    
    
    
       Note:     WKSTACFG.EXE was developed before Windows for Workgroups and
    
       does not accurately determine if WFW is configured for NetWare.  Ignore
    
       the cosmetic message about this copy of Windows not being configured for
    
       NetWare.
    
    
    
       Note:     Desktop Access (WSIGHT.EXE) only requires WUSER.EXE on a
    
       target  Windows workstation, not on the administrator workstation. Since
    
       Desktop Remote and WUSER.EXE cannot run at the same time, the
    
       administrator workstation can run Desktop Remote and still control other
    
       workstations.
    
    
    
    

    DOS ENVIRONMENT

    
       This section details Desktop Access memory requirements.
    
    
    
       Note:     If you are having problems with a memory manager besides
    
       EMM386 (for example, QEMM, QEMM Stealth Mode, or 386MAX), use EMM386
    
       instead.
    
    
    
       When using MS-DOS v5.0 or v6.x, the following sample environment leaves
    
       about 600KB of conventional memory for the largest executable program
    
       size.
    
    
    
       CONFIG.SYS:
    
    
    
       device=c:\windows\himem.sys
    
       device=c:\windows\emm386.exe noems
    
       dos=high, umb
    
       buffers=20
    
       files=40
    
       shell=c:\command.com c:\ /p /e:1024
    
    
    
       AUTOEXEC.BAT
    
    
    
       @echo off
    
       prompt $p$g
    
       path c:\windows;c:\dos
    
       lh c:\mouse\mouse
    
       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

    
       Each Windows* workstation must be configured for NetWare*.  Use Windows
    
       SETUP.EXE and install the network option (i.e., NETX v3.26 and
    
       above)--this requires Windows diskette #2 and supplies the necessary
    
       NETWARE.DRV (125,712 bytes, 3-10-92 3:10am).   Desktop Access requires
    
       386 Enhanced Mode. Also, pay strict attention to the ODI drivers and
    
       NetWare/Windows file requirements listed in the section Workstation
    
       Configuration.
    
    
    
       Windows for Workgroups must not use the IPX/SPX compatible transport
    
       (with or without NetBIOS) in the Network Setup because this transport
    
       uses NWLINK.DLL. Microsoft has recommended that we avoid using the
    
       NWLINK driver. Instead, use Microsoft NetBEUI for your workgroup
    
       connectivity. 
    
    
    
    

    CREATING A DEFAULT SECURITY TEMPLATE

    
       When USER.COM loads for Desktop Access, Chat, or File Transfer, it
    
       checks the primary server's bindery for default security settings. Use
    
       the following steps in Desktop Access (WSIGHT.EXE) to choose your
    
       settings:
    
    
    
         1. Enter Desktop Access from the LANDesk(R) Control Panel.
    
    
    
         2. Choose Tools|Control Options|Server Default Security.
    
    
    
         3. Choose OK (regardless of whether you change any settings or not).
    
    
    
       The NetWare* v4.0x bindery context contains the serialization
    
       information. See document 5539 for more information.
    
    
    
    

    WUSER.EXE TROUBLESHOOTING TIPS FOR DESKTOP ACCESS AND LANSIGHT V4.0

    
       This section contains common issues to check to make sure that the
    
       programs are loaded properly.
    
    
    
         *  Make sure USER.COM has been loaded. The DOS command MEM /C will
    
            show if USER.COM really is in conventional or upper memory.
    
            USER.COM loads if it finds LANDesk(R) Manager serialized on the
    
            primary file server.
    
    
    
         *  Make sure that system login script (NET$LOG.DAT) changes were
    
            accepted the last time SETUP.EXE ran from diskette #1. If only
    
            group LANDESK loads USER.COM, make sure the group contains the
    
            appropriate users.
    
    
    
         *  Remove WLANSEL.EXE from the Windows* Startup group and/or the  RUN=
    
            line of WIN.INI--LANDesk Manager v1.0x installations used
    
            WLANSEL.EXE.
    
    
    
         *  If FAXNODE (a TSR from another product) loads at the workstation,
    
            load it after USER.COM but before LANSEL.EXE. Loading FAXNODE
    
    
    
            before both USER and LANSEL can also suffice as advised in the
    
            Setup Guide.
    
    
    
         *  If Alcom LANFAX's TSR loads, load it after USER.COM.
    
    
    
         *  If none of the above tips remedy a wrong version or memory message,
    
            use the latest IDISPLAY.DLL and WUSER.EXE in DTAC.EXE on the
    
            Intel's online services in the LANDesk Manager current area. They
    
            utilize Window's upper memory pool better than before. The
    
            IDISPLAY.DLL also includes a change for the v7.34 Compaq Qvision
    
            video drivers that may also improve the transfer of graphics for
    
            programs such as Lotus and WordPerfect.
    
    
    
    

    MOUSE AND KEYBOARD CONTROL TROUBLESHOOTING TIPS

    
       This section contains common issues to check in a Desktop Access
    
       installation to ensure mouse and keyboard control function properly.
    
    
    
         *  Load the mouse driver before loading USER.COM, LANSEL.EXE, and
    
            Windows* on both the LANDesk(R) Manager workstation and the target
    
            station.  Logitech mouse drivers need to load in conventional
    
            instead of upper memory.
    
    
    
         *  Make sure WUSER.EXE is in the Windows Startup group or you have
    
            run=WUSER.EXE included in your WIN.INI.
    
    
    
         *  WLANSEL.EXE is being used with WUSER.EXE.  Remove WLANSEL.EXE from
    
            the RUN=       line in the WIN.INI and/or remove WLANSEL.EXE from
    
            the Windows Startup Group.
    
    
    
         *  Set keyboard stuffing to interrupt-driven; if results are not
    
            perfect, try BIOS. If viewing an EGA or VGA screen, choose
    
            Configure...  from the upper left horizontal bar and activate
    
            Accelerated Mode. Make sure both stations have a mouse connected to
    
            them.
    
    
    
         *  Ensure that VUSER.386 is loaded in the SYSTEM.INI file on both
    
            stations and that MOUSE.DRV is in the Windows SYSTEM directory (we
    
            use Windows MOUSE.DRV, not IMOUSE.DRV or ILMOUSE.DRV).
    
    
    
         *  Make sure that you have only one instance of VUSER.386 in the
    
            SYSTEM.INI's [386enh] section.
    
    
    
         *  If you have Windows for Workgroups, don't use the IPX/SPX
    
            compatible transport.  In Windows for Workgroups Network Setup,
    
            highlight the "IPX/SPX Compatible Transport" underneath the adapter
    
            and choose Remove.
    
    
    
         *  The Qemm memory manager is using stealth mode.  Try using
    
            EMM386.EXE or not using stealth mode with Qemm.
    
    
    
    

    MISCELLANEOUS USAGE TIPS

    
       This section contains miscellaneous information about Desktop Access.
    
    
    
       WKSTACFG.EXE does not search its launch directory for Windows*  files.
    
    
    
       In certain network installations of Windows where the user's personal
    
       directory is not in the DOS or NetWare* search path, place the user's
    
       personal directory temporarily in the search path in order for
    
       WKSTACFG.EXE to properly update all of the necessary files.
    
    
    
       WUSER.EXE loads "silently" with the syntax WUSER.EXE /nosplash in its
    
       Startup icon. Windows WIN.INI does not accept options when loading 
    
       programs. USER /lh /stealth loads USER.COM silently into upper memory.
    
    
    
       Several lines in the LANDesk(R) Manager section of the system login
    
       script follow the Universal Naming Convention (UNC) supported by
    
       NetWare.  For example, #\\SERVERNAME\SYS \LOGIN\LANDESK\USER.  This
    
       change in LANDesk  Manager v1.5 allows programs to correctly reference
    
       the directory where they loaded from.
    
    
    
       LANDesk Manager v1.51 began shipping PUSHPOP.EXE to meet a NetWare v4.x
    
       requirement that a drive letter be used to run programs from the login
    
       script. Whether drive L: is mapped or not, PUSHPOP.EXE temporarily
    
       assigns L: to the shared LANDESK directory to run LDISCAN.EXE, 
    
       WKSTACFG.EXE, and LOADTSR.EXE.  LOADTSR.EXE loads USER.COM and
    
       LANSEL.EXE  into memory. NetWare v3.11 and v3.12 file servers don't need
    
       PUSHPOP.EXE.  See document 5539 for more details.
    
    
    
       Desktop Access does not support IPX because Novell ceased making their
    
       Windows VIPX.386 file backwards compatible with IPX (v3.1) beginning 
    
       with VIPX.386 v1.13 (and we've seen v1.15 and v1.17 since then).
    
    
    
    

    WUSER.EXE, VIPX.386, OR USER.COM ARE REPORTED TO BE THE WRONG VERSION.

    
       Product:  LANSight v4.0 & LANDesk(R) Manager, Component: Desktop Access
    
    
    
       Symptom:
    
       When Windows* tries to load WUSER.COM, WUSER will not load with the
    
       error; "Resident USER.COM is the wrong version.
    
    
    
       Note:     Similar error messages can given for the files VIPX.386 and
    
       USER.COM.
    
    
    
       Description:
    
       Apparently this error can still occur even though the files involved
    
       match what  ships in v1.51 and are being accessed correctly (including a
    
       working directory in the icon properties for WUSER.EXE):
    
    
    
       USER.COM  32,560  03-14-9412:00a  
    
       WUSER.EXE 67,600  11-18-9312:00a 
    
    
    
       This error occurs when you  upgrade from a previous version of LANDesk
    
       Manager but choose NOT to update your system login script (NET$LOG.DAT).
    
       The differences in the loading of the Desktop Access TSRs affects
    
       WUSER.EXE accurately sensing USER.COM in memory.
    
    
    
       Solution:
    
    
    
         *. Run the v1.51 update or installation again (SETUP.EXE from Disk 1),
    
            and this time allow the system login script to be modified
    
            correctly.
    
    
    
         *  WLANSEL is still loading from LANDesk Manager 1.02.  Check the
    
            startup group for WLANSEL and remove it.  Check the WIN.INI and the
    
            SYSTEM.INI for any lines that have WLANSEL in them and remove these
    
            lines.
    
    
    
         *  FAXNODE, (a TSR from another product) is loading in the wrong place
    
            in memory at the workstation.  Load FAXNODE, then USER.COM, then
    
            FAXPOP (if used) and LANSEL.EXE.  The latest version of Net
    
            Satisfaxtion does not require FAXNODE if Windows is running.
    
    
    
         *  USER.COM and ALCOM FAX share the same multiplex ID INT2F with the
    
            hex value CB (203 in decimal).  Add the /mpx:204 option to the load
    
            line of ALCOM FAX's TSR, WKS_IPX.EXE. Whatever options the user is
    
            currently using is not reflected in this example of the syntax:
    
    
    
                 WKS_IPX /mpx:204
    
    
    
            ALSO, the Alcom workstation software must be configured to use
    
            multiplex 204. If in DOS, the user would load FAXMGR2.EXE /mpx:204
    
            (this is for v2.1; v2.15 users omit the colon on this one). If
    
            users load Alcom's print capture utility, they would use the syntax
    
            LANFAX7.COM /mpx:204. If in Windows, the Alcom v2.15 Gamma-Link
    
            user would access the Windows Control Panel where Alcom added three
    
            icons; choose the LanFax CASDLL icon. A screen appears with
    
            Multiplex Number as one of the fields; change that to 204 and
    
            choose OK to store the changes in the LanFax Windows configuration.
    
            If in Windows, the Alcom v2.1 user must modify the WIN.INI file.
    
            They add the [CASDLL] section with one line: Multiplex=204 and save
    
            the changes to affect the LanFax Windows configuration
    
    
    
            Alcom supports 203 as the multiplex default (same as WUSER.EXE);
    
            204-209 are valid choices.
    
    
    
    

    SVGA SUPPORT

    
       Product: LANSight v4.0 &  LANSight, LANDesk(R) Manager, Component: 
    
       Desktop Access
    
    
    
       You need to make sure that the three items listed below are in place.
    
    
    
         WUSER.EXE must be loaded for SVGA to be controlled.
    
         Both stations must be in Window*. 
    
         WUSER.EXE will not load if the station is in Standard Mode or in DOS.
    
    
    
       Note:     Desktop Access and LANSight do not check the video mode if
    
       WUSER.EXE has been loaded.
    
    
    
       Note:     Testing has reported that v4.0 USER.COM worked with all video
    
       modes up to 1280x1024 with 16.7M colors.
    
    

    Trademark information