[Intel Navigation Header]

    LANDesk(R) Workgroup Manager Tips: Desktop Manager

    Contents:

    • ERROR MESSAGE: "BTRIEVE ERROR 4 DELETING RECORD." RECEIVED WHEN DELETING A LICENSE RECORD.
    • ERROR MESSAGE: "THERE IS NO INFORMATION TO EXPORT BECAUSE %S DOES NOT EXIST." OCCURS WHEN TRYING TO EXPORT THE CHANGES LOGFILE
    • ERROR MESSAGE: "UNABLE TO OBTAIN A SERVERNAME FOR THIS CONNECTION" WHEN OPENING THE DATABASE
    • ERROR MESSAGE: "THE REMOTE COMPUTER HAS ENTERED A VIDEO MODE THAT IS NOT SUPPORTED BY THE REMOTE CONTROL AGENT...."
    • LDISCAN REPORTS "UNABLE TO ASSIGN DEVICE ID. PLEASE LOAD LDINV.NLM V2.01 OR ABOVE"
    • ERROR MESSAGE: "THE CLIENT HAS ENTERED AN UNSUPPORTED VIDEO MODE"
    • LDISCAN.EXE REPORTS THE ERROR; "NETBIOS DID NOT RESPOND ON LANA NUMBER 0. ERROR: 23H" OR "LDISCAN COULD NOT FIND SERVER PLEASE LOAD LDINV.NLM 2.00
    • REMOTE CONTROL AGENT REPORTS THE ERROR: "UNABLE TO GET WORKSTATION NAME. USEDLANA: 0"
    • LDISCAN DOES NOT APPEAR TO BE WORKING IN ENVIRONMENTS WITH ROUTERS
    • DATABASE WILL SAVE ONLY 5 REVISIONS OF THE CONFIGURATION FILES
    • CONTROLLING CONSOLE'S REMOTE CONTROL SESSION COLORS ARE INCORRECT
    • SCANNING STANDALONE NT WORKSTATIONS: SOFTWARE SCAN INFORMATION DOES NOT GET WRITTEN TO THE OUTPUT FILE.
    • NO REMOTE CONTROL CAPABILITY FOR DOS SESSIONS ON WINDOWS FOR WORKGROUPS* ANDWINDOWS 95* WORKSTATIONS
    • UNABLE TO REMOTELY CONTROL A NETWARE* SERVER THAT IS MANAGED BY LANDESK(R) WORKGROUP MANAGER.
    • USER PERMISSION REQUIRED TO REMOTELY CONTROL A DESKTOP DOES NOT OCCUR AFTER
    • THE FIRST TIME.
    • UNABLE TO FIND INVENTORY LOGFILE "LDINV.ERR" REFERENCED IN THE DOCUMENTATION.
    • LDISCAN.EXE IS NOT REPORTING NEW SOFTWARE ADDED TO THE LDAPPL.INI.
    • UNABLE TO ADD STANDALONE DATA TO SERVER INVENTORY DATABASE.
    • LDISCAN UNABLE TO OPEN THE CFG_YES.LOG OR THE CFG_NO.LOG FILES
    • IPX CLIENTS AND/OR STANDALONE CLIENT WORKSTATIONS ARE NOT REPORTING THE NEW SOFTWARE ADDED TO LDAPPL.INI USING SOFTWARE LIST
    • HOW TO DETERMINE THE LAST COMPLETED INVENTORY SCAN DATE FOR ANY NODE
    • CONFIGURATION LIMIT FOR FILE REVISION SAVES
    • NAMING STANDALONE COMPUTERS FOR INVENTORY PURPOSES
    • RUNNING BOTH LANDESK(R) WORKGROUP MANAGER AND LANDESK MANAGEMENT SUITE ON THENETWORK - COMMON POINT OF INVENTORY DATA COLLECTION
    • WHEN STARTING WINDOWS* FROM A DOS CLIENT, WINDOWS COMES UP BUT NO TEXT FIELDS
    • REMOTE CONTROL SESSION TERMINATES WHEN EXITING A NETBIOS WINDOWS FOR WORKGROUPS AND WINDOWS 95*
    • UNABLE TO PRINT OUT THE ATTACHED NOTES SAVED IN THE INVENTORY DATABASE
    • QUICK METHODS TO VERIFY IF INVENTORY CHANGES WERE MADE
    
    

    ERROR MESSAGE: "BTRIEVE ERROR 4 DELETING RECORD." RECEIVED WHEN DELETING A LICENSE RECORD.

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       The error message "Btrieve error 4 deleting record." is received when
    
       deleting a license record.
    
    
    
       Description:
    
       A BTRIEVE* error 4 indicates the record does not exist.
    
    
    
       Solution:
    
       Make sure you are selecting a valid license object. 
    
    
    
    

    ERROR MESSAGE: "THERE IS NO INFORMATION TO EXPORT BECAUSE %S DOES NOT EXIST." OCCURS WHEN TRYING TO EXPORT THE CHANGES LOGFILE

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       When trying to export the Changes Logfile the error message "There is no
    
       information to export because %s does not exist." occurs.
    
    
    
       Description:
    
       The changes log doesn't exist. 
    
    
    
       Solution:
    
       Verify that the file resides in 
    
       "\\DATABASESERVERNAME\LDWMDB\LOGFILENAME".  If not, you must
    
       configure/create a logfile from the administrator console (Options -
    
       Configure Changes Log). 
    
    
    
    

    ERROR MESSAGE: "UNABLE TO OBTAIN A SERVERNAME FOR THIS CONNECTION" WHEN OPENING THE DATABASE

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       When opening the database the message  "Unable to obtain a servername
    
       for this connection" occurs.
    
    
    
       Description:
    
       When opening a database for the first time, LANDesk(R) Workgroup Manager
    
       tries to decide where to look for it.  It calls NetServerGetInfo to get
    
       the servername for the default connection.  If that fails, you get this
    
       error.
    
    
    
       On an NT machine, this should return the name of the machine on which
    
       you are running.
    
    
    
       Solution:
    
       Make sure that the LANDesk Workgroup Manager services are started, and
    
       that the Windows NT* server it resides on is running NetBeui, NetBIOS,
    
       IPX/SPX Compatible Transport and TCP/IP protocols. 
    
    
    
    

    ERROR MESSAGE: "THE REMOTE COMPUTER HAS ENTERED A VIDEO MODE THAT IS NOT SUPPORTED BY THE REMOTE CONTROL AGENT...."

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       When taking remote control of a client, the error "The remote computer
    
       has entered a video mode that is not supported by the remote control
    
       agent.  The remote control agent is not currently running on the remote
    
       computer" occurs.
    
    
    
       Description:
    
       This occurs when the agent is remotely controlling a client in DOS mode
    
       when client starts Windows*.  The console has to wait until the Windows
    
       remote control program is loaded (WUSER.EXE).
    
    
    
       Solution:
    
       Agent must load Windows in order to control that client. 
    
    
    
    

    LDISCAN REPORTS "UNABLE TO ASSIGN DEVICE ID. PLEASE LOAD LDINV.NLM V2.01 OR ABOVE"

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       LDISCAN reports "Unable to assign Device ID.  Please load LDINV.NLM
    
       v2.01 or above", when doing a standalone scan on a Windows For Workgroup
    
       client.
    
    
    
       Description:
    
       You'll see this message if you used the client disk to set up a Windows
    
       For Workgroup client.  If you go to a DOS box and manually run the scan
    
       using the '/o' option to scan to an output file, you will get the above
    
       message.  You will only see the message if you are in a Windows for
    
       Workgroup DOS box and LDISCAN.CFG (the hidden device ID file) does not
    
       exist. 
    
    
    
       Solution:
    
       Create a LDISCAN.CFG on the root of the local drive and then add the
    
       line "Device ID = jkskjdfiei98889" to the file.  After the file is
    
       created, mark it as a hidden file; then the standalone scan will work
    
       fine.
    
    
    
       Note:  You can also get the message if the LANABASE=# in the
    
       PROTOCOL.INI is not equal to 0. 
    
    
    
    

    ERROR MESSAGE: "THE CLIENT HAS ENTERED AN UNSUPPORTED VIDEO MODE"

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       On Windows 95* Workstations running NetBIOS, you occasionally receives
    
       the error message, "The client has entered an unsupported video mode."  
    
    
    
       Description:
    
    
    
       On slower machines running Windows 95 and NetBIOS this may happen when
    
       the client gets busy.  This can also appear if the client is low on
    
       resources and packets are being dropped.
    
    
    
       Solution:
    
       Upgrade the workstation to a higher performance PC or accept that this
    
       message will occur on occasion due to the performance of the
    
       workstation. 
    
    
    
    

    LDISCAN.EXE REPORTS THE ERROR; "NETBIOS DID NOT RESPOND ON LANA NUMBER 0. ERROR: 23H" OR "LDISCAN COULD NOT FIND SERVER PLEASE LOAD LDINV.NLM 2.00

    
       OR ABOVE ON SERVER" 
    
    
    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       LDISCAN.EXE reports the error;  "NetBIOS did not respond on lana number
    
       0.  Error: 23h" 
    
    
    
       or   
    
    
    
       "LDISCAN could not find server please load LDINV.NLM 2.00 or above on
    
       server"  
    
    
    
       Description:
    
       Incorrect protocol specified in the PROTOCOL.INI file.
    
    
    
       Solution:
    
       To resolve both of the above problems modify the clients PROTOCOL.INI
    
       and change the LANABASE=X in the [NETBEUI] section to LANABASE=0.  This
    
       will make NETBEUI be the default protocol.  This error should only occur
    
       on Window For Workgroup and Window 95 clients.
    
    
    
    

    REMOTE CONTROL AGENT REPORTS THE ERROR: "UNABLE TO GET WORKSTATION NAME. USEDLANA: 0"

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       Remote Control Agent reports the error: "Unable to get Workstation name.
    
       Used LANA: 0"
    
    
    
       Description:
    
       The incorrect default protocol is specified in the PROTOCOL.INI file.
    
    
    
       Solution:
    
       To resolve this problems modify the clients PROTOCOL.INI and change the
    
       LANABASE=X in the [NETBEUI] section to LANABASE=0.  This will make
    
       NETBEUI be the default protocol.  This error should only occur on Window
    
       For Workgroups.
    
    
    
    

    LDISCAN DOES NOT APPEAR TO BE WORKING IN ENVIRONMENTS WITH ROUTERS

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
    
    
       LDISCAN does not appear to be working in environments with routers. 
    
       (TCP/IP is a routable protocol,  NetBEUI is not routable.)
    
    
    
       Description:
    
       LDISCAN is not working properly.
    
    
    
       Solution:
    
       1. Check to see if there is a router between the NT server and the
    
       client.  If there is check to see what protocol it is trying to use. 
    
       NetBIOS is not routable so the router should be using IP.  
    
    
    
       2. If you have TCP/IP installed then they probably need to change the
    
       LDISCAN.EXE line in either the NETBIOS.BAT or if local the NBSCAN.BAT. 
    
       To make the scan work you may need to change the "/ntn" command line
    
       parameter to a different LANA (the lana number that is assigned to
    
       TCP/IP on the client).  The default LANA number if none is specified is
    
       0.  To change the LANA number simple put a 1,2,.... on the "/ntn"
    
       parameter.  
    
    
    
       For example if I wanted to use LANA 1 the LDISCAN.EXE line would look
    
       like this;  LDISCAN /s=servername /ntn1 /v /w. 
    
    
    
    

    DATABASE WILL SAVE ONLY 5 REVISIONS OF THE CONFIGURATION FILES

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Question:
    
       If you try to save 10 revisions of the configuration files the database
    
       only saves 5. 
    
       The field allows for up to 9999 revisions to be specified.
    
    
    
       Answer:
    
       This (5) is a hard coded value.  The field should be changed, it should
    
       not allow someone to enter more than 5 revisions. 
    
    
    
    

    CONTROLLING CONSOLE'S REMOTE CONTROL SESSION COLORS ARE INCORRECT

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       The Controlling Console's remote control session colors are incorrect
    
       when remotely controlling Windows 95* Workstations that are running
    
       Animated Frame Support (Plus Pack built into Windows 95).
    
    
    
       Description:
    
       This is a known issue in the first release of the product. The Animated
    
       Frame Support is unsupported.
    
    
    
       Solution:
    
       The functions are not affected; it affects only the colors and animated
    
       cursor/mouse pointer. 
    
    
    
    

    SCANNING STANDALONE NT WORKSTATIONS: SOFTWARE SCAN INFORMATION DOES NOT GET WRITTEN TO THE OUTPUT FILE.

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       When scanning standalone NT workstations, the software scan information
    
       does not get written to the output file designated in the /O=filename
    
       file.
    
    
    
       Description:
    
       This is a known issue that should be resolved in the next release.
    
    
    
       Solution:
    
       Connect to the network and scan to the LANDesk(R) Workgroup Manager
    
       inventory server directly. If this is not possible, then the software
    
       scan information of that specific Windows NT* workstation cannot be
    
       saved. 
    
    
    
    

    NO REMOTE CONTROL CAPABILITY FOR DOS SESSIONS ON WINDOWS FOR WORKGROUPS* ANDWINDOWS 95* WORKSTATIONS

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom 1: 
    
       Unable to control a Windows for Workgroups* (WFW) v3.1x workstation at
    
       the point  that DOS is loaded (prior to loading WFW).
    
    
    
       Symptom 2: 
    
       Unable to open a DOS box on a Windows 95* workstation,  but the agent
    
       loads.
    
    
    
       Description: On both WFW and Windows 95 stations, the LANDesk(R)
    
       Workgroup agents are loaded  with the "/w" option. This option waits
    
       until the network drivers are loaded in Windows before enabling the
    
       agent. So, the agent never will be enabled under  DOS.
    
    
    
       Solution: None. There is no DOS Remote Control capability in these
    
       environments.
    
    
    
    

    UNABLE TO REMOTELY CONTROL A NETWARE* SERVER THAT IS MANAGED BY LANDESK(R) WORKGROUP MANAGER.

    
       Component: Desktop Manager
    
    
    
       Symptom:
    
       Unable to remotely control a NetWare* server that is managed by
    
       LANDesk(R) Workgroup Manager.   However, we are able to ping the server
    
       successfully.  
    
    
    
       Description:
    
       The reason for this is most likely due to the parameter "NOVIEW" loaded
    
       on the NLM load line for the "USER.NLM".
    
    
    
       Solution:
    
       Check STARTUP.NCF file to verify the parameters used. If the "NOVIEW"
    
       option is enabled verify why.   To re-enable remote control, load the
    
       "USER.NLM" without the "NOVIEW" option.
    
    
    
    

    USER PERMISSION REQUIRED TO REMOTELY CONTROL A DESKTOP DOES NOT OCCUR AFTER

    
    

    THE FIRST TIME.

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       The user permission required to remotely control a desktop does not
    
       occur after the first time the desktop is remotely controlled.
    
    
    
       Description:
    
       This is as designed and works the same as Microsoft SMS product. The
    
       reason this occurs is that once the desktop grants permission to the
    
       LANDesk(R) Workgroup Manager v1.0 Administrator, this permission
    
       continues even after the one session is terminated.
    
    
    
       Solution:
    
       The only way this attribute gets disabled is by unloading the LANDesk
    
       Workgroup Manager Console on the Windows NT* station or unloading the
    
       Workstation Agent on the controlled workstation. 
    
    
    
    

    UNABLE TO FIND INVENTORY LOGFILE "LDINV.ERR" REFERENCED IN THE DOCUMENTATION.

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       Unable to find the inventory error logfile referenced in the
    
       documentation. The documentation refers to a filename "LDINV.ERR"?
    
    
    
       Description:
    
       The error log filename was changed after the documentation was
    
       completed.
    
    
    
       Solution:
    
       The filename of the LANDesk(R) Workgroup Manager inventory database
    
       error logfile is "\ldwm\database\LDINV32.ERR". 
    
    
    
    

    LDISCAN.EXE IS NOT REPORTING NEW SOFTWARE ADDED TO THE LDAPPL.INI.

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       LDISCAN.EXE is not reporting new software added to the LDAPPL.INI.
    
    
    
       Description:
    
       This is due to the requirement in the first release of the product that
    
       this list be in alphabetic order.
    
    
    
       Solution:
    
       LDISCAN.EXE only finds the software listed in the LDAPPL.INI that is in
    
       alphabetic order.  When a new software item is added it is put right at
    
       the top of the [APPLICATIONS] section of the LDAPPL.INI.  A simple work
    
       around for this problem is to have the customer move these newly added
    
       software items down into the [APPLICATIONS] into alphabetic order. 
    
    
    
    

    UNABLE TO ADD STANDALONE DATA TO SERVER INVENTORY DATABASE.

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       Unable to add standalone data to server inventory database.
    
    
    
       Description:
    
       The '/t' for the DOS, WIN3.X, and WIN95 LDISCAN is not currently
    
       working.
    
    
    
       Solution:
    
       If you create a output scan file using LDISCAN.EXE with the "/o" option
    
       to add the information to the Inventroy Server Database you need to copy
    
       the file to the NT console and then use LDISCNNT with the '/t' option to
    
       read it into the inventory database. 
    
    
    
    

    LDISCAN UNABLE TO OPEN THE CFG_YES.LOG OR THE CFG_NO.LOG FILES

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       LDISCAN unable to open the CFG_YES.LOG or the CFG_NO.LOG files.
    
    
    
       Description:
    
       This problem can occur after setting up a Novell NetWare* server to scan
    
       and configure clients.  The error is the result of not having sufficient
    
       rights assigned to the LANDesk(R) Workgroup Manager group that was
    
       created.
    
    
    
       Solution:
    
       Ensure the group has read and file scan in the directory where the
    
       client files where copied and read, file scan, create, modify, create,
    
       and erase rights in the LDLOG directory. 
    
    
    
    

    IPX CLIENTS AND/OR STANDALONE CLIENT WORKSTATIONS ARE NOT REPORTING THE NEW SOFTWARE ADDED TO LDAPPL.INI USING SOFTWARE LIST

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       IPX clients and/or standalone client workstations are not reporting the
    
       new software added to LDAPPL.INI using Software List.
    
    
    
       Description:
    
       The LDAPPL.INI that is modified using Software List exists in the
    
       \LDWM\LDLOGON directory but is not replicated to the NetWare* servers or
    
       standalone clients automatically.
    
    
    
       Solution:
    
       The LDAPPL.INI that is modified using Software List exists in the
    
       \LDWM\LDLOGON directory.
    
    
    
       All Microsoft clients that login to the NT server will see the new
    
       modified LDAPPL.INI, but the clients that login to the NOVELL Server
    
       will not see the new LDAPPL.INI until it is copied to the client
    
       directory on the NOVELL Server.  Also if the client was configured using
    
       the client disks with the /NOLOGON option then the LDAPPL.INI will need
    
    
    
       to be copied to the clients local LDCLIENT directory. 
    
    
    
    

    HOW TO DETERMINE THE LAST COMPLETED INVENTORY SCAN DATE FOR ANY NODE

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Question:
    
       How is it possible to determine the last completed inventory scan date
    
       for any node?
    
    
    
       Answer:
    
       Information reflected in servers database is not updated.
    
    
    
       The simple method is to select the DOS, Windows* or Windows NT*
    
       workstation in the network tree and choose Diagnostics - Inventory
    
       Summary. At the bottom of this display in the right hand corner is the
    
       last Scan Date.
    
    
    
    

    CONFIGURATION LIMIT FOR FILE REVISION SAVES

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Question:
    
       What is the configuration limit? It is not stated in the documentation.
    
       It appears that it's not saving specified number of reiterations.
    
    
    
       Answer:
    
       The hard-coded limit is a maximum of 5 file revision saves for any one
    
       file. 
    
    
    
    

    NAMING STANDALONE COMPUTERS FOR INVENTORY PURPOSES

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Question:
    
       When setting up several standalone workstations, what is the maximum
    
       number of characters and types of characters that can be used in
    
       creating the unique name for the computers for inventory purposes?
    
    
    
       Answer:
    
       Only Alpha/Numeric characters are supported with a maximum of 15
    
       characters in length. 
    
    
    
    

    RUNNING BOTH LANDESK(R) WORKGROUP MANAGER AND LANDESK MANAGEMENT SUITE ON THENETWORK - COMMON POINT OF INVENTORY DATA COLLECTION

    
       Component: Desktop Manager
    
    
    
       Question:
    
       We run both LANDesk(R) Workgroup Manager and LANDesk Management Suite on
    
       the network but would like a single point of inventory data collection.
    
       Can the LANDesk Workgroup Manager Inventory be sent to the LANDesk
    
       Management Suite inventory server? We need a common inventory database
    
       location.
    
    
    
       Answer:
    
    
    
       This can be accomplished if the LANDesk Workgroup Manager nodes are
    
       running NetWare* IPX protocol.  Do this by:
    
    
    
       1. Direct the LDISCAN of these nodes to the LANDesk Management Suite's
    
       Inventory server. Example:
    
    
    
       LDISCAN /S=LDMS_Inventory_Servername /F /V
    
    
    
       2. Modify the LDAPPL.INI file on the LANDesk Workgroup Manager NT server
    
       to reflect that the information will be stored on a NetWare* server
    
       instead of the Windows NT* server. To do this edit the LDAPPL.INI file
    
       (residing in the \lLDWM\LDLOGON directory) by replacing:
    
    
    
       DefaultNetwork=Microsoft
    
    
    
       with
    
    
    
       DefaultNetwork=Novell
    
    
    
    

    WHEN STARTING WINDOWS* FROM A DOS CLIENT, WINDOWS COMES UP BUT NO TEXT FIELDS

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       When remotely controlling a DOS station and starting Windows* v3.1x,
    
       Windows comes up OK but there are no text fields (ie: there are icons,
    
       but there isn't any text under the icons).
    
    
    
       Description:
    
       This occurs randomly when starting Windows from a DOS client that is
    
       remotely controlled. 
    
    
    
       Solution:
    
       Refresh the remote control screen and/or exit Windows within the remote
    
       control box and restart. This should re-paint the text in the Windows
    
       display. 
    
    
    
    

    REMOTE CONTROL SESSION TERMINATES WHEN EXITING A NETBIOS WINDOWS FOR WORKGROUPS AND WINDOWS 95*

    
       Product: LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       Remote Control session terminates when exiting a NetBIOS Windows For
    
       WorkGroups or exiting Windows 95* in to a DOS Command Prompt only.
    
    
    
       Description:
    
       This is done by design.  The remote control session terminates because
    
       the network drivers, by design, are unloaded in both the above
    
       situations. 
    
    
    
       Solution:
    
       None.  This is as designed by Windows for Workgroups and Windows 95
    
       products. 
    
    
    
    

    UNABLE TO PRINT OUT THE ATTACHED NOTES SAVED IN THE INVENTORY DATABASE

    
       Product:  LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       Unable to print out the attached notes saved in the inventory database.
    
    
    
       Solution:
    
       This is as designed in the first release of the product.
    
    
    
    

    QUICK METHODS TO VERIFY IF INVENTORY CHANGES WERE MADE

    
       Product:  LANDesk(R) Workgroup Manager, Component: Desktop Manager
    
    
    
       Symptom:
    
       Is there a quick method to verify that inventory changes were made, and
    
       the status of whether they were successful or not?
    
    
    
       Solution:
    
       Inventory changes are written to two locations for reference.  They are
    
       :
    
         - The Windows NT* Event Viewer Application Log.
    
         - Tthe CHANGES.LOG file that can be viewed from the LANDesk(R)
    
       Workgroup Manager Network
    
           Tree window under the View pulldown option.
    
    

    Trademark information