[Intel Navigation Header]

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

    Contents:

    • CONTENTS
    • "USER USERNAME IS NOT ATTACHED TO COREFILESERVERNAME OR HAS INSUFFICIENT RIGHTS TO RUN MANAGEMENT CONSOLE 2.0 ON COREFILESERVERNAME"
    • LANDESK(R) MANAGEMENT CONSOLE HAS DETECTED THAT THE CURRENT DOMAIN CONTAINS MORE NODES THAN THE CURRENT DOMAIN IS CONFIGURED TO MANAGE
    • "DATABASE ERROR: UNABLE TO LOAD OBJECT TABLES"
    • APPLICATION SERVERS NOT RUNNING OR CORE NLMS NOT LOADED OR UNABLE TO LOAD MANAGEMENT CONSOLE
    • NO TOOL PALETTE ICONS APPEAR IN THE CONTROL PANEL
    • SOCKET TABLE IS FULL OR FAILED TO OPEN SOCKET
    • UNABLE TO OPEN UNICODE TABLES
    • CANNOT EXPAND DOMAIN IN NETWARE* 4.X ENVIRONMENT
    • BTRIEVE* ISSUES
    
    

    CONTENTS

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

    "USER USERNAME IS NOT ATTACHED TO COREFILESERVERNAME OR HAS INSUFFICIENT RIGHTS TO RUN MANAGEMENT CONSOLE 2.0 ON COREFILESERVERNAME"

    
       Symptom:
    
       Error message:User USERNAME is not attached to COREFILESERVERNAME or has
    
       insufficient rights to run Management Console 2.0 on COREFILESERVERNAME.
    
    
    
       Description A:
    
       Management Console v2.0 reports this error when an administrator
    
       launches the management console from a core file server while logged in
    
       as a user with insufficient rights, or uses File|Open Domain to try and
    
       view another core file server with insufficient rights.
    
    
    
       Description B:
    
       The [CoreServices] section of the WIN.INI does not point to the current
    
       core LANDesk(R) Management Suite file server.
    
    
    
       Description C:
    
       The LDINIT>INI file is corrupt ([LANDesk section ]).
    
    
    
       Solution A:
    
       Grant the login ID the following minimum rights:
    
    
    
         -  All rights except A and S (Access and Supervisor) to the
    
            administrator's network LANDesk directory (SYS:\LANDESK is the
    
            default). Members of LANDESKADMINGROUP on the core file server have
    
            these rights.
    
    
    
         -  R and F (Read and File Scan) rights to the shared LANDesk directory
    
            (SYS:\LOGIN\LANDESK is the default)
    
    
    
            -    R and F (Read and File Scan) rights to the SYS:SYSTEM
    
       directory.
    
    
    
       Solution B:
    
       Make sure the [CoreServices] section of the WIN.INI points to the
    
       current core LANDesk Management Suite file server. Modify the
    
       ClientDomain=COREFILESERVERNAME line to accurately reference a core file
    
       server running LDDB.NLM.
    
    
    
       Description C:
    
       Re-expand the LDINIT.IN_ file off of th eLANDesk Management Suite
    
       CD-ROM, or restore off of a previous backup tape. 
    
    
    
    

    LANDESK(R) MANAGEMENT CONSOLE HAS DETECTED THAT THE CURRENT DOMAIN CONTAINS MORE NODES THAN THE CURRENT DOMAIN IS CONFIGURED TO MANAGE

    
       Symptom:
    
    
    
       The message "insufficient  number of node licenses" appears every 10
    
       minutes or so.
    
    
    
       Description:
    
       Each server and PC in a domain counts as a licensed node. As you expand
    
       your domain, you need to make sure that you include only the containers
    
       and associated devices for servers that yoyu really want to manage. If
    
       you have more PCs and servers in your domain that you have licenses, you
    
       frequently will get a message telling you that there is a discrepancy in
    
       the license count. Since the count comes from the database instead of
    
       from a real-time count of objects, it is likely that the number of
    
       managed nodes will not correspond exactly with the number of nodes that
    
       are currently logged in.
    
    
    
       Solution:
    
       To stop the error message, you need to either add more licenses (by
    
       running SETUP.EXE from the SYS:LANDESK directory and choosing Manage
    
       Licenses) or delete inactive nodes from the database on the Management
    
       Console.
    
    
    
    

    "DATABASE ERROR: UNABLE TO LOAD OBJECT TABLES"

    
       If this message appears while loading the management console, one of
    
       three conditions may exist:
    
    
    
         *  The administrators workstation is not running IPXODI drivers (see
    
            NOV_TODO.TXT on the root directory of the CD or in the
    
            administrator's LANDesk(R) directory, SYS:LANDESK by default).
    
    
    
         *  The file server has below 40 percent cache buffers free.
    
    
    
         *  The LANDesk(R) Management Suite core database may have become
    
            corrupt due to insufficient Btrieve* environment space.
    
    
    
       To rebuild the core database, see Database Corruption in document 5617. 
    
       To make sure Btrieve is not starved for environment space, see the
    
       Btrieve issues discussed on the pink card included in the shipping
    
       release box.
    
    
    
       Note: More than any other product, the remote workstation control
    
       features push the relationship between NetWare* and Windows* and require
    
       a solid set of drivers, as does the Management Console in v2.0 in order
    
       to communicate with the file server (connection manager).
    
    
    
    

    APPLICATION SERVERS NOT RUNNING OR CORE NLMS NOT LOADED OR UNABLE TO LOAD MANAGEMENT CONSOLE

    
       Symptom:
    
       Application servers not running or Core NLMs not loaded or Unable to
    
       load Management ConsoleMake sure that the LANDesk(R) NLMs are loaded on
    
       the core server.
    
    
    
       Solution 1:
    
       Make sure that the LANDesk NLMs are loaded on the core server.
    
    
    
       Solution 2:
    
    
    
       Check the CoreServices section of the WIN.INI in the Windows* directory
    
       and the CONMAN.INI in the SYS:SYSTEM directory to make sure that it
    
       points to the core LANDesk server.
    
            ClientDomain=COREFILESERVERNAME
    
    
    
       Solution 3:
    
       In Netware* 4.x environments, the user may be authenticating to a server
    
       that is not running LANDesk. In NWADMIN | user | details | environment,
    
       there is a preferred server option. configure this to point to the
    
       LANDesk server where authentication should occur.
    
    
    
       Solution 4:
    
       The Network drive used during the initial installation of LANDesk
    
       Management Suite v2.0 is written into serveral .INI files. When drive
    
       letters change, the network administrator may have to modify the .INI
    
       files as listed below.
    
    
    
       For example: If you installed from the CD to the server volume VOL1
    
       using drive N: every workstation that is to be a management console must
    
       have drive N: mapped to VOL1. If another administrator workstation uses
    
       another drive letter, make the appropriate changes to the following .INI
    
       files.
    
    
    
       WIN.INI        change path for loading ALCONV.EXE.
    
       LANDESK.INI change common=
    
            change FPcommon=
    
            change netld=
    
            change FPnetld=
    
            don't change UNCnetld=
    
            don't change UNCommon=
    
            check locld=
    
            check FPlocld=
    
            change REPORT=
    
            change CSV=
    
    
    
       LDMWORKS.INI change Queue Monitor=
    
            change Printer Manager
    
            change ReportTool=
    
            change BasicScript Editor=
    
            change PRCM=
    
            change Virus Scan=
    
    
    
       ODBCINST.INI
    
             check Driver=
    
            check Setup=
    
            Probably no changes are necessary)
    
    
    
       ODBC.INI
    
            check Driver= lines
    
            change DataDirectory=
    
    
    
       LDPM.INI
    
            check DIR=
    
    
    
       Remember to modify the Program Item Properties for the LANDesk
    
       Management Suite icons in Windows Program Manager. It may be necessary
    
    
    
       to rebuild the database as discussed in document 5617.
    
    
    
    

    NO TOOL PALETTE ICONS APPEAR IN THE CONTROL PANEL

    
       Symptom:
    
       No tool palette icons appear in the control panel.
    
    
    
       Description:
    
       This is usually due to running Windows* with insufficient memory, or a
    
       corrup .LDU file, or installing LANDesk(R) with insufficient memory at
    
       the installation work station.
    
    
    
       Solution A:
    
       Exit Windows, and re-enter, without loading any applications. Make usre
    
       that you have at least 540k conventional memory free before starting
    
       Windows, and 70% Windows resources free before launching LANDesk.
    
    
    
       Solution B:
    
       Rename the .LDU file (usually called LOGINNAME.LDU) in SYS:LANDESK, then
    
       copy the DEFAULT.LDU to the LOGINNAME.LDU.
    
    
    
       Solution C:
    
       From the CD-ROM, re-expand DEFAULT.LD_ to SYS:LANDESK\DEFAULT.LDU,
    
       MCONSOLE.DL_ to SYS:LANDESK\MCONSOLE.DLL and expand LDCP.EX_ to
    
       SYS:LANDESK\LDCP.EXE.
    
    
    
       Solution D:
    
       Delete "user".LDU and re-run SETUP.EXE from the Core servers
    
       SYS:\LANDESK directory.
    
    
    
       Solution E:
    
       If none of the previous solutions work, you will need to reinstall
    
       LANDesk Management Suite.
    
    
    
            1. Close the control panel
    
            2. Delete the LANDesk program group.
    
            3. Exit to DOS.
    
            4. Delete the [CoreServices] and [Traffic] sections from the
    
       WIN.INI.
    
            5. Delete the LANDESK.INI in the Windows directory.
    
            6. Have 580k conventional memory free if possible (install only).
    
            7. Remove all unneccessary TSRs and reboot if needed.
    
            8. EMM386.EXE with NOEMS is the recommended memory manager.
    
            9. Restart Windows.
    
            10. Close all applications listed in the Task List (press Ctrl-Esc
    
       to view task list).
    
            11. From File | Run, run SETUP.EXE from the CD-ROM.
    
    
    
    

    SOCKET TABLE IS FULL OR FAILED TO OPEN SOCKET

    
       Symptom:
    
       Socket Table is Full or Failed to Open Socket error message.
    
    
    
       Description:
    
       Not enough IPX sockets are available on this workstation to perform the
    
       task specified.
    
    
    
       Solution:
    
       In the NET.CFG file, add the foloowing tow lines. If these already
    
       exist, then increase their values to match the example.
    
            IPX SOCKETS=50
    
            SPX CONNECTIONS=40
    
    
    
    

    UNABLE TO OPEN UNICODE TABLES

    
       Symptom:
    
       Unable to open unicode tables.
    
    
    
       Solution:
    
       * Make sure you have a search drive mapped to the PUBLIC\NLS directory
    
       on the server.
    
       * Or, copy the PUBLIC\NLS files, directories, and all subdirectories
    
       into the PUBLIC directory.
    
       * Or, copy the PUBLIC\NLS files, directories, and all subdirectories to
    
       the WINDOWS\NLS and NWCLIENT\NLS.
    
    
    
    

    CANNOT EXPAND DOMAIN IN NETWARE* 4.X ENVIRONMENT

    
       Symptom 1:
    
       Cannot expand domain in NetWare* 4.x environment with a country in the
    
       NDS. When the Management Console is opened and Manage-Domain-Assign
    
       Members to Domain is selected, none of the OUs or servers appear.
    
    
    
       Symptom 2:
    
       When the Management Console is opened and Manage-Domain-Assign meemeber
    
       to domain is selected, the tree does not appear in the available
    
       elements. Only the servers appear in bindery emulation.
    
    
    
       Solution 1:
    
       Not supported in LANDesk(R) Management Suite versions 2.01a or
    
       below.Upgrade to current release.
    
    
    
       Solution 2:
    
       Make sure that you do not have a tree, O, OU, or server with the same
    
       name. Also make sure that you install to the tree first, and then choose
    
       a management server to get full NDS compatibility. If you choose a
    
       server first, LANDesk will install in bindery emulation. To get full NDS
    
       compatibility, uninstall and re-install through the tree, then choose a
    
       management server.
    
    
    
    

    BTRIEVE* ISSUES

    
       It is critical that Btrieve be configured with sufficient environment
    
       space.  One LANDesk Management Suite administrator workstation will not
    
       require more than the default Btrieve values.  If any other file server
    
       applications use Btrieve or you plan on running multiple administrator
    
       workstations, software distributions to a large number of users, etc.,
    
       you MUST load Btrieve with more environment space.
    
    
    
       To avoid starving critical NetWare* and Btrieve* environment space,
    
       refer to the following table of Btrieve defaults and the values required
    
       for LANDesk Management Suite.  If you know the environment needs of your
    
       other applications, use BSETUP.NLM to add them to these requirements. 
    
    
    
       If you are unsure, you should double or triple the Btrieve defaults. 
    
       Doubling only consumes approximately 100 to 250 KB of additional file
    
       server RAM.
    
    
    
       Parameter                    Btrieve Default    Required    Recommended
    
    
    
       Number of Open Files         20                 13 (25 in v2120
    
    
    
       Number of Handles            60                 35*         210
    
       * Increase if Btrieve Error 87 occurs
    
    
    
       Number of Locks              20                 3           120
    
    
    
       Number of Transacions        15                 5           45
    
    
    
       Largest Compressed Record    0                  N/A         N/A
    
       Size
    
    
    
       Largest Record Size          8192               8192        8192
    
    
    
       Largest Page Size            4096               4096        4096
    
    
    
       Number of Remote Sessions    15                 15**        30
    
       ** Increase if Btrieve Error 96 occurs
    
    
    
       Cache Allocation             256                256         256***
    
       ***in Netware 4.x environments, increase this value to
    
       ...........................................................768
    
    
    
       Perform Index Balancing      No                 N/A         N/A
    
    
    
       Logging of Select Files      No                 N/A         N/A
    
    
    
       Create Btrieve Files in Pre vNo                 No          No
    
    
    
       Create Files as TransactionalNo                 N/A         N/A
    
    
    
       Config BSTART.NCF to load BRONo                 N/A         N/A
    
    
    
       During heavy file server processes, such as Cheyenne ArcServe, it's
    
       critical that NetWare and Btrieve have enough environment space.  We
    
       have found that the above Recommended Btrieve values for large servers
    
       consume little in file server RAM, but provide greater security when
    
       running LANDesk Management Suite in conjunction with other products such
    
       as ArcServe.  If Btrieve loads from an application specific *.NCF, make
    
       sure it reflects the recommended environment space listed above.  If you
    
       have questions regarding the amount of environment space needed by other
    
       products you use, contact their technical support line.  For more
    
       information on how LANDesk Management Suite uses Btrieve, see
    
       FORMATS.DOC in the BTRIEVE directory of your LANDesk Management Suite
    
       CD-ROM.
    
    
    
       Cheyenne ArcServe v4.x does NOT use Btrieve, BUT its intensive file
    
       operations still negatively impact a file server with the Btrieve
    
       default settings.  We recommend that you double or triple the Btrieve
    
       environment settings.  ArcServe v5.x (5.01F is the current version) 
    
    
    
       uses Btrieve.  Tests with Btrieve v5.01E in our lab were successful with
    
       the Btrieve default settings.  All versions of ArcServe are supported at
    
       800-243-9832.  Cheyenne OEMs ArcServe to other companies under several
    
       different names (for example ProServe).
    
    
    
       To refresh the corrupted database, see the section on Rebuild the
    
       database.
    
    
    
       If Distribute was running, then it would mean one extra session and so
    
       Number of sessions would increase to 5 and Number of handles would
    
       increase to 20.
    
    
    
       BTR61.EXE is on the LANDesk Management Suite v2.0 CD and contains the
    
       latest Btrieve files necessary.
    
    

    Trademark information