ATREADME.TXT
                 AlertTrack Lite for NetWare(r)
                  Enterprise-wide Alert System 
ABOUT THIS README
This file contains updated information that is not included in 
the Command AntiVirus for NetWare Administrator's Guide. Please 
read this file thoroughly before using AlertTrack Lite.
Installation instructions, system requirements, and basic
troubleshooting information for AlertTrack is located toward 
the end of this README file.
What is AlertTrack?
-------------------
AlertTrack Lite is a Novell NLM that provides forwarding of alerts
and alarms from applications and services to any person throughout
an enterprise.  
AlertTrack can deliver a message using any of seven different 
devices: Numeric Pager, Alpha-numeric Pager, MHS Mail, Pegasus Mail,
SNMP Traps, FaxWare FAX and Network Broadcast Message. An unlimited
number of recipients is supported along with the ability to 
individually configure each to receive messages from any or all of 
the supported devices. All messages that are delivered by AlertTrack 
are indexed and logged for future reference.
All configuration and management is performed through a Windows 
Management Console. The console can "talk" to any Alert Server on 
the network. Managing alerts for an entire enterprise-wide network 
can be performed in a matter of minutes.
__________________________________________________________________
Notes on Command's AlertTrack for NetWare version 4.58.0
12/06/99
PRODUCT ENHANCEMENTS
None for this release.
FIXES
None for this release.
SPECIAL NOTES
None for this release.
_____
Notes on Command's AlertTrack for NetWare version 4.57.1
09/13/99
PRODUCT ENHANCEMENTS
None for this release.
FIXES
None for this release.
SPECIAL NOTES
None for this release.
_____
Notes on Command's AlertTrack for NetWare version 4.57
07/12/99
PRODUCT ENHANCEMENTS
None for this release.
FIXES
If your server was located two or more levels deep in the NDS tree,
AlertTrack may not have loaded. This resulted in -601 or 
-316 errors. This has been fixed.
SPECIAL NOTES
To avoid potential conflicts with Novell Client32 system files in
the Windows/System directory, AlertTrack's NetWare Client API files
are now stored in the AlertTrack program directory.
____
Notes on Command's AlertTrack for NetWare
Version 4.54 SP1 (Service Pack 1)
02/02/99
PRODUCT ENHANCEMENTS
When an ALERTTRACK.EXE user selects a new AlertTrack server, 
AlertTrack no longer logs in to that file server. Because of this, 
the username and password text boxes are not presented. As 
ALERTTRK.EXE reads recipient information and writes device information
to the SYS:ALERTTRK folder, the user is still required to have access 
rights to that folder. 
FIXES
None for this release.
SPECIAL NOTES
None for this release.
Notes on Command's AlertTrack for NetWare 
Version 4.54
12/02/98
PRODUCT ENHANCEMENTS
None in this release.
FIXES
AlertTrack did not allow logging on to a NetWare Directory Service
(NDS) server from the management console unless the /BINDERY switch
was loaded. This is fixed.
Administrators logged onto one NDS tree could not recognize server
objects located on other NDS trees. ALERTTRK.EXE has been modified
to correct this problem.
SPECIAL NOTES
For information regarding the functionality of Command Software 
products with regard to the Year 2000 issue, please visit our web 
site at:
http://www.commandcom.com/html/tech/ts-year2000.html
-----
Notes on Command's AlertTrack for NetWare 
Version 4.53
09/15/98
PRODUCT ENHANCEMENTS
None in this release.
FIXES
None in this release.
SPECIAL NOTES
None in this release.
========= Notes for previous releases of AlertTrack ===============
Notes on Command's AlertTrack for NetWare
Version 4.52
08/13/98
PRODUCT ENHANCEMENTS
None in this release.
FIXES
On rare occasions, an error message would appear stating that 
AlertTrack could not locate the SYS volume object on NDS servers.  
To circumvent the problem, we now look for the name of the volume 
object, "servername_SYS" (where "servername" contains the actual 
name of the server) and use that name it if exists.
SPECIAL NOTES
Enhancements to CSAV for NetWare's VSENGINE requires that you 
install the latest patches for Novell NetWare. The required 
patches are:
     For NetWare 3.11 servers: 311PTG.EXE and LIB311b.EXE
     For NetWare 3.12 servers: 312PTD.EXE and LIB312a.EXE
     For NetWare 4.10 servers: 410PT8B.EXE and LIBUPH.EXE
     For NetWare 4.11 servers: IWSP5b.EXE
For further information regarding these patches, we suggest that you
visit Novell's web site located at: 
     http://support.novell.com/misc/patlst.htm
Notes on Command's AlertTrack for NetWare
Version 4.00 
01/09/98
PRODUCT ENHANCEMENTS
None in this release.
FIXES
Occasional difficulty encountered with AlertTrack's creation
of the SYS:ALERTTRK\DATA directory has been corrected.
When opened for the first time, AlertTrack would sometimes
produce an "Error opening recipient file" message. The message
would appear prior to the successful completion of the user
sending a test message.  This situation has been corrected.
On some NetWare 4.x servers, ALERTTRK.NLM would produce a 
"Could not find SYS Volume object for this server" message 
and then terminate. This appears to be related to the way 
some versions of DS.NLM locate the first volume object
in an NDS tree.  We have circumvented this problem by 
searching for objects whose resource names are "SYS".
The situation involving difficulties with reading the AlertTrack
readme file has been corrected. Prior to the fix, viewing 
the readme could not be accomplished without either (1) extensive
editing or (2) opening it in another viewer such as 
Microsoft Word.
A problem resulting in a "Could not create monitor data 
object..." error message has been corrected. This error
was produced because some NDS trees cannot contained objects
with names that comprise of more than 63 characters. 
SPECIAL NOTES
Beginning with FPNAdmin v.3.01, the AlertTrack server files are 
included in the deploy files lists.  These lists include the 
MODEM.DAT and APPLIC.DAT files which you may or may not want to copy 
to other servers. If you do not wish to deploy any of the AlertTrack 
files, simply remove them from the DEPLOYNW.FPN or FPNADMIN.INI files.
The "Module name is _ALRTTRK.NLM not ALERTTRK.NLM" message is displayed
whenever the AlertTrack NLM is loaded from the server console.  This is
by design; previous versions of FPN would check for a loaded module 
named _ALRTTRK.NLM.
NDS SUPPORT NOTES: As of AlertTrack v2.0, AlertTrack can make
use of NDS on both the server and workstation. The following 
information pertains to NDS support:
     NDS recipient names are specified with the usual 
conventions. Here are some examples:
	cn=dtsitrelis.o=dev
	barbara.documentation.commandcom
     Currently, there is a 48 character limitation on recipient names 
that exists to remain compatible with previous versions of 
AlertTrack. This restriction will be lifted in a future version.
     ALERTTRK.NLM will store its configuration and status information
in bindery objects if it is loaded on a NetWare 3.x server and in NDS 
objects if loaded on a NetWare 4.x server.  This behavior may be 
overridden on 4.x servers; if ALERTTRK.NLM is loaded with the /BINDERY 
switch it will always store its information in the bindery.  This will 
permit these servers to be managed by older versions of the AlertTrack 
Management Console (ALERTTRK.EXE).  For this to work a suitable bindery 
context must be set at the server, of course.
     When logging into a server with ALERTTRK.EXE the same rules 
apply; on 3.x servers a bindery password verification is performed and
it is assumed that the NLM's information can be obtained by examining 
bindery objects on that server, whereas the selection of 4.x server will 
cause ALERTTRK.EXE to use NDS instead.  Should a version of AlertTrack be 
loaded on a 4.x server which does not support NDS (a version prior to 
2.0) or which uses the /BINDERY switch, however, ALERTTRK.EXE can still
administer it.  To do so, check the "Force Bindery Login" checkbox on 
the login dialog.  This will cause ALERTTRK.EXE to communicate with the
ALERTTRK.NLM through bindery services.
     It should be noted that Windows 95 does not ship with any network 
support for browsing NDS trees.  Microsoft has an updated set of 
network drivers that have this capability contained in the MSNDS.EXE 
file available from their Web site.
If you experience a "Cannot attach queue server to queue: EA" error
message on Novell 4.x servers, load ALERTTRK /CLEAN to remove the
previous definition of the AlertTrack print server and then reload
AlertTrack without using any switches. The error message can be
caused by the order in which both the NLM and print server that 
is created by the NLM are logged into NDS.
If FPN Administrator or ALERTTRK.EXE do not show recipients listed
for a particular server, you can use LOAD ALERTTRK /CLEAN and then
reload AlertTrack again without any switches to correct the problem.
Likewise, if you are using a Novell 4.x server with AlertTrack loaded
in bindery mode, you can use LOAD ALERTTRK /BINDERY /CLEAN and then
reload AlertTrack using LOAD ALERTTRK /BINDERY.
5/96
Note for AlertTrack Lite users: If you clear (delete) the activity 
log, you may get a message saying "Activity Log not found" the next time
you attempt to access it. This occurs if there are no new entries in
the log. Once new entries exist (e.g. sending a test message, or other 
alerts ) you will again be able to see the Activity Log.
If you are running Windows 95 and are unable to open the F-PROT.LOG 
file from the workstation, try using NCOPY (NCOPY F-PROT.LOG NEW.LOG) 
to copy the file and then open the log with the new name. The ability 
to view the log file from FPN Administration will be available in an 
upcoming release.
03/14/96
Load the AlertTrack Lite NLM before the F-PROT for NetWare NLM, and 
then do not unload.
The AlertTrack NLM should only be loaded on a NetWare 3.X server or a
NetWare 4.1 server which is using bindery emulation.  (To verify this on
a 4.1 server, at the console type:  set Bindery context
If you see anything about bindery context = then you are in bindery mode.)
Workstations must be logged in using bindery mode.  If using the VLM
requester to log in to NW 4.1, you must type the /B parameter to
have bindery mode.
Loading the AlertTrack Lite NLM on one server is sufficient.
==================================================================
AlertTrack System Requirements
------------------------------
Server:
NetWare 3.11, 3.12, 4.1, 3.x SFT-III and 4.1 SFT-III
500K of free memory
300K of free disk space (+200K for NetWare NLMs)
Workstation:
1 Meg of free memory
400K of free disk space (+600K for NetWare DLLs)
In order to administer AlertTrack, the user must have read/write access
to the files in SYS:ALERTTRK\DATA.
The network must have IPX capability.
Feature List
------------
* Windows Management Console
* NLM Technology for NetWare Servers
* No TSR's 
* No Dedicated Workstation or Server required
* Unlimited Number of Recipients
* Sends Messages via Beepers, AlphaNumeric Pagers, SNMP Traps, MHS Mail,
  Pegasus Mail, FaxWare Fax and Network Broadcast.
* Filter on Priorities/Severities, originating application and content.
* Log all Alerts and Messages
Installing AlertTrack
---------------------
The installation for F-Prot Professional for NetWare and AlertTrack 
have been combined with this release.  You may choose to select either 
or both programs; either one can be used with or without the other.  
Simply run SETUP.EXE on the first installation disk and follow the 
prompts.
As an added bonus for this release, multiple servers may be selected 
as targets for both the F-PROT and AlertTrack products.  Servers are 
selected on the list box by clicking them with the mouse or by pressing
the space bar.
F-PROT.NLM has the ability to reload itself if it is updated by the 
installation or during deployment from FPNAdmin.  AlertTrack does not. 
If ALERTTRK.NLM is already running on a server when it is updated the 
user must manually exit the program and then reload it.
Configuring your Server for Modem Communication
-----------------------------------------------
Before you try to send Pager alerts, you must configure your server for
Modem / Serial communication.
Serial communication on a Novell server requires the loading of a 
communication driver  to control the standard serial ports available on
your server (COM1, COM2 etc.).
The driver (AIOCOMX.NLM) is included with NetWare and can be loaded at 
any time before loading AlertTrack.
Just type at the server console LOAD AIOCOMX.NLM
You may have to specify the port and interrupt of your serial boards. 
On most systems COM1 is using PORT 3F8 and Interrupt 3
		COM2 is using PORT 2F8 and interrupt 4
Be sure to verify that your other hardware cards (i.e. Network card) 
are NOT using the same interrupts and ports.  Specifying the wrong 
interrupt and port may crash your server.
When AIOCOMX is loaded NetWare identifies COM1 as Board 0 Port 0 and
COM2 (if exists on your server) as Board 1 Port 0.
In the AlertTrack directory (SYS:ALERTTRK) you will find a useful 
utility that can help you determine if you installed your AIOCOMX 
driver and the modem correctly.
LOAD SYS:ALERTTRK\TESTAIO.NLM
TestAIO will detect all the boards and ports available through the 
communication driver you loaded and will try to verify that your modem 
is attached and working correctly.
Troubleshooting AlertTrack
--------------------------
There are two load time switches which can be useful for 
troubleshooting: the /DEBUG switch and the /CLEAN switch.
The use of each switch is described below:
Switch      Symptom
------      -------
/DEBUG      AlertTrack will not load in NetWare 4.X and there
            is no error message.
Procedure:  At the console type: LOAD ALERTTRK /DEBUG
This shows the procedures AlertTrack uses and lists any error messages.
If there are any reports of duplicates or errors try running DSREPAIR
for 4.X servers. The reason this occurs is NetWare will tolerate minor
damage to directory services. However, AlertTrack cannot and is 
incapable of recognizing the precise error, but will not load. If you
have a similar situation with NetWare 3.X, try running BINDFIX.
Switch      Symptom
------      ------- 
/CLEAN      AlertTrack is unable to process messages; it receives them,
            but does not send them. 
Procedure:  First, unload AlertTrack: UNLOAD ALERTTRK
            Reload by typing: LOAD ALERTTRK /CLEAN
            This resets the configuration. However, the path needs to
            be re-established. Unload AlertTrack again and then reload 
            to begin messaging: LOAD SYS:ALERTTRK\ALERTTRK
This allows AlertTrack to refresh and begin to resend broadcasts.
=================================================================
PRODUCT SUPPORT
Command Software Systems' technical support includes a variety of 
electronic services. You can contact us at:
Command Software Systems, Inc.
1061 E. Indiantown Rd., Suite 500
Jupiter, FL  33477
   Voice: 561/575-3200 8:00 a.m. to 8:00 p.m. Eastern Standard Time.
     Fax: 561/575-3026
Internet: [email protected]
     FTP: ftp.commandcom.com
     Web: http://www.commandcom.com
In Europe contact:
Command Software Systems, Inc.
UK Branch
Ground Floor
Millbank Tower
Millbank
London SW1P 4QP
If dialing from within the UK:
   Voice: 020 7 931-9301
     Fax: 020 7 931-9302 
If dialing from outside the UK:
   Voice: +44 20 7 931-9301
     Fax: +44 20 7 931-9302
Internet: [email protected]
          [email protected]
          [email protected] 
In Pacific Rim, contact:
Command Software Systems, PTY Pac Rim
Unit 5, 18-20 Floriston Road
Boronia, VIC 3155
Australia
   Voice: 1-300-65-0903 or 613-9762-2203
     Fax: 1-300-65-0904 
Internet: [email protected]
     Web: http://www.commandcom.com.au
====================================== END ========================================