![[Intel Navigation Header]](/CONTENT/PIX/HEADER.GIF)
LANDesk(R) Workgroup Manager Tips: Installation
Contents:
WHAT PROTOCOL SUPPORT IS REQUIRED ON THE WINDOWS NT* SERVERS FOR LDWM?
Product: LANDesk(R) Workgroup Manager, Component: Install
Question: What protocol support is required on the Windows NT* servers
on which the LANDesk(R) Workgroup Manager Product is installed?
Answer:
* NetBEUI Protocol & NetBIOSEUI Protocol & NetBIOS Interface
(Workgroup Manger requirement)
* NWLINK "IPX/SPX" Compatible Transport and NWLink NetBIOS (BTRIEVE
requirement)
* TCP/IP Protocol (Server Monitor requirement)
ERROR "USERTSR(IPX).EXE IS NOT LOADED: REMOTE CONTROL AGENT WILL NOT LOAD."
Product: LANDesk(R) Workgroup Manager, Component: Install
Symptom:
Windows for Workgroup workstation is configured for NetBIOS and receives
message "USERTSR(IPX).EXE is not loaded : Remote Control agent will not
load.".
Description:
PROTOCOL.INI file is pointing to LANABASE=1 in the NETBEUI section.
Therefore the LANDesk(R) Workgroup Manager agent thinks the USERTSR
should be of the IPX vintage.
Solution:
Edit the PROTOCOL.INI file and add the line "LANABASE=0" to the
[NETBEUI] section.
ERROR "UNABLE TO FIND %SAUTOEXEC.BAT. PLEASE ADD %SUSERTSR /W (OR USERIPX /W) TO YOUR AUTOEXEC.BAT"
Product: LANDesk(R) Workgroup Manager, Component: Install
Symptom:
Receive error "Unable to find %sAUTOEXEC.BAT. Please add %sUSERTSR /W
(or USERIPX /W) to your AUTOEXEC.BAT".
Description:
This will occur if no AUTOEXEC.BAT exists or it is a diskless
workstation.
Solution:
Download patch "NTWCFG.EXE" from the LANDesk(R) Workgroup Manager
Current area of the online services.
USERTSR DOES NOT LOAD BEFORE WINDOWS* EXECUTES AFTER RUNNING WKSTACFG.EXE SETUP PROGRAM
Product: LANDesk(R) Workgroup Manager, Component: Install
Symptom:
USERTSR does not load before Windows* executes after already running
WKSTACFG.EXE setup program.
Description:
WKSTACFG.EXE does not scan for WIN command in AUTOEXEC.BAT File.
Therefore the line entries to load USERTSR are appended to the end of
the AUTOEXEC.BAT file.
Solution:
Download the patch "NTWCFG.EXE" from the LANDesk Workgroup Manager
Current area on the online services. For stations that have already
been configured, the workaround is to manually edit the AUTOEXEC.BAT
file moving the WIN load line after the load of USERTSR.EXE.
AFTER DELETING THE WORKSTATION FROM THE CFG_YES.LOG FILE, WKSTACFG.EXE AND NTSTACFG.EXE WILL NOT RECONFIGURE THE WORKSTATION.
Product: LANDesk(R) Workgroup Manager, Component: Install
Symptom:
A workstation needs to be reconfigured with "WKSTACFG.EXE" or
"NTSTACFG.EXE", but after deleting the workstation from the
"CFG_YES.LOG" file, neither program will reconfigure the workstation.
Description:
The cause of this is that these configuration utilities check both the
"CFG_YES.LOG" and the "CFG_NO.LOG" files for the existence of the
workstation.
Solution:
To make sure the workstation runs setup again, delete the computer
Device ID in both files (CFG_YES.LOG and CFG_NO.LOG).
WHEN INSTALLING LANDESK(R) WORKGROUP MANAGER THE SNMP FORWARDING CAPABILITY IS NOT ENABLED.
Component: Install
Symptom:
When installing LANDesk(R) Workgroup Manager the SNMP forwarding
capability is not enabled.
Description:
This is because the install program did not find that the SNMP service
was enabled/Installed on the Microsoft NT Server.
Solution:
Add the SNMP support to the LANDesk Workgroup Manager Windows NT*
server. To do this, load the Windows NT Server CD/ROM. Go into Control
Panel; Network; Add Software and select "TCP/IP Protocol and related
components". When the screen appears, select the SNMP service and add
it.
Note: Prior to performing this the administrator needs to know the
station IP address and the router IP address to complete the SNMP
installation on the Windows NT station.
SMC8000 NETWORK INTERFACE CARD CAUSES LOCK UP
Product: LANDesk(R) Workgroup Manager, Component: Install
Symptom:
SMC8000 Network Interface Card causes the client to lock up randomly
when trying to get diagnostic information or using tools (remote
control, etc..).
Description:
This only happens if the SMC8000 is setup for I/O mapped and not memory
mapped.
Solution:
To fix the problem run the EZSETUP utility that comes with the SMC8000
card and change the settings from I/O mapped to memory mapped.
WKSTACFG.EXE HANGS ON A WINDOWS 95* WORKSTATION
Product: LANDesk(R) Workgroup Manager, Component: Install
Symptom:
WKSTACFG.EXE hangs on a Windows 95* workstation.
Description:
WKSTACFG.EXE hangs if AUTOEXEC.BAT does not exist.
Solution:
Window 95 default install does not create an AUTOEXEC.BAT. So if you
are not upgrading or you do not have an AUTOEXEC.BAT, Windows 95 does
not require one. If no AUTOEXEC.BAT exists on the client,
WKSTACFG.EXE will hang. This is because it is trying to write to the
AUTOEXEC.BAT file.
The fix is to download the patch "NTWCFG.EXE" from the LANDesk
Workgroup Manager current area of the online services or simply manually
create an autoexec.bat file in the root directory.
HOW TO SETUP A NETWARE* SERVER TO AUTOMATE IPX CLIENT SETUP AND INVENTORY
Product: LANDesk(R) Workgroup Manager, Component: Install
Symptom:
How to setup a NetWare* server to automate IPX client setup and
inventory.
Description:
Enable easier client setup of NetWare clients.
Solution:
1. Run the LANDESK(R) Workgroup Manager client setup to copy files to a
NetWare server.
2. Create a LANDesk Workgroup Manager group to assign users to.
3. Grant all users assigned to the group Read and File Scan rights in
the directory where the LANDESK Workgroup Manager client files where
copied.
4. Grant all users assigned to the group Read, File Scan, Create, Write,
Erase and Modify in the LDLOG directory. (The LDLOG directory is
located in the directory where the client files where copied to).
5. Assign the users you wish to manage to the LANDESK Workgroup Manager
group.
6. Add the following lines to your system login script (NET$LOG.DATt):
IF MEMBER OF "LDWM Group" THEN
INCLUDE VOLUME:CLIENTFILEPATH\LDWMIPX.DAT
END
WHICH USER AGENT SHOULD BE LOADED WITH MULTIPLE NETWORK OPERATING SYSTEMS?
Product: LANDesk(R) Workgroup Manager, Component: Install
Symptom:
In environments where the client workstations logon to multiple network
operating systems, how do we determine which user agent to load?
Description:
Problems remotely controlling workstations.
Solution:
If your client workstations log on to more than one network operating
system, (such as NetWare* from DOS and then Microsoft from Windows*), be
sure that the Workgroup Manager manages the workstation via the network
it logs into first.
For NetWare logins, run "LDWMIPX.DAT from the NetWare servers system
login script.
For Microsoft Network logins change the login script name in the user
profile to point to
"LANDESK\IPX.BAT" for IPX or "LANDESK\NETBIOS.BAT" for Microsoft NetBIOS
workstations.
BTI MICROKERNAL ENGINE (BTRIEVE* FOR WINDOWS NT*) WILL NOT START DURING SETUP
Product: LANDesk(R) Workgroup Manager, Component: Install
Symptom:
BTI Microkernal Engine (BTRIEVE* for Windows NT*) will not start during
setup.
Description:
BTRIEVE requires IPX/SPX compatible transport and NWLink NetBIOS
protocols to be installed before the service will start.
Solution:
Check to see what protocols are installed. If you only have IPX/SPX
compatible transport protocol installed you must remove the IPX/SPX
compatible transport protocol and reinstall it by selecting the default,
which installs IPX/SPX and NWLink NetBios.
Note: If BTI Microkernal Engine is not started during setup, Intel
Inventory Server will not get installed (This service does not get
installed because it is dependent on BTI...). So after resolving why
BTI Microkernal Engine will not start you must run setup again.
INTEL INVENTORY SERVER WILL NOT START DURING SETUP
Product: LANDesk(R) Workgroup Manager, Component: Install
Symptom:
Intel Inventory Server will not start during setup.
Description:
The problem is that TCP/IP is not set up correctly on the Windows NT*
Workgroup Server.
Solution:
Have the customer remove the TCP/IP protocol and then run LANDesk(R)
Workgroups Manager setup. After LANDesk Workgroups Manager setup is
complete, re-install TCP/IP on the machine.
HOW CAN YOU TELL WHETHER YOU'RE RUNNING THE "ENHANCED" OR THE "BASIC" VERSIONOF THE LANMAN DRIVERS?
Product: LANDesk(R) Workgroup Manager, Component: Install
Symptom:
To run NetBIOS support for Windows* v3.1x workstations there is a
requirement to run LANMAN (LAN Manager NetBIOS) enhanced version
drivers. How can you tell whether you're running the "Enhanced" or the
"Basic" version of the drivers?
Description:
Product compatibility.
Solution:
After the LANMAN drivers are loaded into memory, run "NET VER" from the
MS/DOS prompt. The type is included in the description of the driver.
Trademark information