Installing NetWare Navigator on a 4.1 Server
TID1200842
15JUN95
NetWare Navigator 3.0

DISCLAIMER:  THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO
NOVELL.  NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY THIS
INFORMATION.  HOWEVER, THE INFORMATION PROVIDED IN THIS DOCUMENT IS FOR
YOUR INFORMATION ONLY.  NOVELL MAKES NO EXPLICIT OR IMPLIED CLAIMS TO THE
VALIDITY OF THIS INFORMATION.

Question:
What needs to be done to install NetWare Navigator 3.0 on a 4.1 Server?

1. Login Scripts
When you install new clients, the NetWare Navigator setup program modifies
the clients' bindery login scripts to map drives and run the client setup
program.  These lines are shown below:

For DOS/Windows clients:
  MAP N:=<staging_server>\SYS:
  MAP INS S16:=<staging_server>\SYS:\NETNAV\USER
  MAP INS S16:=<staging_server>\SYS:\NETNAV\CODE
  PCCOMPATIBLE
  #NNWSI <user_name> <staging_server>

For OS/2 clients:
  MAP N:=<server_name>\SYS:
  #N:\NETNAV\OS2USER\NNWSNLM <user_name> <server_name>

In order for the NetWare Navigator clients to be able to login to NetWare
Directory Services, these changes will need to be made to the NetWare
Directory Services login scripts.  You could copy the lines from each
user's bindery login script to their NetWare Directory Services login
script - but it would be painstaking for a large number of users.

Instead, you can copy the lines to the login script for Organizational Unit
(OU) where your users reside, and then change the NNWSI line the following:

     #NNWSI %LOGIN_NAME <staging_server>

The "%LOGIN_NAME" tells the login program to substitute the name of the
user currently logging in.  If not all users in the OU will be NetWare
Navigator clients, you can surround all of the NetWare Navigator lines with
an "IF MEMBER OF GROUP" clause.  You would then need to add all of the
users you want to be NetWare Navigator clients to the group name you
specify.  The OU login script would then look like the following:

     IF MEMBER OF "<group_name>" THEN
     MAP N:=<staging_server>\SYS:
     MAP INS S16:=<staging_server>\SYS:\NETNAV\USER
     MAP INS S16:=<staging_server>\SYS:\NETNAV\CODE
     PCCOMPATIBLE
     #NNWSI %LOGIN_NAME <staging_server>
     END 
 

2. NWSDRUN.NCF and AUTOEXEC.BAT File Changes
NetWare Navigator uses Storage Management Services (SMS) for some of the
distribution functions  Get SMSUPx.EXE from Novell via CompuServe or  
Internet.  Follow all of the readme instructions for SMSUP2 and SMSNAV to   
customize NetWare Navigator to use the latest SMS files.

In the NetWare 4.1 environment, some of the SMS file names have changed.  

The NWSDRUN.NCF file needs to be modified to load the correct NLM files. 
Correspondingly, the clients' AUTOEXEC.BAT files need to change to load the
SMS TSR that works with the updated NLMs.  The contents of the NWSDRUN.NCF
file should be the following:
     bstart
     load tsa410
     load tsaproxy
     load tsados
     load djobschd
     load djobfdbk
     load sjobdmgr
     load sjobfdbk

The NetWare Navigator section of the AUTOEXEC.BAT file should be changed to
load TSASMS.COM, instead of TSA_SMS.COM, so that the lines look like the
following:
     REM ----- NetNav statements BEGIN ----
     SET NETNAV=C:\NETNAV
     SET NETNAVC=N:\NETNAV\CODE
     COPY C:\NETNAV\NETNAV.SMS C:
     C:\NETNAV\SCHEDRUN.COM
     C:\NETNAV\TSASMS.COM /N=<user_name> /P=NWSD /D=C
       /SE=<server_name>
     REM ----- NetNav statements END ------

3. Bindery Contexts
In order for NetWare Navigator to be installed and functional, the Staging
Servers and Distribution Servers need to have a bindery context set.  At
install time, NetWare Navigator adds some objects to the bindery.  On a
NetWare 4 server, these objects will go into the NetWare Directory Services
context set as the server's bindery context.  Once NetWare Navigator is
installed, the bindery context needs to continue to be set to the context
where the objects were added, in order for NetWare Navigator to continue to
operate.  

NetWare 4.1 allows you to set up to 16 bindery contexts, so this should not
affect the operation of any other applications that require bindery
emulation.  To set a bindery context on the server, type:

     SET BINDERY CONTEXT=<context_name>

To set multiple bindery contexts, separate each context by a colon, like
the following:  SET BINDERY CONTEXT=<context1>;<context2>

To see what the server's bindery context is currently set to, type "SET
BINDERY CONTEXT" or "CONFIG".

For each context you want to set as a bindery context, you also need to
make sure that the server has a writeable copy of the replica of the
partition containing that context.  You can ensure that it does by using
the Partition Manager tool in the NetWare Administrator application.  For
more detailed information on setting up bindery emulation, refer to the
NetWare 4.1 documentation.

4. Other Issues
NetWare Navigator may experience problems if it's configuration file is
compressed using NetWare 4.x compression.  Flag NNSRVCFG.NET to dc (don't
compress) on the Distribution server \system directory.

-----------------------------------------------------------------
Any trademarks referenced in this document are the property of their
respective owners.  Consult your product manuals for complete
trademark information.
-----------------------------------------------------------------