======================================================================
                Halcyon PrimeAlert (R) Agent for Windows
                              Version 5.2.0
                   For use with Sun Management Center

                            ReleaseNotes
======================================================================

======================================================================
VERSION/DATE: 5.2.0a/2008-04-19


ENHANCEMENTS:
----------------------------------------------------------------------

- Support for Sun MC 4.0.

- Support for x86 platforms.


UPGRADE STRATEGY:
----------------------------------------------------------------------

- None. This version is compatible with the previous release.


KNOWN PROBLEMS:
----------------------------------------------------------------------

- During installation of the PrimeAlert Agent for Windows, the user can
  select which user will run the Halcyon PrimeAlert Agent service. The
  'Select User' button does not work properly when a non-default user
  is desired.

- [LogFileAlert] If a file is scanned using the full scan mode, the
  file is only re-scanned when the file's size or modification time are
  changed; the file should actually be re-scanned periodically
  regardless of whether or not the size or modification time have
  changed.

- [LogFileAlert] If a pattern regular expression contains round
  brackets, (), an incomplete matching line may be displayed.


======================================================================
VERSION/DATE: 5.2.0/2007-04-30


ENHANCEMENTS:
----------------------------------------------------------------------

- The PrimeAlert Agent for Windows is now interoperable with Sun
  Management Center 3.6.1.

- The PrimeAlert Agent for Windows is now compatible with Microsoft
  Windows XP and Windows Server 2003.

- The EventLogAlert module now supports monitoring additional Windows
  event logs.  The Hardware Events and Forwarded Events logs that were
  added in Windows Server 2003 R2 can now be monitored.

- The PrimeAlert Agent for Windows now supports a 16 character Super
  User seed.  SunMC 3.6 and above allow the use of 16 character seeds.

- The ProcessAlert and WinSystemAlert modules have bee renamed to
  ProcessMonitor and WinSystemMonitor.


UPGRADE STRATEGY:
----------------------------------------------------------------------

- When upgrading from version 5.1.1b of the Windows Agent use the
  following steps:

  1) Stop the previous verion of the PrimeAlert Windows Agent
     by executing the following on the command line:

     > net stop "Halcyon PrimeAlert Agent"

  2) Uninstall the previous version of the PrimeAlert Windows Agent

  3) Install the current version of the PrimeAlert Windows Agent.
     See the README.install file for more details.

  4) Any custom alarm limits set in the Physical Disks and Logical
     Disks section of the PrimeAlert SystemMonitor module will
     have to be re-entered as they will be lost.


KNOWN PROBLEMS:
----------------------------------------------------------------------

- During installation of the PrimeAlert Agent for Windows, the user can
  select which user will run the Halcyon PrimeAlert Agent service. The
  'Select User' button does not work properly when a non-default user
  is desired.

- [LogFileAlert] If a file is scanned using the full scan mode, the
  file is only re-scanned when the file's size or modification time are
  changed; the file should actually be re-scanned periodically
  regardless of whether or not the size or modification time have
  changed.

- [LogFileAlert] If a pattern regular expression contains round
  brackets, (), an incomplete matching line may be displayed.


======================================================================
VERSION/DATE: 5.1.1b/2005-11-28


UPDATES:

- Added Solaris 10 support.
- Tested against Sun MC 3.6


UPGRADE STRATEGY:

- This version is compatible with the previous version.  No changes
  have been made to the Windows agent software.  The Solaris packaging
  has been modified to allow installation on Solaris 10.

  We recommend that you uninstall the 5.1.1a Solaris components before
  upgrading your OS, and re-install with this 5.1.1b release afterwards.
  Remember to re-apply any manual patches you have received from Halcyon.

  If you have any patches or manual procedures that you used with
  the 5.1.1a Windows agent, you should also install/undertake
  them with the 5.1.1b Windows agent.

KNOWN PROBLEMS:

- Same as prior version (5.1.1/5.1.1a).


-----------------------------------------------------------------------
VERSION/DATE: 5.1.1a/2003-07-23


ENHANCEMENTS:

- Added Solaris 9 support.

- Interoperable with Sun MC 3.5


UPGRADE STRATEGY:

- This version is compatible with the previous version.  To upgrade to 
  this release from the previous version, only the Server Layer 
  components need to be upgraded.  There is no need to upgrade the 
  agents.


-----------------------------------------------------------------------
VERSION/DATE: 5.1.1/2001-01-22

BUG FIXES:

- The Solaris packages for the PrimeAlert Agent and its bundled modules
  can now be installed when the SunMC 2.1.x/3.0 packages are installed 
  in a non-default location.

- For Windows agent hosts, the host pop-up menu in the SunMC console
  now has an Alarm Action entry.

- Under Windows 2000, the reported physical memory for machines with
  greater than 2 GB of memory is now correct.

- A new SunMC 2.1.1 console feature, 'enhanced tables', has been
  disabled, since SunMC 2.1.1 does not support this feature for modules
  that have multiple instances (see the Sun Management Center 2.1.1
  Software Release Notes - Bug ID 4302619).

- [SystemAlert] An empty Threads value in the Object Information table
  no longer causes a data update error.

- [EventLogAlert] Instances of EventLogAlert no longer disappear from
  the SunMC console after the Halcyon PrimeAlert Agent service is
  restarted.

ENHANCEMENTS:

- The PrimeAlert Agent for Windows is now interoperable with Sun
  Management Center 3.0.

- The PrimeAlert Agent for Windows is now compatible with Microsoft
  Windows 2000.

- The InstallShield installer for Windows now allows a user to specify
  a non-default public user seed.

- The agent is now called the 'PrimeAlert Agent for Windows'.

- As documented in the README.txt file for this distribution, all text
  documentation files for this distribution are now archived to a
  standard location on any installation host.

- This distribution includes a new UNIX uninstallation script; see
  the INSTALL.txt file for details.

KNOWN PROBLEMS:

- Assume that a user installs Sun Management Center in the /opt
  directory, and then decides to relocate some of the installed
  directories (located below /var/opt/SUNWsymon or below
  /opt/SUNWsymon) after SunMC is installed. For example, assume that
  the directory /opt/SUNWsymon/modules is moved to /export1/SUNWsymon,
  and then a symbolic link is created to link /opt/SUNWsymon/modules to
  /export1/SUNWsymon/modules. In this case, if the current distribution
  attempts to install any files in or below the directory
  /opt/SUNWsymon/modules, the symbolic link will be replaced by a real
  directory. This problem does not occur under Solaris 2.5.1.

- Under certain circumstances, when a module's demo license expires,
  the module is no longer accessible from the SunMC console window, and
  newly loaded instances of the same module are also not accessible
  from the console. To make the module accessible again, load an
  instance of a different module (that has a valid license) on the
  agent.

- During installation of the PrimeAlert Agent for Windows, the user can
  select which user will run the Halcyon PrimeAlert Agent service. The
  'Select User' button does not work properly when a non-default user
  is desired.

- [LogFileAlert] If a file is scanned using the full scan mode, the
  file is only re-scanned when the file's size or modification time are
  changed; the file should actually be re-scanned periodically
  regardless of whether or not the size or modification time have
  changed.

- [LogFileAlert] If a pattern regular expression contains round
  brackets, (), an incomplete matching line may be displayed.

- [SystemAlert] For PrimeAlert SystemAlert, within the Disk Information
  folder, the Reads/s and Writes/s columns of the Physical Disks table
  do not provide correct data for a Windows 2000 host.

UPGRADE STRATEGY:

- This version of the PrimeAlert Agent for Windows no longer supports
  Sun Enterprise SyMON 2.0.x; only Sun Management Center 2.1 or higher
  is supported.

- This version of the PrimeAlert Agent for Windows only works with the
  following versions of these unbundled modules:

    - PrimeAlert for Microsoft SQL Server 1.0.3 or higher
    - PrimeAlert ScriptRunner 1.0.5 or higher

- If you are upgrading a Windows host (agent layer) from PrimeAlert
  Agent for Windows version 5.0 to 5.1.1, all current configuration
  information for the local agent will be lost, unless certain files
  are manually copied to the new agent directory tree after the
  upgrade; see the INSTALL.txt file for details.

- In order to obtain the full benefit of the new features included in
  this version of the PrimeAlert Agent for Windows, PrimeAlert Agent
  for Windows packages should be upgraded for all SunMC/PrimeAlert
  layers (server, agent, and console).

- PrimeAlert Agent for Windows packages on the SunMC server host should
  be upgraded first. Then, PrimeAlert agent hosts can be upgraded
  according to any user defined schedule. Note that after the server
  host is upgraded, the PrimeAlert Agent for Windows should continue to
  operate properly for all agent hosts, regardless of the version of
  the PrimeAlert Agent for Windows that is installed on an agent host.
  Finally, after all server and agent hosts have been upgraded, the
  console hosts should be upgraded to ensure that the module help
  documentation is up-to-date.

- CAVEAT: After the server host has been upgraded, agent hosts that
  contain older versions of the PrimeAlert Agent for Windows may not
  have all of the functionality of the newest agent until the agent
  hosts have also been upgraded to the same level as the server host.