NetLM requirments
=================

NetLM requires the following:

- Either LanManFS (supplied with OmniClient) or LanMan98 (from Warm Silence
Software)
- 64K free memory at all times to run NetLM
- 48K free memory to run the ConfigLM application
- TCP/IP connection or NetBEUI transport system
- LanManager server


Setup
=====

You should place NetLM in a secure place where it can be run from but not
altered from. It is ensential that NetLM is placed in a safe place otherwise
users maybe able to change the NetLM configuration file and the NetLM
templates file (if they have access to a template editor).

NetLM requires the use of either the LanManFS (supplied with OmniClient)
module or the LanMan98 (from Warm Silence Software). The prefered LanManager
module must either have loaded before NetLM loads or be placed inside the
NetLM RMStore folder located inside the NetLM application (hold shift and
double click on !NetLM to open the application up and navigate to the RMStore
folder).

On the Windows NT Server you should have the user profiles shared in the
manner of \\server\username Where server is the name of the logon server
and where username is the users personal folder. NetLM requires user
profiles to be shared this way on the logon server.

In terms of the setup of NetLM this is it but it does require some
cofiguration before NetLM maybe used. See the next section for details.

Configuration
=============

NetLM comes with its own configuration application named ConfigLM which is
distributed with the NetLM package.

Make sure the NetLM application you are going to configure has been seen by
the filer before running the ConfigLM application.

Run the ConfigLM application to start the configuration process. The first
section that needs to be filled in is the LanMan filing system that will be
used. This corispondes to the LanMan module you are using (see the setup
section for further details). Select one of the two filing systems you will
be using.

Next is the logon information section. The logon server is the server on
which all logons happen and is where the users personal work area is stored
and shared from (in the form of  \\server\username - see setup section for
further details). Type the logon server here. The logon share can be setup in
two ways. 
i.) It can either be a fixed share to which users all have access to  OR; 
ii.) It can be a users personal work area to which only the user has access 
to. 

If the first setup is adopted then type the name of the share to be
logged into here otherwise if the user is to logon to their personal work
area that only they have access to type %username% in this field.

The iconbar text field sets what the iconbar text changes from when a user
logs on. If you leave this blank then when a user logs on it will change to
their username or if you enter some text here then when a user logs on it
will change to what you have specified.

The directory prefix allows you to specify when a user logs on what directory
in that share you make their root directory. For example on RM Connect
Networks the users root directory is the MyWork directory inside their
personal folder (so user 95BloggsF would logon to \\server\95BloggsF\MyWork).
You need to prefix the directory you type in this field with a dot. On my
setup I have all the users root directories set to MyWork so I have typed in
.MyWork as the directory prefix.

The user interface section tells NetLM which of the three user interfaces to
use, each being different. You need to play around with this and see which
one is best for your network users needs.

Like on Windows NT Servers User Manager for Domains program you can set to
run logon and logoff scripts in the next section of the configuration. On
these fields simply type the script paths in (for example
ADFS::HardDisc4.$.Network.NetLM.Scripts.logon)

The NetLM options section has three different options: 
Disable Lock Workstation - Tick this if you want users to be able to lock
the workstation requiring either the correct password to be entered to
unlock the system or a reboot of the machine.

Logon on startup - Tick this if you want a dialog box to appear when the
machine boots up telling the user to logon to the network, like on a Windows
machine or an RM Connect Network. If this is ticked then when a user logs off
the screen will popup again (like on a Windows or an RM Connect Network).

Force user to logon - Tick this if want to force the user to logon. The
pointer will be stuck in the network logon dialog box until the user gives a
valid username and password to logon then the pointer will be released and
the user will be logged onto the network.

Click on the Save button to save the configuration settings or click on the
Cancel button to not save any of the settings an quit the ConfigLM
application.

The configuration file is held inside the NetLM application and is called
Config. You can copy this file to other NetLM applications so that you only
have to run the configuration program once to configure NetLM and then copy
the configuration file.

General Administrators Guide
============================

There is a flaw in the lock workstation feature if it is enabled. A user can
unlock the workstation by simply quitting the NetLM application if the new
Acorn boot structure is running on that machine. This can be done by pressing
Alt+Break to stop a task that is running and selecting NetLM.

NetLM, as of yet does not do any auditing or logging so hacking of the
network can not be detected. Network Administrators should setup audits on
the server to track failed logon attempts.

If NetLM for some reason complains about having too many nested structures or
a function/procedure failed then NetLM needs a bigger wimpslot, as set in the
!Run file (default is 48k min. and max.).
