![[Intel Navigation Header]](/CONTENT/PIX/HEADER.GIF)
LANDesk(R) Management Suite v2.x: Desktop Manager Usage Tips
Contents:
CONTENTS
This document discusses issues commonly encountered with Desktop
Manager. It supplements the files in LANDesk(R) Management Suite's
Readme Viewer.
"SERIALIZATION OBJECT NOT FOUND ON SERVER SERVERNAME" OR "ERROR: SERIALIZATION OBJECT NOT FOUND IN CONTEXT OU=OUNAME.O=ONAME." OR "UNABLE TO COMPLETE
CHECK FOR SERIALIZATION"
LANDesk(R) Management Suite v2.0x
Symptom:
"Serialization Object not found on Server SERVERNAME" or
"ERROR: serialization object not found in context OU=OUNAME.O=ONAME" or
"Unable to complete check for serialization".
Description:
This error occurs when a user tries to run USERTSR.EXE while logged in
to a file server or OU that is not part of the LANDesk Management
Domain. (Being attached to a server that is part of the domain is not
enough.)
Solution:
For Netware* v3.11/v3.12, check the following requirements for proper
serialization:
* Add a "Preferred Server = SERVERNAME" line to the workstation
NET.CFG or use the "/PS=SERVERNAME" command-line option when the
workstation loads NETX or VLMs
* Login to a file server that is part of the LANDesk Management
Suite domain.
* Include the file server that you log in to as part of the LANDesk
management domain (using the management console)
* Create a new management server by installing LANDesk Management
Suite v2.0x on the file server you log in to
For NetWare v4.02/4.1, check the following requirements for proper
serialization with Netware Directory Services (NDS):
* Expand the LANDesk Management Domain to the container which you are
a member of (using the management console under
Manage|Domain|Assign Members to Domain).
Note: That adding an O or OU to the Management Domain will not
automatically include subcontainers unless you activate that option
in the lower left corner of the Define Domain screen.
* A leading dot in the context parameter of the NET.CFG could also
account for a serialization error; removing the leading dot from
the NET.CFG allows serialization to function properly.
* in the NET.CFG make sure the Netware Protocol statement has NDS
first,
Example: "Netware Protocol = NDS BIND", not BIND NDS
* Place a "Preferred tree = TREENAME" in NET.CFG, do not use the
preferred server option.
* IN NWADMIN.EXE highlight the User, choose Details/Environment;
there is a preferred server setting, change this to point to the
LANDesk server where authentication should occur.
"ERROR: UNABLE TO GET PRIMARY SERVER INFORMATION"
LANDesk(R) Management Suite v2.0x
Symptom:
USERTSR will not load if the network shell is NETX (any version) and the
user has not logged into a managed server. However, USERTSR will load
if the network shell is VLM and the user has not logged into a managed
server.
Description:
In previous releases of LANDesk Manager USER.COM loaded before login
using NETX.EXE or VLM.EXE. However, in the process of adding NDS support
temporarily removed this functionality (for workstations running
USERTSR.EXE and NETX.EXE).
Solution:
Upgrade to LANDesk Management Suite v2.0x. If you haven't received this
upgrade you should get electronic document 9985 from Intel's online
services.
"ERROR LANS011: INVALID TEMPORARY PATH" OR UNABLE TO LOAD POPUPTSR /T=SELTEMPBEFORE LOGIN IS RUN
LANDesk(R) Management Suite v2.0x
Symptom:
Error message:"Error LANS011: Invalid temporary path" or Unable to load
POPUPTSR /t=SELTEMP before LOGIN is run
Description:
POPUPTSR requires sufficient rights to store a temporary file during DOS
workstation processes like chat, file transfer, and software
distribution.
When POPUPTSR.EXE tries to load before a workstation is logged into a
file server, it checks to see if the temporary file can be stored in a
default location (SYS:\LOGIN\LANDESK unless the
/t=SYS:\LOGIN\LANDESK\SELTEMP switch was used). Because the users
aren't logged in yet, the check for write privileges fails, and POPUPTSR
checks the DOS environment for a TEMP=DIRECTORYNAME setting. If one
does not exist, POPUPTSR cannot load and this message appears.
Solution:
Create a DOS setting TEMP=C:\ (or another existing directory where the
workstation can write files) or load POPUPTSR with the /t=DIRECTORYNAME
option. For example, POPUPTSR /t=C:\ or POPUPTSR /t=C:\TEMP.
WKSTACFG.EXE DOES NOT PROPERLY CONFIGURE A WORKSTATION
Symptom:
Changes are made to the WIN.INI (for example, METERWIN.EXE and WUSER.EXE
are added to the load= line), but WKSTACFG.EXE doesn't place WUSER.EXE,
METERWIN.EXE, etc. in WINDOWS\SYSTEM or modify SYSTEM.INI.
Description:
The WKSTACFG.EXE supplied with LANDesk(R) Management Suite is the first
to require Windows to be in the search path in order to make the proper
Windows* modifications. This allows network administrators to keep
backup copies of Windows on their hard drives without having
WKSTACFG.EXE modify them.
Solution:
Place the WINDOWS directory in the search path.
HOW TO INVENTORY OS/2 WORKSTATIONS--UNABLE TO FIND V2.0 DOCUMENTATION ON LDISCAN2.EXE
Since the OS/2 inventory scanner, LDISCAN2.EXE, operates the same as
LDISCAN.EXE, the LANDesk(R) Management Suite v2.0 documentation forgot
to place a simple "How to" on how to inventory scan an OS/2
workstation's hardware and software. Simply run LDISCAN2.EXE with the
same options in the system login script or those documented on page 110
in the LANDesk Management Suite Tools Guide.
WORKSTATION HANGS
LANDesk(R) Management Suite v2.0 only
Symptom:
Workstation hangs in DOS or Windows*.
Description1:
Calls to Interrupt 21h via the NetWare* shell hang a PC running the
shipping release version of USERTSR.EXE. The majority of calls to Int
21h function properly, but programs like BINDVIEW v3.5, pcANYWHERE v2.0,
RPRINTER, and NPRINTER may cause conflicts while making calls via the
NetWare shell. The Novos Terminal Emulation interrupt redirector for
mainframes has also been reported to cause workstation hangs.
Description2:
Versions of NetManage Chameleon prior to v4.5 (released April 1995)
contain NetWare/Windows incompatibilities that hang PCs running LANDesk
Management Suite or LANDesk Manager. WUSER.EXE and IDISPLAY.DLL bring
out the NetWare/Windows conflict with NetManage Chameleon.
Solution1:
Upgrade to LANDesk Management Suite v2.01x which resolves this problem.
Solution2:
Upgrade to NetManage Chameleon v4.5 or later. Contact NetManage at
408-973-7171 to get their current release.
TIME STAMP OFF BY 1 HOUR OR MORE
Symptom:
Displayed time stamps in LANDesk(R) Management Suite v2.0x are off by an
increment of 1 hour or more.
Description:
The time zone setting at the file server and/or workstation probably
needs modification. NetWare's SYSTIME.EXE fixes some time discrepancies
between the file server and workstation, but not all. Novell's CLIB
v3.12h reportedly reports time better than previous releases (not an
hour off).
Solution:
To check the file server time zone setting, run SET TIME ZONE at the
file server console. Follow the instructions in NetWare* System
Administration under SET TIMEZONE. For example, a file server in Utah
would use SET TIMEZONE=MST7 (during daylight savings, MST7MDT would be
appropriate; the default is EST5EDT, but NetWare seems to ignore the
daylight savings settings regardless, so many customers end up
specifying EST5 or MST7 when they are really CST6, for example). To
automatically set this parameter when the file server comes up, place
this SET parameter in STARTUP.NCF or at the beginning of AUTOEXEC.NCF.
CLIB.NLM must be loaded after this parameter, so setting it manually may
require you to unload several NLMs. NetWare does not automatically
adjust the time zone setting when daylight savings changes every six
months.
To set the time zone at a workstation, use SET TZ with similar syntax.
For example, a LANDesk administrator's workstation in California would
place SET TZ=PST8 in AUTOEXEC.BAT.
ACCESS IS ALLOWED WITHOUT PERMISSION
Symptom:
With NetWare* 4.x and the USERTSR /permission switch in use, access is
allowed without permission.
Description:
The permission feature will not work unless there is a default security
template for the container/server that the user is a member of/attached
to, even if you use the /permission switch.
Solution:
To insure permission will be required, run Desktop Manager, select
Options, select Security, and create a default security template for
each managed server in the tree and for each managed container in the
tree.
"SOCKET TABLE FULL"
LANDesk(R) Management Suite v 2.x
Symptom:
Socket table full
Description
Not enough IPX sockets available on this workstation to perform task
specified.
Solution:
1. Check ipx and spx in NET.CFG.
2. Set :
IPX Sockets=40
SPX Connections=40
"CANNOT LOAD ECB FINDER ROUTINE"
Document # 5611.99
Symptom:
Error : "Cannot Load ECB Finder Routine" when loading POPUPTSR.EXE.
Description:
This occurs when you update your drivers to VLM or newer NETX.
Solution:
Load POPUPTSR.EXE using the NOECB option:
POPUPTSR /NOECB
CANNOT REMOTE CONTROL USERS IN DIFFERENT CONTAINERS IN A NETWARE* 4.1 ENVIRONMENT
LANDesk(R) Management Suite v2.01x
Symptom:
Cannot remote control users in different containers in a NetWare* 4.1
environment without first connecting to that specific server as was
required in the NetWare 3.X environment.
Description:
This is the way it was designed.
Solution:
Attach to the server you wish to control first prior to attempting to
remote control that server or one of the nodes in that container.
Trademark information