[Intel Navigation Header]

    LANDesk(R) Management Suite v2.x: Metering Usage Tips

    Contents:

    • CONTENTS
    • METERING DOES NOT ACCURATELY SHOW APPLICATIONS IN USE AS CONFIGURED
    • DESKTOP REMOTE TROUBLESHOOTING - LANDESK(R) MANAGEMENT SUITE V2.0X
    • "RELAY ERROR: RELAY CAN NOT COMMUNICATE WITH PSCAN.NLM. MAKE SURE PSCAN'S VERSION CORRECTLY MATCHES THE NETWARE VERSION. OR RELOAD PSCAN.NLM"
    • COULD NOT ATTACH TO PRE-SCAN PROTOCOL STACK" OR "PSCAN: COULD NOT ATTACH PRE-SCAN DRIVERS"
    • DOS APPLICATION LICENSES ARE NEVER REMOVED FROM THE METERED LIST
    • METERWIN.EXE DOES NOT APPEAR TO BE FUNCTIONING
    
    

    CONTENTS

    
       This document discusses issues commonly encountered with Software
    
       Metering.  It supplements the files in LANDesk(R) Management Suite's
    
       Readme Viewer.
    
    
    
    

    METERING DOES NOT ACCURATELY SHOW APPLICATIONS IN USE AS CONFIGURED

    
       Symptom:
    
       User knows it is configured accurately, but the LANDesk(R) Management
    
       Suite metering console shows no licenses used even though the
    
       application is running.
    
    
    
       Description A:
    
       RELAY.NLM is not loaded (METER.NLM is also required, but the metering
    
       console won't load without it running).  The Meter Map will show the
    
       server "greyed out" as well.
    
    
    
       Solution A:
    
       Slow servers (like 386s) may not autoload RELAY.NLM when LD_AUTO.NCF
    
       executes. Manually load RELAY.NLM with the syntax LOAD RELAY
    
       <ServerName>.  If RELAY.NLM is unable to load because PSCAN.NLM doesn't
    
       load, see: "Could not attach to pre-scan protocol stack " or " PSCAN:
    
       Could not attach to prescan drivers."
    
    
    
       Description B:
    
       LANDesk Management Suite v2.01a and below only monitors .EXE and .COM
    
       files from the file server.
    
    
    
       Solution B:
    
       Upgrade to LANDesk Management Suite v2.01b or higher, which now supports
    
       .DLL metering functionality.
    
    
    
       Description C:
    
       The file server is running an old version of PSCAN.NLM supplied with
    
       LANDesk Virus Protect or LANProtect.
    
    
    
       Solution C:
    
       Make sure the file server is running a PSCAN.NLM dated no earlier than
    
       1995. Rename the old PSCAN.NLM to something like PSCAN.OLD and rename
    
       the appropriate PSCAN311.NLM or PSCAN312.NLM to PSCAN.NLM (PSCANCH.NLM
    
       can be used on NetWare* v3.11 or NetWare v3.12 file servers running
    
       CLIB.NLM v3.12g or late, and on any 4.x serverr; see the section "Could
    
       not attach to pre-scan protocol stack" or "PSCAN: Could Not Attach
    
       Pre-Scan Drivers" for more information).
    
    
    
    

    DESKTOP REMOTE TROUBLESHOOTING - LANDESK(R) MANAGEMENT SUITE V2.0X

    
       Most Desktop Remote problems in LANDesk(R) Management Suite are
    
       addressed by adjusting the settings under [Manage] menu at your Control
    
       Panel.  Chose Manage|Events (chose your event, or <insert> to create
    
       one) Configure| Select tools to Configure, then chose Configure again.;
    
       there are settings for both baud rate and *Flow Control. If you are
    
       having connection problems, choose a lower baud rate  and verify that
    
       the *Flow Control setting matches the setting on the Host PC.  
    
    
    
       Flow Control, or handshaking, prohibits either modem in a data transfer
    
       from overloading the modem on the other end of a communication.  Each
    
       modem sends and receives signals to determine if the other modem is
    
       ready for more data.  If either modem has not processed previous data
    
       yet, the first modem postpones sending more data.  If your modem
    
       communicates at baud rate of 19200 or greater, you should consider using
    
       RTS/CTS hardware regulated flow control.  Refer to your modem's owner's
    
       manual to find out if your modem performs RTS?CTS flow control.
    
    
    
       Under the [Manage] menu, chose Events, chose your event, and Configure. 
    
       The Advance configuration button gives you 
    
    
    
            1) Choice of range of time for the event to occur, 
    
    
    
            2) Let you configure from where the event should occur to initiate
    
       a notification.  
    
    
    
            3) You can also configure  if you want the notification to occur at
    
       the beginning of an event, after an event or to skip multiple
    
       notifications if it happened too close together. 
    
    
    
    

    "RELAY ERROR: RELAY CAN NOT COMMUNICATE WITH PSCAN.NLM. MAKE SURE PSCAN'S VERSION CORRECTLY MATCHES THE NETWARE VERSION. OR RELOAD PSCAN.NLM"

    
       Error message:
    
       RELAY ERROR: Relay can not communicate with PSCAN.NLM. Make sure PSCAN's
    
       version correctly matches the Netware* version. Or reload PSCAN.NLM.
    
    
    
       Description:
    
       This error message occurs when loading the LANDesk(R) Management Suite
    
       NLMs (LD_AUTO.NCF) because RELAY.NLM cannot load until PSCAN.NLM
    
       succesfully loads. LD_AUTO.NCF does not directly load
    
       PSCAN.NLM--RELAY.NLM automatically loads it. 
    
    
    
       Solution:
    
       See the section "Could not attach to pre-scan protocol stack" or "PSCAN:
    
       Could Not Attach Pre-Scan Drivers" for an explanation of why PSCAN.NLM
    
       could not load successfully.
    
    
    
    

    COULD NOT ATTACH TO PRE-SCAN PROTOCOL STACK" OR "PSCAN: COULD NOT ATTACH PRE-SCAN DRIVERS"

    
       Error message:
    
       Error message "Could not attach to pre-scan protocol stack" or "PSCAN:
    
       Could Not Attach Pre-Scan Drivers" occurs when loading the LANDesk(R)
    
       Management Suite NLMs.  Software metering (METER.NLM and RELAY.NLM)
    
       relies on PSCAN.NLM to intercept files.  RELAY.NLM won't load until
    
       PSCAN.NLM loads successfully.
    
    
    
       Description:
    
       PSCAN.NLM may be failing to load because PSCAN.NLM is already loaded or
    
       another application "dirty hooks" files directly through the operating
    
       system on your NetWare* v3.11/3.12 file server. Another possibility is
    
       that a PSCAN.NLM from a NetWare v3.11 file server is loading on a
    
       NetWare v3.12 file server or vice-versa.
    
    
    
       Solution:
    
    
    
         1. Make sure PSCAN.NLM is unloaded (type: UNLOAD PSCAN).
    
    
    
         2. Determine if another NLM is loaded that directly hooks files
    
            through the operating system.  Some of the known products are:
    
            McAfee NetShield, McAfee SiteMeter, Symantec Central Point
    
            AntiVirus, Symantec Norton AntiVirus, Cheyenne Inoculan, Funk
    
            Software AppMeter, LANAuditor, LTAuditor, Microtest DiskPort, and
    
            AuditTrack (ADTTRK.NLM). 
    
    
    
            If this is the case, there is a PSCANCH.NLM already in the
    
            SYS:SYSTEM directory of the core file server (not managed file
    
            servers) as documented in the Readme Viewer release notes for
    
            Software Metering (LDMETER.TXT), item #7.  This new NLM hooks files
    
            through CLIB instead of through the operating system directly. For
    
            this reason, it is required that CLIB v3.12G or later is used
    
            because previous versions did not support file hooking. This "clean
    
            hooks" PSCAN.NLM will work on any 3.x version of NetWare (including
    
            SFTIII). This problem should not happen on a 4.x server, so no fix
    
            is required.
    
    
    
         3. Make sure the correct version of CLIB is running on the file
    
            server.  If an upgrade is required, remember that the currently
    
            running CLIB must be unloaded, which may require that a series of
    
            other NLMs be unloaded first.
    
    
    
         4. Rename or delete the existing PSCAN.NLM in SYS:SYSTEM. If you use
    
            LANDesk Virus Protect, make the same change in the VPROTECT
    
            directory.
    
    
    
         5. Rename PSCANCH.NLM to PSCAN.NLM. Remember to update the PSCAN.NLM
    
            in any VPROTECT directory.
    
    
    
       PSCAN.NLM will now load and not conflict with the other products listed
    
       previously.
    
    
    
       Note:     If the error message continues to appear or the file server
    
       has problems even after updating PSCAN.NLM and CLIB, then reverse the
    
       load order of PSCAN and McAfee SiteMeter or NetShield.  This reversed
    
       load order works best. SiteMeter v4.3 and NetShield v1.61 now both
    
       support clean hooks, which allows other third-party vendors to intercept
    
       files. NetShield upgrades to v1.61 are available in 3NS161RC.ZIP on
    
       McAfee's BBS at 408 988-4004. NetShield prefers CLIB v3.12F and requires
    
       the Novell patches SPXS.NLM and SPXDDFIX.NLM from STRTL3.EXE.
    
    
    
            Symantec Central Point AntiVirus for NetWare v2.5 is the first
    
       release to support clean hooks with a fix in the self-extracting zip
    
       file CPNLM.EXE on their BBS at 503 984-5366. Symantec Norton AntiVirus
    
       for NetWare v1.0 shipped in the last year contains the "clean hooks"
    
       fix.
    
    
    
            Cheyenne Inoculan v3.0 is the first release to support clean hooks
    
       with signature file version v2.31 or later. Download IL0004.ZIP from the
    
       Inoculan Signature File area on Cheyenne's BBS at 516 484-3445. 
    
    
    
    

    DOS APPLICATION LICENSES ARE NEVER REMOVED FROM THE METERED LIST

    
       Symptom:
    
       Despite exiting a DOS application, in LANDesk(R) Management Suite
    
       v2.0xthe license isn't released (metering doesn't decrease the license
    
       count as expected).
    
    
    
       Description:
    
       The DOS application was run under Windows* but not launched from inside
    
       a DOS box. DOS applications launched from a Program Manager icon,
    
       File/Run, or File Manager never send a Netware* End-Of-Task packet. The
    
       license isn't released until the user logs out of the Network. DOS
    
       applications launched from within a DOS box send the End-Of-Task packet
    
       properly and are reflected properly in metering's license count.
    
    
    
       This has been improved with v2.01B so that it releases the license 0% of
    
       the time. But it is still possible for the license not to be freed when
    
       the DOS program exits. The license will always be exited when the user
    
       logs out of the network.
    
    
    
       Solution:
    
       Launch DOS applications under Windows from within a DOS box. 
    
    
    
    

    METERWIN.EXE DOES NOT APPEAR TO BE FUNCTIONING

    
       LANDesk(R) Management Suite v2.01x
    
    
    
       Symptom:
    
       METERWIN.EXE does not appear to be functioning or catching an
    
       application during metering.
    
    
    
       Causes/Solutions:
    
    
    
         *  Make sure that the configurations inside the meter icon have been
    
            done correctly.  Some common mistakes may be
    
    
    
           a.  There is more than one copy of the application that you're
    
              trying to meter.  The configuration may be set for one copy but
    
              you may be using another copy in a different location;
    
    
    
           b.  The user you*re doing your test on is on the <exempt> list that
    
              is defined from under LANDesk Management Suite.
    
    
    
         *  Make sure that METERWIN.EXE is loading.  Check the configuration of
    
            the Load=Meterwin.exe that is in the WIN.INI under Windows*.  If
    
            the meterwin loads successfully then you won't get an error
    
            message.  But it also does not provide an icon.  The way you can
    
            test that METERWIN.EXE is doing its job is by trying to bring up an
    
            application that has been configured to be metered.  The Metered
    
            application will give you an error message at the workstation if
    
            meterwin is not loaded.  if you don't get an error message, that
    
            shows that meterwin is loaded and working.
    
    
    
         *  If two people have a copy of the Control Panel up and they are
    
    
    
            configuring metering, one user may be able to save their changes
    
            and the other could not.  Make sure only one person is making
    
            changes on the metering application at a time.
    
    
    
         *  Unload the METER.NLM for the Core/Management File server and then
    
            reload it.  When it loads, make sure there are not any error
    
            messages referring to PSCAN.NLM while it loads.
    
    
    
         *  As you run modules at the file server, make sure the PSCAN.NLM is
    
            loaded.
    
    
    
         *  If you are running a network version of Windows, make sure you have
    
            followed the instructions concerning a network version of Windows
    
            described in the WKSTACFG.INI in the LANDESK directory 
    
    

    Trademark information