SYMANTEC--PETER NORTON GROUP

README.TXT--August 29, 1994
Copyright 1993, 1994 Symantec Corp. All Rights Reserved.

NORTON ADMINISTRATOR FOR NETWORKS
Version 1.5


Welcome to Norton Administrator for Networks!

Please read this document carefully; it contains important information not included in the user's guide. This document and the online help have the latest and most accurate information.

For easiest reading, MAXIMIZE this window by clicking the Maximize button. You may also want to print it for future reference.

If you still have questions after reviewing this ReadMe file, call Technical Support for assistance.


---------------------------------------------------
CONTENTS
---------------------------------------------------
1. LOADING THE DOS AGENTS
    1.1 Novell NetWare
    1.2 Microsoft LAN Manager and IBM LAN Server
    1.3 Banyan Vines
2. CHANGES TO AND LIMITATIONS OF AGENTS
    2.1 Minimum Memory Requirement to Run Each Agent
    2.2 Additional Information about NANODE.EXE
    2.3 Metering Agents and /NOEXEC Command-Line Option
    2.4 Running LAN Inventory Agent in a DOS Box
    2.5 EISA Systems and Memory Managers
    2.6 Additional Information about NANODEW.EXE
3. CHANGES TO CONFIGURATION FILES AND ENVIRONMENT
    3.1 Changes to NADMIN.INI
    3.2 Environment Variables
    3.3 Configuration Files List
    3.4 SYMNET.INI
4. NETWORKS OTHER THAN NOVELL NETWARE
    4.1 Banyan Vines NIC Addresses and User Groups
    4.2 Broadcast Messages
    4.3 LAN Inventory Information about Networks
    4.4 LAN Manager and LAN Server: Synchronizing Times
        on Workstations with Times on Network
5. NORTON ADMINISTRATOR ENHANCEMENTS
    5.1 Filtering Operators
6. OS/2 NATIVE INVENTORY AND SUPPORT FOR THE DOS AGENTS
    6.1  Inventory: OS/2 vs. OS/2 DOS Box
    6.2  REQUIRED FILES
    6.3  NARUNOS2 - Running agents automatically
    6.4  System Version Requirements: Network Drivers and OS/2 CSDs
    6.5  Special Note
    6.6  Metering & Distribution in OS/2 DOS Boxes
    6.7  Running the agents successfully in DOS boxes
    6.8  Taking a stand-alone inventory
    6.9  Installing from WIN/OS2 sessions
    6.10 Netware OS2 and UNC names
    6.11 Running DOS agents in OS/2
7. TIPS
    7.1 Stub Executables (Transient Loaders)
    7.2 Minimum Rights Required per Directory
    7.3 Location of Login Scripts
    7.4 Note on Partial Scan times
8. MISCELLANEOUS
    8.1 DOS and UNC Names for Files
    8.2 Duplicate Selections of Recipients and Licensees
    8.3 QuickHelp Screens
    8.4 Editing .INI Files
    8.5 NDIS Drivers
    8.6 Switches
    8.7 Mac Inventory System Dialogs

===================================================
1 LOADING THE DOS AGENTS
===================================================

After you install Norton Administrator for Networks, you need to load the agents so you can collect data from, distribute data to, and meter the use of applications on each workstation.

---------------------------------------------------
1.1 Novell NetWare

If you have a NetWare network, you probably added the LAN Inventory and Software Distribution agents to your system login script so that data can be collected from and distributed to each workstation easily. You may want to adjust the login script to use the batch file TSRLOAD.BAT that comes with Norton Administrator and loads the License Metering agent NANODE.EXE to meter products.

---------------------------------------------------
1.2  Microsoft LAN Manager and IBM LAN Server

Due to the high memory overhead of the NET command for a LAN Manager or LAN Server network, you may need to write a batch file to load the DOS agents that includes:
***************************************************
net login user password /domain:domain
*** any net use commands necessary
    ex. net use e: \\servername\c$
cd nadmin\agents
*** be sure that the login script
    puts you on the right drive.
nainv
nadist
nanode
***************************************************

---------------------------------------------------
1.3 Banyan Vines

Loading the DOS agents on a Banyan Vines network requires the use of the post login command (postlogin command /c agents.bat) in the user profile. You use a command similar to the following to execute a batch file that loads all three agents:
***************************************************

cd nadmin\agents   ** be sure that the login script puts you on the right drive.
nainv
nadist
nanode
***************************************************

NOTE:  See Section 4 for other important Banyan Vines information.



===================================================
2. CHANGES TO AND LIMITATIONS OF AGENTS
===================================================

This section explains the changes made to the metering agents and the limitations encountered when running the LAN Inventory agent from a DOS box.


---------------------------------------------------
2.1 Minimum Memory Requirements to Run Each Agent

       AGENT                        MINIMUM MEMORY

LAN Inventory Agent:
NAINV.EXE   (for DOS)               325K

Software Distribution Agents:
NADIST.EXE  (for DOS)               325K
NADISTW.EXE (for Windows)           2MB (Standard Windows Req.)

Metering Agents:
NAMETER.EXE  (for DOS)              325K
NANODE.EXE   (for DOS)              4 K TSR (optional)
NAMETERW.EXE (for Windows)          2MB (Standard Windows Req.)
NANODEW.EXE  (for Windows)          2MB (Standard Windows Req.)

NOTE:   Please remember that if running from the login script, 
you will need additional memory.

---------------------------------------------------
2.2 Additional Information about NANODE.EXE

NANODE.EXE has two additional command-line options:

/NODOS   With this option, the TSR does not meter DOS applications. When Windows
         starts up, NANODE launches NANODEW.EXE.
/NOWIN   With this option, the TSR does not meter Windows applications. That means
         it does not launch NANODEW.EXE.

For the /AGENTS:pathname command-line option (which provides the pathname to the directory where the metering agents NAMETER.EXE and NANODEW.EXE reside), it is best to specify a regular DOS pathname. If you use the Universal Naming Convention (UNC), Windows cannot load NANODEW.EXE if the server name or the volume name is more than 11 characters.

NANODE is disabled if DESQview is launched after NANODE and returns to normal when DESQview terminates. NANODE works correctly if loaded from within a DESQview task.

---------------------------------------------------
2.3 Metering Agents and /NOEXEC Command-Line Option

The /NOEXEC command-line option works with all the metering agents (NANODE, NANODEW, NAMETER, and NAMETERW). Without it, an error is displayed when a system error occurs (because the license system is not available or fails), but the application is still launched. With this option, the application is not executed unless a license can be verified.

---------------------------------------------------
2.4 Running LAN Inventory Agent in a DOS Box

The LAN Inventory agent, when run in a DOS box, cannot collect the following information or collects it inaccurately:
    Information about the network card and setup may not be collected.
    Hard disk models are not detected.
    Benchmark information is not collected.
    I/O port information may be inaccurate.
    Memory and Memory Manager information may be inaccurate.

---------------------------------------------------
2.5 EISA Systems and Memory Managers

Some memory managers, when running on systems with an EISA bus, incorrectly process Interrupt 15.  Therefore, the LAN Inventory Agent defaults to not performing the Expansion Slot tests.

If you enable the Expansion Slot test and experience lockup problems with the LAN Inventory Agent, disable the Expansion Slots test from the Configure menu in the Console, or use the /NOSLOTS command-line switch on workstations affected. The lockup problem may also occur if the memory manager was manually told to map RAM into the memory regions starting at segment F000 or above.

---------------------------------------------------
2.6 Additional Information about NANODEW.EXE

The Windows metering agent NANODEW.EXE will meter DOS applications launched from Windows even if the metering TSR NANODE.EXE is not loaded.  However, DOS application launched from a DOS box or indirectly through a PIF file are not metered unless NANODE is loaded as well.

You can use NANODE.EXE with the /NODOS command-line option to prevent it from metering DOS application but still have it launch NANODEW.EXE when Windows starts up.

When NANODEW.EXE denies access to an application (for example, when no more licenses are available), two message boxes will usually appear.  The first, is a message from NANODEW notifying the user that no licenses are available.  The second message, if it appears, is from the Windows shell (for example, Program Manager, Norton Desktop for Windows, etc) notifying the user that it could not launch the application.  The second error message is normal and is usually not very descriptive of the denied access.




===================================================
3. CHANGES TO CONFIGURATION FILES AND ENVIRONMENT
===================================================

This section covers changes to the configuration files and introduces the Norton Administrator environment variables.

---------------------------------------------------
3.1 Changes to NADMIN.INI

If you use Norton AntiVirus for NetWare and/or Norton pcANYWHERE for Windows, you can add either or both of the following sections to the NADMIN.INI file in your Windows directory.

[pca]                   Section for Norton pcANYWHERE for Windows
path=c:\winaw           Specifies the location of the WINAW.EXE program.
loadanyway=1            Causes the pcANYWHERE icon to load regardless of its path and file
[nav]                   Section for Norton AntiVirus for NetWare.
pathnlm=c:\navnlm       Specifies the location of the NAVNLMW.EXE program.
pathnet=c:\navnet       Specifies the location of the NAVNETW.EXE program.
loadanyway=1            Causes the Norton AntiVirus for NetWare icon to load regardless of path and file.

---------------------------------------------------
3.2 Environment Variables

Norton Administrator for Networks has added four environment variables that can be set from your AUTOEXEC.BAT file or the command line.

NAINV.EXE, the LAN Inventory agent, has default configuration settings that can be changed from the console using the Configure pulldown menu. In addition, you can add to or override the configuration information in NAINV.CFG by setting NAINV, the environment variable which configures the LAN Inventory agent. For example to turn off the software inventory, you would use:

SET NAINV=/NOSOFTWARE

The environment variable setting can be overridden by running NAINV from the command line with command-line options.

NADIST.EXE, the Software Distribution agent for DOS, operates in the same way--but its configuration file is NADIST.CFG and its environment variable is NADIST. For example, you can change the database the agent searches for jobs to deliver to a given workstation by setting the environment variable as follows:

SET NADIST=/DATABASE:f:\nadmin\data\latest.dst

Two other environment variables assist the LAN Inventory agent in gathering data about a workstation. SYMNETWORK and SYMNODE override a workstation's network number and Network Interface Card (NIC) address, respectively. For example:

SET SYMNETWORK=00000152
SET SYMNODE=08000900B06D

To stop the agents from using XMS memory:

SET RTVMEXT=0 

To stop the agents from using EMS memory:

SET rtvmexp=0

---------------------------------------------------
3.3 Configuration Files List

Nadmin.dat (in the agent's directory): tells the agents where to look for their individual configuration files.

Nainv.cfg: This is the file for the inventory agent to tell the agent what to test.

Nameter.cfg: This is the configuration file for all of the metering agents.

Nadist.cfg: is the configuration information for the distribution agents

Nadmin.ini (Windows directory): This is the file that holds all of the settings that you set in the console through configure console. This includes the default data directory which allows the menu bar icons to know what databases to open.

Nadmin.cfg: shows what directories were used during installation.

In the console, choose the menu bar option configure, then choose any of the three agents configuration buttons. Open the configuration screen.  This will copy the data directory from the console (stored in nadmin.ini) to that agent's configuration (stored in the respective .cfg file). If you have two administrators (or the same administrator with two different sets of data)  and experience problems, it may be because the data path for the menu bar icons is being changed by the console configuration stored locally.

--------------------------------------------------- 
3.4 SYMNET.INI

The SYMET.INI files provides a way of specifying network configuration information for NAN.  

There is a section in SYMNET.INI for configuring what type of network a console is to use.  This is useful when running dual protocols under windows.

Example:
[Network]
Nettype=0
Netdll=symnw34.dll

Where the Nettype choices are:
0 = no network
1 = Microsoft Network
2 = LanManager
3 = Netware
4 = Banyan Vines

And the Netdll choices are:
symnw34.dll = Netware
symlm24.dll = LanManager
symbv44.dll = Banyan Vines



===================================================
4. NETWORKS OTHER THAN NOVELL NETWARE
===================================================

---------------------------------------------------
4.1 Banyan Vines NIC Addresses and User Groups

Network Interface Card (NIC) addresses are automatically detected in Banyan Vines versions 5.52 (5) and greater.

If you are running a version of Banyan Vines prior to 5.52 (5), you may use the /ASSIGNID switch to assign a permanent node address.  This will create a SYMANTEC directory on the boot drive, containing a file SYMNET.INI with a unique node and network number assigned to that system.

The solution suggested in NAN 1.0 is also still viable, though more cumbersome for the Administrator.  That is to set the environment variables for SYMNODE and optionally SYMNETWORK to a unique value for each workstation on the network that will be using Norton Administrator. See the section on environment variables later in the ReadMe for more details about SYMNODE and SYMNETWORK.

Example:
       SET SYMNODE=00AA002F5946
       SET SYMNETWORK=001

If your network is very large, then the selection of users and groups can take a very long time. Setting the BAN_SEARCH environment variable to a location restricts user and group enumerations and improves performance.

Example:
       SET BAN_SEARCH=*@*@myorg

The Software Distribution agents (NADIST.EXE and NADISTW.EXE) will not distribute to groups unless the BAN_SEARCH environment variable is detected on the workstation running the Software Distribution agent.

---------------------------------------------------
4.2 Broadcast Messages

On non-Novell networks, users need to check for messages. For example, when no more licenses are available for a product that has a concurrent-use license policy, users can be notified when a license becomes available. On a LAN Manager network, the user would receive a WinPopup message. If an application covers the entire screen, the user would not see the message without specifically looking.

---------------------------------------------------
4.3 LAN Inventory Information about Networks

On non-Novell networks, some of the data collected about networks is not available. These fields are Server Name, NDIS Version, Vendor, Revision, Revision Date, and Copyright. The Detail button on the dialog box showing the Network Category of LAN Inventory is grayed because none of the data on the Network Detail dialog box is available.

---------------------------------------------------
4.4 LAN Manager and LAN Server: Synchronizing Dates and Times
    on Workstations with the Date and Time on the Network

For accurate metering and distribution, make sure that the date and time on the workstations are the same as the date and time on the network. For example, if the workstation's date is 1980, distribution jobs with start dates in 1993 are not distributed.

---------------------------------------------------
4.5 Dec Pathworks 

Under certain configurations of Dec Pathworks, Users and Groups are  not accessible from distribution and metering.  See Section 3.4 on SYMNET.INI for additional hints on how to work with different network configurations.  If you are experiencing problems with Groups try the no network switch.



===================================================
5. NORTON ADMINISTRATOR ENHANCEMENTS
===================================================

This section explains enhancements to Norton Administrator not covered in the user's guide or in online help.

---------------------------------------------------
5.1 Filtering Operators

When you are creating a filter you have two additional operators:

Contains
Member Of

These operators do not apply to all fields.

If a field is alphanumeric, you can search for a partial match. For example, you can search for server names that contain a certain substring. The following filter would find records containing Server Name of "central", "innocent", and so forth.

Server Name contains "cent"

The Member Of operator helps you find the users in a group. The User Name fields in the License Metering Log and Current Users windows can be used in a filter with the operator Member Of. For example: User Name member of "ACCOUNTING" filters the database for records for anyone who is a member of the ACCOUNTING group.



===================================================
6. OS/2 NATIVE INVENTORY AND SUPPORT FOR THE DOS AGENTS
===================================================

This section will describe the differences between inventories run in OS/2 and in an OS/2 DOS Box.  It will also give tips and techniques specific to the OS/2 environment.

---------------------------------------------------
6.1 Inventory: OS/2 vs. OS/2 DOS Box

Differences between the OS/2 Inventory agent and the DOS agent run in an OS/2 DOS box are summarized on page 1-14 of the manual.  Additional differences are:

Memory:  When inventorying an OS/2 machine, the DOS agent will report erroneous amounts for Extended, Expanded, HMS, and Available memory, and can report more than exists.  The OS/2 agent returns the actual amounts of memory.  Note that the OS/2 agent may report more memory available than physically exists because OS/2 includes in its calculation any disk space that is available for use as virtual memory.

Serial Ports: The DOS Agent will report as missing the serial port with the mouse on it, and may get the IRQs wrong.  The OS/2 agent will report the mouse on the serial port list.

Operating System Specifics: When an OS/2 machine is inventoried by the DOS agent, the Operating System information is correct for the environment within that DOS Box.  It is not necessarily meaningful to the outer OS/2 environment.  For example, OS/2 does not enforce a LASTDRIVE or environment size restriction.  The OS/2 agent, on the other hand, will reflect OS information correct for the OS/2 environment itself.

On the software scan, the DOS Agent will not see directories or files with names that are HPFS-legal but not DOS-legal.  For example, C:\"Norton Commander" is a legal HPFS name, but neither the directory or any software in it will show up in a DOS-box scan.  They will show up, with the complete path and file name, in an OS/2 agent software scan.

---------------------------------------------------
6.2 REQUIRED FILES

For the OS/2 Inventory Agent (NAINVOS2.EXE), the same data file restrictions apply as to the DOS agent NAINV.EXE.  However, the OS/2 agent may also require a DLL.

   SYMNW34O.DLL  is used for Novell networks.

   SYMLM24O.DLL  is used for Lan Manager, Lan Server, and DEC Pathworks networks.

If a necessary DLL is not found, the inventory will still be taken, but the networking information will not be reported.  Consequently, the inventory record will not be stored by the NIC address and user name, which is essential for guaranteeing uniqueness in the inventory database.

--------------------------------------------------- 
6.3 NARUNOS2 - Running agents automatically

NARUNOS2 is designed to get around the problem of not having a login script capable of running the agents under most OS/2 networks.  NARUNOS2 circumnavigates this problem by checking for specified files, presumably on the network, before executing one of them.  NARUNOS2 can be run from STARTUP.CMD.  It is covered in Appendix A, with some clarification below.

NARUNOS2 can watch for and run up to five programs.  It requires a parameter file with up to five lines, one per program, with a structure as follows:

 <exe_name> <data_file_name> <delay_between_tries> <delay_between_repeats> <parameters>

(Note that page A2 of the documentation shows an example of this command line that contains commas separating the fields.  The commas are incorrect.  Only spaces separate the fields in this command line.)

<exe_name> and <data_file_name> may be the same, and must include an explicit path.  (The "path" statement is not searched.)  The executables may be DOS, Windows, or OS/2 EXEs.

<delay_between_tries> is in seconds, and is how long to wait between attempts to find those two files.

<delay_between_repeats> is how long in MINUTES to wait before re-executing the process.  For example, use "60" to repeat it once an hour.  Use "0" to only run the process once.

<parameters> are the parameters to pass to the executable, such as "/MACHINENAME="FRED'S PC"".

Again, note that the <delay_between_retries> is in SECONDS, while the <delay_between_repeats> is in MINUTES.

Because NARUNOS2 can be run at startup, it should be copied to the local hard drive.  If you can run it from the network instead, you don't need it because you could instead run NAINVOS2 directly.  The only additional file required by NARUNOS2 is NARUN.DAT.  The currently logged directory and all current network directories will be searched for NARUN.DAT.  This allows MIS to put NARUN.DAT in the login directory IF the network device drivers support a login directory visible before the user has logged in.

---------------------------------------------------
6.4 System Version Requirements: Network Drivers and OS/2 CSDs

If running LanMan, you MUST have the latest client requester software, including the December '93 release of  NETWKSTA.SYS available from Microsoft.  At the same time, you must clear the attributes of the hidden file C:\OS2VER and, in that file, change the reference "netwksta.200" to "netwksta.sys".  (You may then restore the attributes to HSR if you wish.)  Inventorying without this release of the requesters will crash the workstation.

If running Novell, you also may need a recent version of the Netware OS Requester, which can be downloaded from CompuServe.  Please note that there is performance degradation when doing a software scan if the April '94 Requesters are loaded.  We suggest you not use this version of the Requesters.

If running OS/2 V2.0, you must have the OS/2 service pack XR06100 (or a later version) installed.  Service Paks are also available on CompuServe or directly from IBM.  

---------------------------------------------------
6.5 Banyan Special Note

For uniquely identifying each workstation  on a Banyan network, use the /ASSIGNID switch.  This will create a SYMANTEC directory on the boot drive, containing a file "symnet.ini" with a unique node and network number assigned to that system.  Do not delete this file.  The /ASSIGNID switch need only be run once.  Once this data is in place, specifying it again will have no effect.

---------------------------------------------------
6.6 Metering & Distribution in OS/2 DOS Boxes

Both general distribution and the metering of DOS and Windows applications can be accomplished on an OS/2 system using the DOS or Windows agents.  This is mentioned briefly in the manual, pages 1-19 and 1-21.

Metering cannot be done on OS/2 executables, but will work fine on Windows and DOS executables if the following precautions are taken:

1) For DOS executables, the DOS agent NANODE must be called from the system's AUTOEXEC.BAT.  AUTOEXEC.BAT is run for most starting DOS sessions, even those generated by WIN-OS2.

2) For Windows executables, NANODEW must be properly installed and run in the WIN.INI.  (Follow the instructions in the manual.)

3) For both DOS and Windows, the network must be configured properly.  (See the readme section "Running the agents successfully in DOS boxes" below.)  The DOS agents will work well in Novell GLOBAL mode, as well as when the DOS box has been logged in.  The latter is required by all other networks.

Distribution could be done using the same methods, but it makes more sense to run distribution automatically using NARUNOS2.  (See "NARUNOS2 - Running agents automatically" above.)  This allows the distribution to be run regularly, after checking for login, without any user input or action.

The Distribution agents are DOS-based, so they will not be able to see, access, or distribute to HPFS long filenames.  Since the DOS sessions won't see those filenames or directories, this should not present a problem.

---------------------------------------------------
6.7 Running the agents successfully in DOS boxes

OS/2 DOS boxes can access mapped network drives even when the DOS session itself is not logged into the network.  Because OS/2 provides a virtual machine for the DOS session, most networks require a separate login for each DOS box to be able to report the NIC address or user name, information that is needed to identify the workstation to the database.

Novell networks can be configured in GLOBAL or PRIVATE modes.  In GLOBAL mode, all network information is passed on to each DOS box.  This works well for the DOS agents, but fails for the Windows agents under WIN-OS2.  If you intend to use the Windows agents (NANODEW or NADISTW), you MUST use PRIVATE mode.

To set up PRIVATE mode, verify that the OS/2 CONFIG.SYS contains the following line:

     DEVICE=C:\NETWARE\VSHELL.SYS PRIVATE

This line should already be in CONFIG.SYS, but may end with "GLOBAL" instead.  Change it to "PRIVATE".  Next, add the following to the AUTOEXEC.BAT.  (AUTOEXEC.BAT is only executed when DOS boxes are started.)

     C:\NET\IPX.COM
     C:\NET\NETX.EXE
     cd \net
     login

A disadvantage of the PRIVATE mode is that the user must log in for each DOS box separately.

Lan Manager, Lan Server, and their derivatives do not have an equivalent of the Novell GLOBAL mode.  Consequently, the user must log in before using any of the DOS agents in an OS/2 DOS box.

For an IBM LanServer AUTOEXEC.BAT, add:

     CALL INITFSI.BAT
     NET LOGON 

We suggest you use the /ASSIGNID information described above for Banyan systems.  Note that this requires the /ASSIGNID address be used for distribution and metering.  We do not support groups on Banyan.

--------------------------------------------------
6.8 Taking a stand-alone inventory

If you wish to use the OS/2 inventory agent (NAINVOS2) on systems not connected to the network, you can carry the program on a diskette to each system.  This process is described on page 3-67 of the manual.  Note that if the systems are not on the network or you don't desire network-specific information (the user name or NIC address), you do not need the DLL files.  NAINVOS2.EXE is sufficient.

---------------------------------------------------
6.9 Installing from WIN-OS/2 sessions

The Norton Administrator For Networks must be installed from an existing WIN-OS/2 session via the Windows File Manager or using the File Run menu command.

---------------------------------------------------
6.10 Netware OS2 and UNC Names

You must use literal driver letter identifiers if your UNC servername (including path)  is greater than 8 characters.  This includes both the NADMIN.DAT file and License and Distribution configuration definitions from within the NAN console.

---------------------------------------------------
6.11 Running DOS agents in OS/2

To use the Norton Administrator for Networks DOS agents in OS/2, you need the do the following:

     Get the latest DLLs from Novell. These are available on CompuServe and should have a file date of April or later in 1993.

     These must be properly installed in the netware DLLs directory on the OS/2 system, usually C:\NETWARE, over the older DLLs.

     Run the agent with the current working directory set to a network drive.

     Add a preferred server setting to the file NET.CFG. This file is usually located in C:\. It can be modified or created using the INSTALL program in the Netware directory. The program helps you with the configuration by enumerating the options. The preferred server entry    is as follows:
            PREFERRED SERVER xxxxxxxxxx

     Do NOT use the NWTools option to set this preference    because it puts the information in an NWS (NetWare Script) file, which must be manually invoked.    Enable network support in DOS sessions. This requires two device drivers in the CONFIG.SYS file: VIPX.SYS and VSHELL.SYS (both of which are in the Netware directory).

     Without these two programs, the DOS session cannot detect the network ID or address and, therefore, assumes that no network is installed.

     (Since neither driver is required for accessing the network drives in a DOS, drives mapped from an OS/2 session when the DOS session was started are visible under DOS even when these drivers are not installed.)

     VIPX.SYS and VSHELL.SYS add an item to the DOS Session.  Settings list in object notebooks: Network_Resources.  Set this to "Global". It defaults to global for all objects if you add the word "GLOBAL" as a command-line option after the VSHELL.SYS entry in CONFIG.SYS.  When "Global" is set, all the DOS and WIN-OS2 sessions share all the mappings and IDs currently active in the OS/2 sessions. ("Private" requires a login from each session in  order to access the network. It also restricts those mappings to just that session.)

     Since most users will be attaching through either NWTools or command-line utilities instead of logging    in, you must run the agents from a command file.

     TIP: Create one command (batch) file that attaches the users, maps their drives, and runs the agents. Then use an icon to represent the entire login process on the desktop. Have it call the command file.

     If the user attaches through the "login" screen provided by IBM (which doesn't actually log in or set the preferred server), you should remove the word CONNECTIONS from the SET AUTOSTART= line in the CONFIG.SYS file. They will have to use some other method for attaching.

     NOTE: This is essential, but does not allow you to use IBM's screen any more. Users will have to log in manually using ATTACH or NWTools, etc.

     Attach with NWTools, set the maps, etc., save the settings to a script file (for example, NET.NWS) and create an object that calls NWTOOLS NET.NWS.



===================================================
7. TIPS
===================================================

This section is designed to save you time and eliminate problems before they occur.

---------------------------------------------------
7.1 License Metering and Stub Executables (Transient Loaders)

Often the file that starts an application is only a stub executable, also called a transient loader. It launches one or more other files and comes to an end. The file you really want to meter (to see how long the product was in use) is one of the ones launched by the stub. This section provides some examples:

Norton Desktop for Windows
NDW.EXE launches NDWMAIN.EXE. Meter NDWMAIN.EXE.

Word Perfect for Windows
WPWIN.EXE launches WPWINFIL.EXE. Meter WPWINFIL.EXE.

Word Perfect for Windows 6.0
WPWIN.EXE launches WPWIN60.EXE. Meter WPWIN60.EXE.

cc:Mail for Windows
WMAIL.EXE launches CCMAIL.EXE. Meter CCMAIL.EXE.

---------------------------------------------------
7.2 Minimum Rights required per directory

Console: Read and Write access

Agents:  Read access

Data:    Read, Write and Modify

---------------------------------------------------
7.3 Location of Login Scripts

Netware:  Sys:\public\NET$LOG.DAT

LAN Manager:  Defined by the administrator within the net logon service.

LAN Server:   Defined by the network administrator.

Banyan Vines: Profile defined in the manage utility.

---------------------------------------------------
7.4 Note on Partial Scan times

Partial inventory scans may take longer than specified in the configuration file in order to complete the directory being scanned when the timeout is reached.  (ex. set partial to 3 seconds and scan the windows directory.)



===================================================
8. MISCELLANEOUS
===================================================

---------------------------------------------------
8.1 DOS and UNC Names for Files

Don't use DOS pathnames of more than 200 characters.

When running a Windows application from the command line, don't use UNC names with components of more than 11 characters.

---------------------------------------------------
8.2 Duplicate Selections of Recipients and Licensees

If you select the same recipient for a Software Distribution job or the same licensee in License Metering more than once, Norton Administrator eliminates the duplicates when you click OK to exit the dialog box where you made your selections.

---------------------------------------------------
8.3 QuickHelp Screens

QuickHelp is a new Norton help feature designed to help you find things quickly. If you are using large fonts on your monitor, you may find that your QuickHelp screens are a bit difficult to read. The bitmap is being stretched beyond its limits.  We recommend not using large fonts when using QuickHelp.

---------------------------------------------------
8.4 Editing .INI Files

When you replace an entire section of an .INI file, the old section is deleted, and the new section is added at the bottom of the file.

---------------------------------------------------
8.5 NDIS Drivers

NDIS drivers are unique to each network card vendor.  Some are modified in a way that prevents NAN from getting the proper information.  If this affects you, you may disable the NDIS test in the Tests Configuration dialog.  (Choose LAN Inventory from the Configure menu, then choose the Tests dialog.  Uncheck the NDIS Driver Information item.)

--------------------------------------------------- 
8.6 Switches

To get a complete list of all switches available for each agent, from the DOS prompt type the agent followed by /help.  For example: c:>nainv /help

--------------------------------------------------- 
8.7 Macintosh Inventory System Dialogs

When viewing the System dialog on the Norton Administrator Console for a Macintosh inventory, the information displayed is not "collected" information. It is "static" information filled in by the Norton Administrator Console for that machine.  The information allows an administrator to see the base configuration for that particular computer without any enhancements, such as an accelerator or math coprocessor.  For example, a basic Macintosh IIci has a clock speed of 25 MHz.  If this particular IIci contained an accelerator card that increased its clock speed to 50 MHz, the administrator would still see the 25 MHz value in the System dialog since this is the base configuration clock speed for the IIci.

----End of ReadMe-----

