Monitor Solution 6.x Release Notes

Article:HOWTO4603  |  Created: 2006-08-10  |  Updated: 2008-06-19  |  Article URL
Article Type
How To

What do I need to know about the 6.x release of Monitor Solution?


Monitor Solution 6.x

Release Notes


Installation and Upgrade

Monitor Solution Core New Features

Known Issues

Additional Documentation

Document History


Altiris® Monitor Solution™ software is a single solution consisting of a group of components that monitor computers and applications. Metrics are used to collect data from providers of data, called metric providers. Rules evaluate this data and determine if corrective actions need to be taken. By continuously monitoring computers and applications, corrective actions can be taken when necessary. Availability and uptime are increased, which improves performance and reduces costs.

This document provides the What’s New and Known Issues information for Altiris Monitor Solution products, including:

Monitor Solution core components
Monitor Solution for Servers, including monitor packs to support Windows, UNIX, and Linux
Monitor Solution for Altiris Infrastructure
Monitor Solution for Microsoft SQL Server
Monitor Solution for Microsoft Exchange Server

Installation and Upgrade


Core components:

  • Notification Server 6.0 SP3 (or later). For general information about Notification Server and requirements, see the Altiris Notification Server Help.
  • If you want to send SNMP traps as a rule action, you must install the Altiris SNMP Component from the Solution Center. If you installed Monitor Solution from the Solution Center, the component should already be installed.

Where to Download

If you have not previously installed Notification Server along with any solution, each Monitor Solution product can be downloaded and installed from<. If you have previously installed a solution and Notification Server, you can install a Monitor Solution product from the Solution Center.

Upgrading from an Earlier Version of Monitor Solution 6.x

If you are running an earlier version of Monitor Solution 6.x (example: Monitor Solution 6.0) and want to upgrade to a newer version of Monitor Solution 6.x (example: Monitor Solution 6.0 SP1), do the following:

  1. In the Altiris Console, click the Configuration tab.
  2. In the right pane, click Configuration > Upgrade/Install Additional Software.
  3. In the content pane, click the Available Solutions tab. If you use the Currently Installed tab instead, the reports associated with the solution will not be automatically installed.
  4. Click the Solutions button.
  5. Find the Monitor Solution you want to update in the list, and click the solution name. The table indicates the current version of each solution available and the version of the solution installed on the Notification Server, where applicable.
  6. Follow the steps in the console to install the update.
  7. In the left pane, select Configuration > Solution Settings > Monitoring > Monitor Solution > operating system > operating system Monitor Agent Rollout > operating system Monitor Agent Upgrade, where operating system is the name of the operating system. 
  8. In the content pane, select the Enable check box if it is not already selected. This policy allows any upgrades to the Monitor Agent to be installed on the monitored computer.

If you are upgrading from 6.0, 6.0 SP1, or 6.0 SP2, the new agent will use the configuration settings from the previous agent and not the default settings for the new agent.

If you want to use the new agent default settings, complete the following steps to create a new agent configuration policy with the new default settings:

  1. In the Altiris Console, click the Configuration tab.
  2. In the left pane, select Configuration > Solution Settings > Monitoring > Monitor Solution > operating system > operating system Agent Configuration.
  3. Right-click operating system Agent Configuration, and select New > Agent Settings.

This creates a new configuration policy that uses the default settings. You will need to enable this policy and disable the old policy.

In 6.0 SP2, some default Agent Settings (Data Collection tab) were changed to use less space in the Notification Database. Record metric values every was changed from 60 to 120 seconds, Record process values every was changed from 60 to 120 seconds, and Close logs every was changed from 15 to 60 minutes.

Upgrading from the Beta Version of Monitor Solution for Microsoft Exchange Server 6.0

If you are upgrading from the beta version of Monitor Solution 6.0 for Microsoft Exchange Server to the release version, you must use Add or Remove programs to uninstall Altiris Monitor Packs for Exchange 6.0.

Monitor Solution Core New Features

Improvements for this release include the following new features:

Feature Description

Monitor Solution Core Components 6.0 SP5 Features

1. Remote access from Vista computers

You can access Monitor Solution remotely from a Vista computer using Internet Explorer 7.

2. Monitor Solution portal page with graphical displays of data

The portal page lists:

  • Status of computers
  • Most recent events
  • Monitored computers by operating system 
  • All monitored computers 

3. New system requirements

This version of Monitor Solution requires Notification Server 6.0 SP3 and Altiris Console 6.5.

Monitor Solution Core Components 6.0 SP4 Features

1.      Monitor Agent’s memory usage streamlined

In previous releases, memory usage would grow on Windows servers whenever the Monitor Agent was processing large volumes of Windows events. This no longer occurs.

2.      New ability to create collection-specific dashboards

Now you can create a dashboard specifically for a collection by cloning the existing dashboard and applying it to a different collection.

3.      Computer name included in SNMP traps generated from the Monitor Agent

Now SNMP traps contain the name and IP address of the computer from where the rule generating the trap triggered.

4.      Support for Microsoft’s Internet Explorer ActiveX fix

This version supports Microsoft’s fix to the ActiveX controls for Internet Explorer 6 on Microsoft Windows XP Service Pack 2 and on Microsoft Windows Server 2003 Service Pack 1. For details about this fix, go to and review knowledge-base article 912945.

5.      Cross-server reporting

You may now choose multiple servers to appear in any single report.

Monitor Solution Core Components 6.0 SP3 Features

1. Enhanced Monitor Agent SQL metric type authentication options

Two changes have been made to enhance the Monitor Agent authentication. Previously, if you chose to authenticate using Windows authentication, the Windows account used by the Monitor Agent service was used to authenticate against the SQL database. Now, you can specify the account and password to use, which provides greater flexibility. Also, a new authentication option has been added: NS Database Settings. This option lets the agent authenticate against the SQL database using the Notification Server authentication settings.

2.      Purging Triggered Rules occurs by default

The Purging Triggered Rules Information option is now enabled by default in Monitor Solution. This ensures that tables storing information about triggered rules do not grow too large and consume an excess amount of resources.

This option is only available if you install Monitor Solution 6.0 SP3 on Notification Server 6.0 SP2. If you install it on Notification Server 6.0 SP3, then Notification Server’s purging mechanism hides this option and purges triggered-rules information. Check Notification Server’s settings to confirm that Monitor Solution will keep data long enough for your needs.

3.      MonitorProcessLog is cleared on upgrade but the data is still available

Upgrading Monitor Solution clears the data in Notification Server’s MonitorProcessLog. You still have access to data about processes run before the upgrade, however. If you generate a report in Monitor Solution that displays data on processes run before the upgrade, that data is decompressed from AeXSMPerfLog and written to MonitorProcessLog.

4.      Performance Monitor’s new process for connecting to monitored servers

Performance Monitor now attempts to connect to all IP addresses a monitored server has until it successfully connects to the server.

Monitor Solution Core Components 6.0 SP2

1.      Microsoft SQL Server metric type

The SQL Server metric has been added, which allows Microsoft SQL Server to function as a metric provider.

2.      Enhanced Triggered Rules page

The Triggered Rules page, accessed from the Monitor Solution dashboard, has additional functionality that allows you to acknowledge triggered rules, close associated Alert Manager/Helpdesk incidents, and access and edit the triggered rules.

3.      SNMP metric is now available for Linux and UNIX

SNMP metric providers are now supported in Linux and Sun Solaris.

4.      Support for custom Web reports 

In previous versions of Monitor Solution, the creation of custom reports was undocumented. In this version, new tables of data have been added to the Notification Database for creating Monitor Solution related reports and the creation of these reports is documented. The three new tables contain uncompressed event, process, and metric data.

5.      Reports and Performance Monitor now support multiple instance metrics

Previously, reports and Performance Monitor did not support multiple instance metrics. Now, they are supported.

6.      Dashboard lets you specify which collection of computers to monitor

Previously, the Monitor Solution dashboard monitored all computers with the Monitor Agent installed on them. Now, you can select whether to monitor all computers with the agent installed or a subset of the computers by selecting the collection of computers the dashboard monitors.

7.      Metric name is now shown in the Performance Monitor graph

If you place the mouse pointer over a point on a graph line in Performance Monitor, the coordinates of that point along with the name of the metric will be displayed next to the mouse pointer.

8.      Reset the state of a computer and the triggered rules

We added the ability to reset a monitored computer and the triggered rules associated with the computer back to a Normal state from the Monitor Solution dashboard and Triggered Rules page.

9.      Default Monitor Agent configuration settings have changed

Default Monitor Agent configuration settings have been changed so less space is used in the Notification Database. Data collection intervals ("Record metric values every" and "Record process values every") were changed from 60 to 300 seconds.

10.      The NT Events collected can be specified

In 6.0 SP1, all NT Events were collected into the AeXSMPerfLog table for use in Performance Monitor and only those NT Events that triggered rules were logged to the Filtered Events table for use in reports. This has been modified to let you control which NT Events to collect and to save space in the Notification Database. The functionality remained the same for the Filtered Events table. But the handling of NT Events was moved to the monitored computer; you can collect not only NT Events that trigger rules but also ones that just match conditions in rules. So, you can configure which events to collect for Performance Monitor display and the “List of NT Events by Computer for Last 'N' Days” report, which displays all NT Events (other reports display only NT Events from Filtered Events).

Monitor Solution Core Components 6.0 SP1

1.      Rule actions can be based on rule triggering frequency

Rules can now be configured to perform automated actions based on the frequency of the rule being triggered. You can configure the number of times a rule must be triggered (Repeat count field) within a certain time period (Time period field) before action is taken. For example, a rule must be triggered 5 times within 60 minutes for the rule action to occur.

2.      Triggered and non-reset rules can be viewed through the Monitor dashboard

The Monitor dashboard provides a list of rules that have been triggered and NOT reset on a computer. This allows you to easily identify and deal with potential problems that have not be addressed, without needing to see a list of all triggered rules, as Resource Manager shows.

3.      Multiple attempts are now made to access a metric

If a metric is unavailable, Monitor Solution will now make additional attempts to check for the availability of the metric or confirm that the metric is still unavailable. Retry information is available in the AeX Monitor Agent table on the Events tab of Resource Manager.

4.      Support for Monitor Agent upgrading

Monitor Solution now supports the ability to automatically upgrade the Windows Monitor Agent. When a new version of Monitor Solution is installed, the new version can include a new Monitor Agent. This new agent needs to be deployed from the Notification Server computer to the monitored computers. This is done by enabling the policy that controls this feature.

To enable this feature, in the Altiris Console, click the Configuration tab. In the left pane, select Configuration > Solution Settings > Monitoring > Monitor Solution > Windows > Windows Monitor Agent Rollout > Windows Monitor Agent Upgrade.

5.      Monitor Agent sends overall status on startup

Each time the Monitor Agent starts, the agent will now locally determine its status and send it to the Notification Server. This ensures that the Notification Server has the correct status of each agent.

6.      Monitor Agent for Linux

Monitor Agent is now available for Linux (Red Hat).

Monitor Solution Core Components 6.0

Major changes have been made to Monitor Solution since 5.6, including major changes to the interface, additional metrics, additional platforms, and additional available solutions.

1.      New interface

Monitor Solution uses the newly redesigned Notification Server 6 interface, which groups interface elements by function and provides role and scope-based security. Monitor Solution metric and rule related pages have also been redesigned to be more intuitive and easier to use.

2.      Added SNMP, log event, and command metric

Monitor Solution has added support for three new metrics: SNMP, log event, and command.

The SNMP metric is implemented as a management application that polls attribute values from SNMP-enabled agents.

The log event metric lets you monitor log events. For the most common log types and formats, the necessary configuration is already done. For example, there is no special configuration necessary to collect data from a Microsoft IIS web log. If your log type or format is not predefined, you can specify the configuration settings.

The command metric lets you parse the results of a command-line utility or an input file for a particular value, and return associated values. For example, you can use this metric to run a command-line utility that lists the names of the files in a specific location on a hard drive along with the creation date of the file. This list can be parsed for the presence of a specific file name. If the file name is found, the creation date of the file is returned. This can be used to ensure that the proper version of an application is being used.

3.      Agent profiling

Agent profiling is a rule triggering mechanism that lets a rule be triggered based on statistical criteria. Monitor Solution compares a current metric value with the average of previous values for the same metric and determines if the current value is within a user specified number of standard deviations from the average value for the metric. If the value is outside of the range, the rule is triggered.

Agent profiling lets Monitor Solution automatically and dynamically determine which metric values are acceptable and trigger a rule if necessary. As metric values change over time, the triggering range is automatically adjusted, which helps prevent a rule from being triggered unnecessarily and reduces the need to manually adjust the rule. This automatic adjustment also minimizes the need for manual adjustments across different computer hardware and software.

4.      Rules can be triggered based on non-constant values

A rule can be triggered on a metric value instead of just a constant. The supported metrics are command, custom COM, custom DLL, Performance Counter, SNMP, and WMI.

5.      Monitor packs for Notification Server and Package Server

Solutions are now available for monitoring Altiris Notification Servers and Altiris Package Servers.

6.      Reduced memory usage by Monitor Agent

The Monitor Agent now uses less memory on the monitored computer.

Monitor Solution for Servers New Features

Improvements for this release include the following new features:

Feature Description

Monitor Solution for Servers 6.0 SP5

1. Support for additional versions of Unix/Linux 

  • SUSE Linux Enterprise Server 9, 10 
  • AIX 5.1, 5.2, 5.3 
  • HP-UX 11, 11i, 11i v2, (IA64)

 2. New metrics

We added the following metrics to the Linux pack:

Processor I/O Wait Time%
Processor I/O Wait Time% (per processor)

  3. Removed metrics 

We removed the following metrics from the Solaris and Linux packs:

Disk sec/Transfer Linux
Disk Average Sec/Transfer Solaris
Process Physical Memory Usage (Kb) (bash) Solaris
Process Physical Memory Usage% (bash) Solaris
Process CPU Usage% (bash) Solaris
Process Virtual Memory Usage (Kb) (bash) Solaris
Process Page File (Kb) (bash) Solaris
Process Physical Memory Usage (Kb) (bash) Linux
Process Physical Memory Usage% (bash) Linux
Process CPU Usage% (bash) Linux
Process Virtual Memory Usage (Kb) (bash) Linux
Process Page File (Kb) (bash) Linux

 4. Metrics changed

The "Process Instance Count (bash) Solaris" and "Process Instance Count (bash) Linux" metrics have been changed to find all well known shells. The name of metrics have changed to "Process Instance Count (shell) Solaris" and "Process Instance Count (shell) Linux."

Monitor Solution for Servers 6.0 SP4

1.      Automatic OMSA detection when installing the Monitor Agent for UNIX and Linux

Now the Monitor Agent for UNIX and Linux detects whether or not Dell OpenManage Server Administrator (OMSA) is installed.

Monitor Solution for Servers 6.0 SP3

1.      Support for Red Hat in Monitor Agent

Now Monitor Agent for UNIX and Linux collects data from x86 computers running Red Hat 9, Red Hat Enterprise Linux 3.0 and 4.0 (Intel only), and Red Hat Linux AS 3.0. These operating systems must be running on an x86 computer in order for the agents to collect data from them.

2.      Support for Novell SUSE in Monitor Agent

Now Monitor Agent for UNIX and Linux collects data from computers running Novell SUSE 8.0, 8.1, 8.2, 9.0, and Novell SUSE SLES 8. These operating systems must be running on an x86 computer for the agents to collect data from them.

3.      General Compatibility with Notification Server

You must install Monitor Solution for Servers 6.0 SP2 and SP3 on Notification Server 6.0 SP2 or later.

4.      Monitor Agent’s dependence on Altiris Agent in UNIX and Linux environments

If you use Monitor Agent for UNIX and Linux, you must be running Altiris Agent for UNIX and Linux 6.1 or later.

5.      Agent configuration update file transferable from secure environments

Now you can download the agent configuration update file (config.xml) from secure environments using HTTPS protocol.

6.      Streamlined Monitor Agent

Monitor Agent has been optimized to use less resources on monitored computers.

Monitor Solution for Servers 6.0 SP2

1.      Added support for monitoring Sun Solaris servers

Monitor Solution for UNIX and Linux now supports Sun Solaris 7, 8, and 9 running on Sparc processors.

Known Issues

The following are unresolved issues and workaround instructions for issues in this release:

Known Issue Article ID
SQL Server 2000 connection leak with "localhost" specified as database instance

For SQL Server 2000, when "localhost" is specified as the database instance in the agent settings or SQL Metric settings, and the SQL Server that is being monitored has multiple instances of SQL Server installed on the monitored computer, then SQL Metrics will fail to connect to the database and connections will be left open when the SQL Metric tries to connect, causing a connection leak. The desired SQL Server instance needs to be explicitly specified in the "Server Name" field of the agent settings or SQL Metric settings.
SQL Server metrics don't work with named instances

If you have a named instance of SQL Server, you must specify the full server\instance name in each of the Performance Counter metrics. In the Altiris Console 6.5, select Manage > Monitoring > Tasks > Manage Metrics. Select Performance Counter for Metric Type.

Performance data from Monitor Solution 5.6 displays with incorrect time

Performance data collected using Monitor Solution 5.6 and imported into Monitor Solution 6.0 displays with the incorrect time in Performance Monitor. The problem is due to the 5.6 Monitor Agent storing data in local computer time and the 6.0 Performance Monitor expecting UNC time.

Uninstalling Monitor Solution from Notification Server 6.0

Uninstalling Monitor Solution 6.0 or 6.0 SP1 through the Solution Center is not supported with Notification Server 6.0; it is supported with Notification Server 6.0 SP1. 

Computer name filtering in reports

With the Monitor Solution reports in the "Monitor Agents," "Monitor Rules and Metrics," and "Monitor Alerts" groups, if you set any filtering using the Collection and Domain filters, any computer with the Monitor Agent installed is still listed in the Computer Name field; no filtering of the names occurs.

Retrieval and processing of binary data by the SQL metric is not supported

The Monitor Agent can only retrieve text or numeric data. If you attempt to retrieve binary data (example: columns with data types Binary, Varbinary, TimeStamp, and Image) for the "value column" field in the user interface, the actual data is replaced by the plain string value “[Binary Data]” by the agent. If the "instance column" field in the interface specifies a column that returns binary data, the instance name can be shown as unintelligible data in Performance Monitor.

Log metric can miss log entries that appear while the MetricProvider service is stopped

The log event metric can miss entries in a log that appear in the log when the MetricProvider service is stopped. This is due to a race condition that takes place during Monitor Solution startup, which causes some metric data to be lost.

"Disk Write Kb per Second" and "Disk Read Kb per Second" metrics do not work on some Linux systems

The “iostat” utility from the sysstat package version 4.0.1 does not provide read kB/s or write kB/s data, so the "Disk Read Kb Per Second Linux" and "Disk Write Kb Per Second Linux" metrics do not work. To resolve the problem, install sysstat package version 4.0.3 or later.

No resource available for selection when starting Performance Monitor

On the Launch Performance Monitor page, if you click the “Click to select” link and no resources are listed, you need to install the core set of Monitor Solution reports (Altiris_ReportCoreMonitor_6_0.exe). This only occurs if you are manually upgrading to Monitor Solution 6.0 SP2 and have not installed the core set of reports. Reports are installed automatically when you upgrade using the Solution Center within the Altiris Console.

Metric not listed in the Performance Monitor and Resource Manager retry table

If a metric is unable to read the specified data, the metric might not be listed in the registered metrics list for Performance Monitor and also not listed in the Resource Manager list as a metric in retry state (but it should be).

This problem occurs with command metrics. Metrics are set to retry state based on the execution result of its command line, but sometimes a command is executed properly but the metric is unable to get all needed data from the command. There are metrics that execute the same command but just use different data from the command output, so the command can execute properly and its output can be correct for all metrics that use it, except one that requires some additional data (for example, data from an additional output column that is available only on specific systems or with newer version of the executed application). In this case, this metric will not be set to retry state (because its command worked properly) but won't be shown in Performance Monitor (because it was not able to retrieve the needed data).

Network bandwidth metrics do not work on Linux systems

On some Linux systems the "Network Current Bandwidth Bytes/sec" and "Network Bandwidth Utilization Linux" metrics might not work if the "ethtool" utility is missing from the system. Also, we recommend installing the latest version of the ethtool utility to support Red Hat Linux systems previous to 8.0 because the version of the ethtool utility provided with Red Hat 7.2, 7.3, and Advanced Server 2.1 is outdated and does not work with modern network cards.

“Unable to connect to database” error when opening SQL query builder

If Notification Server is using different authentication information to access SQL Server than specified from the Monitor Solution Agent Configuration page, you will get an "Unable to connect to database..." message when you try to open the SQL builder page, which is accessed from the SQL metric configuration page. Make sure the same authentication information is used in both places.

UNIX command metrics not working properly with Monitor Agent for UNIX and Linux 6.0 SP1

Most of the UNIX Monitor Solution command metrics have been modified in Monitor Solution 6.0 SP2 to allow them to work on non-English operating systems. These modified metrics are not compatible with the 6.0 SP1 version of the Monitor Agent for UNIX and Linux. After you install Monitor Solution Core 6.0 SP2 or SP3, most of the UNIX metrics will be unavailable until you upgrade to Monitor Agent for UNIX and Linux 6.0 SP2 or later.

Numerous error messages can result from using Monitor Agent for UNIX and Linux 6.0 SP1

Numerous error messages can be added to the Notification Server log if you upgrade Monitor Solution to 6.0 SP2 or 6.0 SP3, but some Monitor Agents for UNIX and Linux 6.0 SP1 are still installed and sending data to the Notification Server. These agents can send date information in a format that is not recognized by the new solution and result in errors. The problem is fixed by installing the 6.0 SP2 or SP3 agent.

Rules with a changed configuration are not correctly represented when triggered with the 6.0 SP1 Monitor Agent

If a rule was triggered by Monitor Solution 6.0 SP1 and the rule configuration was changed (example: in Monitor Solution 6.0 SP2, several predefined rules changed acknowledgement type from "Incident acknowledgement" to "self-resetting"), the acknowledgement of the rule does not remove its entry from the Triggered Rules page after upgrading to Monitor Solution to 6.0 SP2 or 6.0 SP3. After you upgrade the Monitor Agent and the updated rule is triggered and acknowledged, the rule will then be removed from the Triggered Rules page.

Normal state rules triggered and unacknowledged in 6.0 SP1 no longer appear in the Triggered Rules page after upgrading to 6.0 SP2 or 6.0 SP3

If a Normal (not Warning or Critical) state rule is triggered and not acknowledged when running Monitor Solution 6.0 SP1, the rule will not appear in the Triggered Rules page after upgrading to Monitor Solution 6.0 SP2 or 6.0 SP3.


Use single quote to enclose UNIX command lines that include a semicolon or pipeline

On UNIX platforms, if the command line contains semicolons or pipelines, the command must be enclosed within single quotes and be run as a shell command line (example: sh -c 'command line' or - bash -c 'command line'). Example: sh –c ‘ps –ef | grep bash | awk ‘{print $1}’’. If you prefer some other shell (not sh or bash), be sure that you use correct syntax to launch the command line.

Acknowledgement type rules triggered in previous versions cannot be acknowledged from the Triggered Rules page

Acknowledgement type rules triggered in previous Monitor Solution versions are shown without a corresponding Helpdesk/Alert Manager incident number in the Triggered Rules page after upgrading Monitor Solution, since this information was not stored before 6.0 SP2. Acknowledgement from the Triggered Rules page is not available for these rules, and they should be reset through the corresponding incidents in Helpdesk/Alert Manager.

“Agent error: The specified request to the Altiris Monitor Agent timed out. Please verify that the agent version supports this request.”

If you attempt to use the Reset Agent feature, available from the Monitor Solution dashboard and the Triggered Rules page, on a monitored computer that is running the Monitor Agent, which has not been upgraded to the 6.0 SP2 or 6.0 SP3 version, you will get this error: “Agent error: The specified request to the Altiris Monitor Agent timed out. Please verify that the agent version supports this request.” To use this feature, you must upgrade to the 6.0 SP2 or 6.0 SP3 Monitor Agent.

Monitor Solution Web service problem during upgrading

If the Monitor Solution Web service is in use during an upgrade, an Altiris Monitor Solution retry dialog opens. Click Retry to continue with the upgrade without problems. This situation commonly occurs if Performance Monitor is open during the upgrade. Closing Performance Monitor before upgrading minimizes this occurrence.

Uninstalling Monitor Solution using the preserve collected data option

When you uninstall Monitor Solution, a dialog gives you the option to preserve collected data for upgrading purposes. If you choose to preserve data, the data pointing to the uninstalled Monitor Solution items remains in the Notification Database, which can cause problems with other Altiris solutions. To minimize the chance for problems, promptly reinstall Monitor Solution.

List of NT Events by Computer for Last 'N' Days report

The "List of NT Events by Computer for Last 'N' Days" report does not show duplicate events. If several absolutely identical events were logged at the same time, only one instance of the event will be shown in a given report.

Notification Server and monitored computer clocks must be in sync

Ensure that the Notification Server clock and the monitored computer clocks are in sync before doing a system reset. If the clocks are not in sync, this can result in triggered rules that do not change Agent status. If the monitored computer time is ahead of the Notification Server time, rules might not successfully reset.

Monitor Agent for UNIX and Linux 6.0 SP3 - Standard distributions of the SUSE 8.x don't include "sysstat" package

The SUSE 8.x standard distributives don’t include the “sysstat” package, which contains the “sar” and “iostat” utilities. In order to obtain all metrics using Monitor Agent for UNIX and Linux, you must have the “sysstat” package installed on the same computer running the agent. This package can be installed separately as an update for SUSE 8.x, which you can download from the Internet.

Monitor Agent for UNIX and Linux 6.0 SP3 – Restart agent after Apache’s log changes location

If Apache’s log changes location while using Monitor Agent for UNIX and Linux, Apache’s log metrics continue to report the last string of the old log file until you restart Monitor Agent for UNIX and Linux.

SQL Metrics with incorrect SQL queries still attempt to retrieve data and return nulls

If the SQL query provided in a SQL metric’s configuration is incorrect, the metric still attempts to retrieve data and return nulls.

Drilling down into Monitor Solution’s performance-metric reports on Notification Server 6.0 SP3

If you’re running Monitor Solution with Notification Server 6.0 SP3 and you drill down into a performance-metric report enough to open Performance Monitor in historical mode, Performance Monitor displays an “Incorrect start time” error. You can get Performance Monitor to start normally by closing it and drilling down into the report once more.

Upgrading to SP3 reverts SQL-metrics connection settings to default Notification Server database settings

If you created any SQL metrics in Monitor Solution 6.0 Service Pack 2 and then upgrade the software to SP3, any custom credentials set for the SQL metrics are lost. Notification Server database settings are used instead. To use custom credentials, you’ll need to set them once more in both the metric’s authentication settings and in the Monitor Agent for Windows Configuration settings.

Setting intervals

Make sure to set the "Close logs every" and “Upload logs every” intervals higher than the “Record metric values every” and “Record process values every” intervals. If you set the log intervals too low, the affected metric logs might not get stored in the Notification Server database as performance BLOBs (binary large objects).

Data for cross-server reports

Only data stored in uncompressed performance-data tables is available to cross-server reports. You can control the amount of data stored in the uncompressed performance-data tables by modifying the Delete uncompressed performance data older than setting on the Monitor Purging Maintenance page.
As in previous versions of the software, if only one server is selected—and if the time requested is beyond the available data in the uncompressed performance-data tables—then data is extracted from the compressed performance-data tables into the uncompressed performance-data tables.

 Custom DLL metric on UNIX and Linux

When using the custom DLL metric on UNIX and Linux with the gcc compiler, link it with the -Bsymbolic flag. Linux Example:
gcc -fPIC -shared -Wl,-Bsymbolic dlltest.o -o


Setting "postfix" as an SMTP server

Some SMTP server metrics won't return information if "postfix" is set as an SMTP server. This is because the "postfix" package doesn't include a utility to return usage information (like "mailstat" in "sendmail" package does, for example).

Exporting Monitor Packs to Windows Vista computers

When exporting a Monitor Pack to a Windows Vista computer with IE Protected Mode is set to ON and the Altiris Console open, the Monitor Pack's XML file is copied to the \temp\ folder instead of the intended path. Completing the import process from this location would fail. You need to copy the XML file manually to the correct location first.

 Shell scripts inside the "Process is Running" detection method

In some cases, shell scripts can't be detected when they're running within the "Process is Running" detection method. This is because "UNIX95=true ps -e -o comm" is used to detect the list of running processes. In that case, the shell interpreter is listed as the process name of the shell script executed.


 "Network Current Bandwidth Bytes/sec Linux" metric and SLES on VMware

The metric "Network Current Bandwidth Bytes/sec Linux" might not report information on SLES 9 & 10 installed on VMware virtual machines.
This happens because the "ethtool" utility might not always report the network adapter speed on such machines.
More information on this issues can be found at:


Installing Monitor Packs on computers running SQL Server 2005 

If, after installing on a computer using SQL Server 2005, the Monitor Packs do not show up in the Manage Monitor Packs task, do the following to correct the problem:

  1. Make sure SQL Server Management Studio's Login dialog box is closed.
  2. Uninstall the Monitor Packs.
  3. Reinstall the Monitor Packs.
 Upgrading to SP5

After upgrading Monitor Solution from SP2 or SP4 to SP5, any Solaris reports saved or scheduled using the earlier version are deleted.


Additional Documentation

Altiris product documentation is available in Microsoft* HTML Help (.CHM) and Adobe* Acrobat (.PDF) formats. To view Altiris product documentation in .PDF format, use Adobe Acrobat Reader (available at:

Documentation files are installed in the following directory on the Notification Server computer:
C:\Program Files\Altiris\eXpress\Notification Server\NSCap\Help.

The following documentation is provided with Monitor Solution 6.x:

monitor.chm - Product Guide
monitor.pdf - Product Guide

You can access documentation from the Altiris Console by clicking the following icons in the upper-right corner of the console:

 Access the contextual online help by clicking the online help icon.
 Access an index of all installed help by clicking the index icon.

Altiris Information Resources

Source What Information it Includes Where to Find it
Altiris Documentation Information about new features, update instructions, and known issues for each release. Includes Altiris formal documentation such as release notes, help, reference guides, best-practice articles, and technical reference Articles.
Altiris Knowledgebase Comprehensive collection of articles, incidents, and issues for Altiris solutions.
Altiris Juice:
an online magazine for Altiris users
Best Practices, tips and tricks, and articles for users of Altiris solutions.
Online Forums Forums for Altiris solutions and suites.

Document History

 Date  Changes
10/20/2006 Updated with information about Monitor Solution for Microsoft Exchange Server 6.0.
4/3/2007 Updated with information for Monitor Solution for Servers 6.0 SP5.

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices