[Intel Navigation Header]

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

    Contents:

    • CONTENTS
    • WHEN INTEGRATING LANDESK(R) VIRUS PROTECT V2.1X AND LANDESK MANAGEMENT SUITE, THE WRONG PSCAN.NLM LOADS
    • POSSIBLE ISSUES WHEN INTEGRATING WITH LANDESK(R) VIRUS PROTECT V3.0
    
    

    CONTENTS

    
       This document discusses issues commonly encountered when integrating
    
       with other products.  It supplements the files in LANDesk(R) Management
    
       Suite's Readme Viewer.
    
    
    
    

    WHEN INTEGRATING LANDESK(R) VIRUS PROTECT V2.1X AND LANDESK MANAGEMENT SUITE, THE WRONG PSCAN.NLM LOADS

    
       Symptom:
    
       LANDesk(R) Management Suite does not recognize the PSCAN.NLM correctly
    
       therefore either Relay does not load or Metering does not function
    
       correctly.
    
    
    
       Description:
    
       The common cause of this is that the PSCAN.NLM for LANDesk Virus Protect
    
       v2.1x gets loaded out of the SYS:\LPROTECT directory on the server. The
    
       PSCAN.NLM that is required for LANDesk Management Suite loads out of the
    
       SYS:\SYSTEM directory. The actual PSCAN.NLM that gets loaded first is
    
       usually out of the SYS:\LPROTECT directory.
    
    
    
       Solution:
    
       Copy the SYS:\SYSTEM\PSCAN.NLM to SYS:\SYSTEM\PSCAN.NLM then copy the
    
       SYS:\SYSTEM\PSCAN.NLM to SYS:\LPROTECT\PSCAN.NLM
    
    
    
    

    POSSIBLE ISSUES WHEN INTEGRATING WITH LANDESK(R) VIRUS PROTECT V3.0

    
       LANDesk(R) Virus Protect v3.0 has a new feature that is refered to as
    
       the Integrity shield.  It is a feature that will prevent ANY user from
    
       modifying protected file extensions in the protected directories.
    
    
    
       By default all users, (including SUPERVISOR or ADMIN) will not be able
    
       to create, rename, delete, modify or change in any way  files with the
    
       extensions .EXE .COM .SYS .BIN .OVL the directories that are protected
    
       are SYS:\SYSTEM SYS:\PUBLIC, and SYS:\LOGIN.
    
    
    
       These are only defaults and can be changed.  By protecting these
    
       directories, some functions may be inhibited (like BINDFIX... which
    
       tries to correct potential errors in .SYS files like NET$BIND.SYS )
    
    
    
       If you experience problems performing NORMAL functions, it would be wise
    
       to make sure that the activities do not conflict with your current
    
       Integrity Shield Configuration.
    
    
    
       Steps that help to debug this.
    
    
    
       Enable the NOTIFICATION from integrity shield violations by:
    
    
    
       1. Run VPWIN.EXE and unlock the domain
    
       2. Select Configure | File Checking
    
       3. Select the "RealTime" tab
    
       4. Click on the "Notify" button
    
       5. The bottom area of the Dialogue that comes up is for
    
    
    
       Integrity Shield Notification:
    
    
    
       Click on the box to ENABLE notifying to LOG and Server Console
    
       Save changes
    
    
    
       Note: If problem occur,  look into the Log file using VPWIN menu item
    
       VIEW | VIRUS LOG.
    
    
    
       Once you know what file(s) need to be accessed or modified, you can make
    
       an intelligent decision on how to adjust the integrity shield to meet
    
       your needs. For example, you may want to exempt directories or files or
    
       temporarily exempt a user.
    
    
    
       For integration information on ManageWise*, NMS, Optivity for NMS, HP
    
       OpenView for Windows* or DEC ManageWORKS Workgroup Administrator see the
    
       Intel LANDesk Management Suite Setup Guide Chapter 3. 
    
    
    
       Note: ManageWise snapin requires LANDesk Management Suite v2.01a  or
    
       newer. 
    
    

    Trademark information