Altiris™ Monitor Solution 7.0 SP5 from Symantec Release Notes

Article:DOC2183  |  Created: 2010-06-30  |  Updated: 2010-10-14  |  Article URL http://www.symantec.com/docs/DOC2183
Article Type
Documentation


Description



Build number: 7.0.8641

Monitor Solution helps you ensure your server and network up-time and availability and ultimately reduce the costs of network management in your organization.
You can do the following with Monitor Solution:

  • Identify the health of your environment by collecting detailed data from servers, applications, and network devices.
  • Analyze trends and isolate recurring issues by collecting comprehensive real-time and historical performance data.
  • Pinpoint problems, define their cause, and take automated actions to resolve them.

See the following sections for information about this release:

Back to top

New features

The following are features of this release:

Back to top

 

Supported client operating systems

This section lists the client computer operating systems that are supported by Monitor Solution.

  • AIX IBM Advanced Interactive eXecutive 5.2, 5.3, and 6.1
  • HP-UX Hewlett Packard UniX 11i v1 (PA-RISC)
  • HP-UX Hewlett Packard UniX 11i v2 and v3 (IA64 and PA-RISC)
  • Microsoft Windows Server 2003 (32- and 64-bit) -excludes Microsoft Windows Server 2003 R2
  • Microsoft Windows Server 2008 (32- and 64-bit)
  • Microsoft Windows Server 2008 R2 (32- and 64-bit)
  • Microsoft Windows Server 2008 Core Edition (32-bit)
  • Microsoft Windows Server 2008 R2 Core Edition (32-bit)
  • Red Hat Enterprise Linux 4 (32- and 64-bit)
  • Red Hat Enterprise Linux 5 (32- and 64-bit)
  • Red Hat Enterprise Linux 5.1 (32- and 64-bit)
  • Red Hat Enterprise Linux 5.2 and 5.3 (32- and 64-bit)
  • Red Hat Enterprise Linux 5.4 (32- and 64-bit)
  • Solaris 9 on SPARC
  • Solaris 10 on SPARC and x86
  • SUSE Linux Enterprise Server 10 (32- and 64-bit)
  • SUSE Linux Enterprise Server 11 (32- and 64-bit)
  • VMware ESX 3.0.1, 3.0.2, 3.5

Back to top

Upgrade issues

 

The following are issues and things to know about upgrading Monitor Solution 7.0.

Issue Article ID Internal ID

Agent update issue

The updated agent is not automatically pushed out after installing Service Pack 4. To deploy the updated agent:

  1. In the Symantec Management Platform console, select Settings > Agents/Plug-ins > Altiris Agent.
  2. Right-click, and then click Export.
  3. In the left pane, select Altiris Agent > Windows > Altiris Agent for Windows - ba and enable the policy.
    (It will take some time for the agent to be pushed out to all targeted computers.)
   

Issues when upgrading from previous 7.0 versions (SP1 and SP2) to the final release version

The following issues contained in this table cell are only applicable when upgrading from previous 7.0 versions. These issues do not apply to upgrades from 6.x versions.

  • Customizations made to Monitor Server Settings and the Remote Monitor Server Settings are not preserved

After upgrading you must update Monitor Server Purging Maintenance Settings and Remote Monitor Settings. These settings are not migrated.

  • You can export custom policy and agent settings before upgrading

Some items may be lost when upgrading from 7.0 release candidate versions. It is possible to preserve custom items (including monitor policies, server settings, and Remote Monitoring Server settings). Export custom items to XML files before installing the 7.0 SP5 release. Then import the .XML files following the installation.

To restore console elements, you import them from the appropriate .XML files. Console elements are identified by their GUIDs. Elements in the imported .XML file overwrite existing elements that have a matching GUID. Any elements in the .XML file that do not have matching GUIDs in the console are added as new items.

Note: You need the Import XML privilege to import .XML files. By default, only the Notification Server administrator role has this privilege.

Note: This functionality is only supported for 7.x to 7.x upgrades. This task is not supported when migrating from Monitor Solution 6.x to Monitor Solution 7.x.

To save a console element as an .XML file:

  1. In the left pane, click the tree node that you want to save.
  2. Right-click, and then click Export.
  3. In the Destination File for Exported XML dialog box, specify the XML file name and location, and then click Save.

To restore a console element from an .XML file:

  1. In the left pane, select the folder to which you want to restore the element.
  2. Right-click, and then click Import.
  3. In the Choose the XML File to Import dialog box, select the appropriate XML file.
  4. If you want to prevent any changes from being made to the imported element, check Open as read-only.
  5. Click Open.
  • Run once ASAP requires manual modification of Agent Upgrade package to work

 This issue only occurs in the following scenario:

 

  • You migrated from a Monitor 7.0 Release Candidate version to the Monitor 7.0 Final version.
  • You uninstalled the Monitor Solution 7.0 Release Candidate version, then you installed the Monitor Solution 7.0 Final version, and then you reconfigured the database.
  • You installed a Monitor Solution 7.0 Release Candidate version of the Monitor Agent, and you clicked the Run once asap option in the rollout policy.

For agents to be installed using the "Run Once ASAP" feature, you must manually modify the agent package. This notifies the Altiris Agent that a newer version of the Monitor Agent package is available.

To workaround this issue by manually modifying Monitor Agent Packages:

  1. On the Notification Server computer, navigate to the directory where the package is located:
    C:\Program Files\Altiris\Notification Server\NSCap\bin\Win32\X86
    C:\Program Files\Altiris\Notification Server\NSCap\bin\Win64\x64
    C:\Program Files\Altiris\Notification Server\NSCap\Bin\Unix\Monitor\Linux
  2. Create a blank .txt file in the folder.
  3. Update the package's distribution points.
  4. Enable the upgrade policy.

 

 

1777516 

1777940

An import of 6.x items after an import of 7.0 items always overwrites

Following installation of Monitor Solution 7.0, if you first import 6.x monitor data and then you import a 7.0 Monitor Pack, then you have the option to enable or disable the overwrite existing items option.

However, if you first import a 7.0 Monitor Pack and then import 6.x monitor data, you do not have the option to enable or disable, and 7.0 Monitor items are automatically overwritten with 6.x.

Therefore, we recommend that when migrating from 6.x to 7.0, following the installation of Monitor Solution 7.0, first import your 6.x data and then import 7.0 Monitor Packs. You then have the flexibility to choose if you want to overwrite the existing items.

  1777937

Referenced items are migrated

When migrating Monitor Solution 6.x items to Monitor Solution 7.0, modified items (such as policies, metrics, rules, and new monitor packs) are all migrated. If an item has not been modified, but the item is referenced by another item that has been modified, then the referenced item is also migrated.

For example, if you modified a rule, but not a metric that the rule references, then both the metric and the rule are migrated.

  1777401
1777436

Monitor Server Purging Maintenance Settings are not migrated

Monitor Server Purging Maintenance Settings are not migrated from versions 6.x to version 7.0.

  1777516

Custom collections associated with custom Monitor packs are not updated

43769  

Issues with migrating Monitor tasks/actions from 6.x to 7.0

The Generate SNMP Trap task and the Create Incident task are not imported from 6.x to 7.0 because they are not supported on version 7.0.

The Generate NT Event task is supported on version 7.0; however, settings made to this task are not preserved. Settings made to previously created Generate NT Event tasks are moved to the parameters field on 7.0. The following data appears: Altiris Monitor Solution for Event Source, 1 for Category, and 1000 for Event ID.

  1777804

Known Issue when Upgrading Windows Monitor Agents

When a Windows Monitor Agent is upgraded, it may be possible that the file that the Monitor Agent uses to write to the system event log is in use by Windows. If this occurs, then the file will not be upgraded until the next restart. The new file will be placed in the Monitor Agent's directory and will have a temporary (.tmp) file name. The operating system will not be automatically restarted, but Windows may prompt the user that a restart is necessary. If upgrading from BEIM to DMC, the agent upgrade will not be complete until a restart has occurred.

  1778015

Issues with upgrading Agents when Notification Server is a new computer

When upgrading to a new Notification Server computer, there are issues with agent communications. After completing a data import, upgrading the Altiris Agent on client computers is unavailable. Although the 6.x client computers are displayed in the filter (Windows/Linux computers requiring Altiris Agent Upgrade), when the upgrade policy is applied, the upgrade fails.

The issues occur because the previous version of the Altiris Agent attempts to connect to the previous 6.x Notification Server computer instead of the new 7.0 Notification Server computer. Therefore, the 6.x agent is unaware that an upgrade policy to the 7.0 version is made available.

To workaround this issue you must manually redirect the 6.x agent to communicate with the new 7.0 Notification Server computer before you migrate to version 7.0:

  1. In the Altiris 6.x Console, on the Configuration tab, click Roll out Altiris Agent > Roll out Altiris Agent Configuration.
  2. In all the required policies (for example, All Desktop Computers, All Package Servers, All Unix Computers, etc.) on the Advanced Settings tab, enable the check box for Specify an alternate URL for the Altiris Agent to use to access the Notification Server.
  3. Specify the server name and the URL of the new 7.0 Notification Server computer.
  4. Refresh the Agent configuration on the client computers.
  5. Upgrade to version 7.0.
  1777531

SQL metrics do not upgrade properly after performing an upgrade from MS 6.0 SP5

If in Monitor Solution 6.0 SP5 you set custom credentials for "SQL Authentication" or "Windows Authentication" and also selected the "Use Multiple instances" check box, then after migrating to Monitor Solution 7.0, the associated SQL metrics do not work. The reason for this is:

  • After migration, custom credentials are encrypted and cannot be used. You must manually reapply the appropriate credentials.
  • After migration, the "Use Multiple instances" check box is not selected. You must manually reselect this option to restore your previous settings.
  1778954

The "SNMP," "Performance Counter," and "SQL" metrics are not correctly migrated from Monitor Solution 6.0 into Monitor Solution 7.0 SP2

If in Monitor Solution 6.0 you enabled "Use Multiple Instance" for "SNMP," "Performance Counter," or "SQL" metrics, then after migrating these metrics into Monitor Solution 7.0 SP2, they will be disabled.

  1779060

Monitor Agent service stops after upgrading the Symantec Management Agent

The Monitor Agent service stops if you upgrade the Symantec Management Agent. To resolve this issue you must manually start the Monitor Agent service. The service will also automatically start if you upgrade the Monitor Agent.

  1779008

Back to top

Fixed issues

The following are previous issues that were fixed in this release. If additional information about an issue is available, click the Article ID link.

Issue Article ID Internal ID

All resource types were displayed in the Computer List drop-down list when creating an agentless monitor policy

When building a custom target for an agentless monitor policy, when the drop-down list (Computer list) was selected, additional resources that were not computers were also displayed.

   1778312

Monitor Agent crashed on computer with two network adapters

On a computer that has two network adapters and the “Network bandwidth % Utilization” policy enabled, the Monitor Agent crashed when one of the network adapters was disabled and then enabled.

   1883573 

The value returned for Hop Count was always “-1”

After creating a metric to collect “Hop Count”, the value returned was always “-1”.

   1944967

Historical Viewer Process information was not clear for CPU Time and did not show CPU usage

Historical Viewer Process information showed only CPU Time and the value was not clear.  It now shows CPU Time in hh:mm:ss and also includes CPU Usage as an additional column.

   1923940

"Rebooted By Root" rule on Linux was not always triggered

Alert often did not appear in Event Console after "Rebooted by root" rule was triggered on Linux servers. As a result administrator did not get information about server reboot as expected.

   1946822

MonitorMetricData Table received only partial data update 

When you run Monitor Solution with Dell policies for 12-24 hours, the amount of data in the MonitorMetricData table did not reflect the amount of data that had been gathered. 

   1958831

Targets for UNIX, Linux, Solaris, and ESX cause web error when viewing Monitor policies as restricted user

When viewing the ESX, Linux, and Solaris Monitor policies while logged into the Symantec Management Console as a user who is a member of a custom Security Role, an aspx web error occurred.

   1978725 

Monitor Agent crashed on some Windows computers

In some environments, the Monitor Agent crashed on some Windows computers and did not restart on its own.

   1978767 

AeXMetricProv.exe consumed excessive amounts of memory on some x64 machines

AeXMetricProv.exe could consume 500 MB of memory or more on some Windows x64 machines.

   1981452

AeXMetricProv.exe consumed high CPU on Domain Controllers with very busy NT Event logs

On Domain Controllers, AeXMetricProv.exe sometimes consumed around 50% CPU usage if they had NT Event Logs with thousands of events per minute. Metric provider had a difficult time keeping up with reading all the events which occurred because of memory leaks.

   1998414

Targets for UNIX, Linux, Solaris, and ESX cause web error when viewing Monitor policies as restricted user

When viewing the ESX, Linux, and Solaris Monitor policies while logged into the Symantec Management Console as a user who is a member of a custom Security Role, an aspx web error occurred.

   1978725

Legacy agent-based alerts weren't active in the Event Console

After an upgrade a legacy alert should have been auto-resolved in the Event Console, but instead of auto resolving the legacy alert remained unchanged and a new normal alert appeared in the Event Console.

   2012875 

Rate based rule alerts displayed the Rate value instead of the metric value

An alert raised from a rule which references "Rate" condition displayed the metric value in a rate format instead of the actual metric's value. The metric value is now displayed. 

   2013257 

Errors in average calculations with Historical Performance Viewer

After selecting time period in Historical Performance Viewer, "Metrics" section provides Min, Max and Avg metric's value for the period. The Avg is calculated as simple average, without taking duration of the metrics into account. It now uses a weighted average value that takes into account the duration field.

   2016616 

"OK" button was missing for metric selection in Historical Performance Viewer for restricted user

If a restricted user attempted to view metric data in the Historical Performance Viewer, the "OK" button could be missing from the "Available Metrics..." window. This occurred if the Security Role which the user is a member of did not have "Monitor Solution UI Write Access" privileges enabled.
 

   2030710 

Heartbeat alerts occurred during system shut down when they should not have occurred

During a purposeful system shutdown, a Heartbeat alert was raised for that computer although an alert should not be raised during a legitimate shut down.

   2038008 

Ping metric entered "Retry" for most resources

When a custom Ping Rule was created that used a custom Ping metric, the metric entered “Retry” for most resources. 

   2039288 

During upgrade Monitor Agent was not installed on Solaris 10 X86_64 computer

During upgrade from Monitor Solution 7.0 SP3 to Monitor Solution 7.0 SP4 HF1, the Monitor Agent did not get upgraded on a Solaris 10 x86_64 computer. The agent accepted the rollout policy, uninstalled the previous version of the UNIX, Linux, Mac agent, and finished, but did not install the new version. 

   2046800 

Monitor Agent leaked memory on a Linux computer

The Monitor Agent leaked memory on Linux computers with glibc version 2.3.4-2.13 and 2.3.4-2.19.

    2064360

Sporadic 2 hour gaps in historical data for some computers

On some computers, there are intermittent sporadic 2 hour gaps in the historical data. 

   2064387

A network port scan caused monitoring to stop on Linux Servers

If you performed a network port scan of Linux Servers that had the Monitor agent installed, metric provider crashed and monitoring stopped on these servers.

   2064390 

Monitor Agent PULL installation failed on the Solaris platform with BASH

The Monitor Agent PULL installation failed on the Solaris platform when BASH is a default shell for root.

   1778648

Changes made to default configuration policies were lost after reconfiguration to a backup SQL database

During reconfiguration of Symantec Management Platform 7.0 using a backup SQL database (Symantec_CMDB), changes made to some Monitor Solution core settings (agent settings and RMS settings) were overwritten with default values when the database was restored. This only affected changes made to default configuration policies and not custom policies.

   1778562

Monitor Agent doesn't install on x64 clients with 32-bit Symantec Management Agent

If you forced the installation of the 32-bit Symantec management Agent on 64-bit computer, then the installation of Monitor Agent failed.

   2078400

Back to top

Things to know

The following are things to know about in this release. If additional information about an issue is available, click the Article ID link.

Things to know Article ID Internal ID

Monitor Solution 7.0 cannot be hosted on a Windows Server 2008

Currently, the Symantec Management Platform, which Monitor Solution is installed on, does not yet support Windows Server 2008 as a host; this support will be added in a future release.

   

The Monitor Agent plug-in supports Windows 64-bit platforms

The Monitor Agent includes 64-bit support for both Windows 2003 and Windows 2008 as a managed device.

   

You may need to install sysstat on your monitored Linux computers

You must install sysstat on your targeted Linux computers to use the following monitor policies:

  • Processor
  • Disk I/O
  • Memory
   

If you install the Remote Monitoring Server on a dedicated computer, the PPA agent and the Credential Manager are required

If you install the Remote Monitoring Server on a dedicated computer, the PPA agent and the Credential Manager are required.

  1777765

Network Discovery found devices may not be listed in the targeted filters of the default agentless policy

Agentless monitor policies target filters of computers and devices. By default, the target only included unmanaged devices running Windows 2003 or 2008. When computers are discovered, the local operating system is a property of that computer resource. If during discovery, a computer's operating system cannot be determined, an operating system specific filter will not recognize that computer.

This is a possible cause if an agentless monitor policy is not running on a computer as expected.
Note: The operating system version is correctly discovered for target computers that have SNMP enabled.

  1777857 

Activated Monitor Policies web part only shows policies that the Monitor Agent has activated

A Monitor Agent must first activate a monitor policy before it is displayed in the Activated Monitor Policies web part of the Monitoring and Alerting home page. If you have enabled a monitor policy but it is not yet displayed in the web part, this may be because the web part is populated from inventory data that is received from the agent.

  1777861

Purging Log Event and Sys Log data

Both Log Event and Sys Log data purging is controlled with the single String metric data purging schedule.
To schedule string metric data purging:

  1. In the Symantec Management Console, on the Home menu, click Monitoring and Alerting.
  2. In the left pane, click Monitoring and Alerting > Monitor > Settings > Monitor Server Settings.
  3. On the Monitor Server Settings page, click the Purge Maintenance tab.
  4. Under Non-numeric Data, set the value for String metric data.
  5. On the Monitor Server Settings page, click Save changes.
  1775418

The Poll Metric on Demand task cannot poll agent-based metrics on a computer that does not have the Monitor Agent

The Poll Metric on Demand task can poll two different types of metrics: agent-based and agentless. It is supported on two different types of targets: with and without Monitor Agent.

If the Poll Metric on Demand Task is executed on an agentless target (the client computer without the Monitor Agent installed on it), then it can only poll agentless metrics on the client computer. Agent-based metrics are not polled on an agentless client computer as agent-based metrics require the Monitor Agent to run.

  1777999

A failed heartbeat may not raise an alert if the Check for heartbeats interval is less than the Send Heartbeat interval with zero retry attempts

If you configure the Monitor Server Setting's > Heartbeat tab's > Retry attempts value to "0" and the Check for heartbeats every interval to be less than or equal to the Monitor Agent Configuration Setting's Send heartbeat every interval, then a failed heartbeat may not raise an alert in the Event Console due to network latency. In this case, a Monitor Agent may appear to occasionally go down only to come right back up again. However, the uptime data will not be affected in this case.

  1777840

There are time drifting issues when monitoring heartbeats on Linux computers that are hosted on VMware

When monitoring heartbeats on Linux computers that are hosted on VMware, there are issues with time drifting.
This issue can cause heartbeats to be received by Notification Server after a very long delay and an alert to be raised in the Event Console.
To avoid issues with unnecessary alerts in the Event Console, make sure that your heartbeat time settings are synchronized to account for possible time drifting.

  1778513

HTTP metrics do not support virtual hosts

The HTTP metric cannot be used with virtual hosting. The HTTP metric only supports the use of the current hostname of a physical computer that reports basic inventory to the Notification Server computer.

43762  1775767

There is a specific setup required to enable Smart Metrics using SNMP

To enable Smart Metrics using SNMP:

  • The SNMP service must be installed on the monitored computer.
  • The community name must be configured in the SNMP service on the monitored computer. The community name must match the community string in the SNMP protocol settings for your connection profile.
  • SNMP packets must be accepted from any host in the SNMP properties on the monitored computer.
  1776096

If two WMI metrics are configured to parse the same command output and they both have different polling intervals, these metrics will read data with the lowest polling interval. The WMI metrics combine into a similar query for optimization. The query runs at the lowest interval setting.

  1772183

When "Altiris" log type is selected, the Log Event metric only supports Windows platforms

When the "Altiris" log type is selected, the Log Event metric uses the Notification Server log file as source. This type of log is supported for Windows platforms only.

  1776924

The reports "Alert History" and "Most Active Hosts" are located in the Event Console Reports folder

The 6.x reports:

  • Alert History by Monitor Agent
  • Alerts Over Last 'N' Days
  • Monitor Agents with Most Alerts

Are now replaced with:

  • Alert History
  • Most Active Hosts

These reports are located under the Event Console Reports folder on the Monitoring and Alerting portal page.

  1777050

There is a delay in the Computers Lists for the Real-time and Historical Performance Viewers

Computers are not populated in the Computers List for the Historical and Performance Viewers until data is received from the target computer by Notification Server.

  1777061

Metrics do not work if Credential Manager is installed by pull to Remote Monitor Server

Some metrics do not work if Credential Manager is installed by a pull to the Remote Monitor Server. If Credential Manager is pushed to the Remote Monitor Server, there are no problems.

   

The repeat count feature specifies the number of times the rule must trigger in a row before an action is taken

After the repeat count specified in a rule has been reached, the rule resets to "normal" on the next value, even if that value crosses the threshold. If the value crosses the threshold, the rule restarts the repeat count for the next evaluation.

Example:

Rule count definition - if CPU > 10 for 3 times

If the values are 11, 12 , 13, 11, the rule will trigger on the third value and then reset to normal on the fourth value. The fourth value then becomes the first increment for the next check.

  1776239

Agentless monitoring uses Pluggable Protocol Architecture (PPA) connection profiles

The Remote Monitoring Server (RMS) agent leverages PPA to make connections to monitored remote resources to obtain metric data. PPA references the Connection Profiles used during Network Discovery. The Network Discovery Connection Profiles define which protocols are enabled and any applicable credentials and settings for each protocol.

When the RMS agent attempts to monitor an agentless resource, it queries the database and uses the connection profile that was used during Network Discovery. If the RMS agent cannot find a reference to a connection profile, the Default Connection Profile is used. To select a different connection profile, run a new Network Discovery and select the desired connection profile for remote resources.

  1850105

Timed rules are no longer supported

Timed rules are no longer supported in Monitor Solution. You can now use the heartbeat feature and Task Server instead.

   1778762

How WMI Metric handles WMI property arrays

In some cases WMI property values are stored as arrays of values. In this case, each property in the array is represented as a different instance\value pair for the metric. The name for instance will be "Name of the instance (n)" where n is the index. For example if % Disk Space had multiple properties for disk space:
"C: (1)" = 23, "C: (2)" = 43, "D: (1)" = 54, "D: (2)" = 7

   

Back to top

Known issues

The following are known issues for this release.If additional information about an issue is available, click the Article ID link.

Known Issues Article ID Internal ID

Issues with agentless monitoring

  • If you first discover a computer, and then change either its computer name or its IP address, then attempting to monitor that device will fail.
  • It is possible that an agentless monitoring policy will not stop monitoring, even after the policy is disabled.
  • The Remote Monitoring Server cannot be installed on 64-bit platforms; therefore, agentless monitoring cannot be performed from a 64-bit computer.
  • In the Event Console, the Remote Monitoring Server will be shown as the source of an alert, even if the alert is raised by a monitored agentless resource.
  • The monitored computer must be specifically set-up to enable SNMP agentless metrics:
    • The SNMP service must be installed on the monitored computer.
    • The community name must be configured in the SNMP service on the monitored computer. The community name should match the community string in the connection profile SNMP protocol settings. (From the Symantec Management Console, click Settings > All Settings > Solution Settings > Protocol Management > Manage Connection Profiles).
    • The monitored computer's SNMP properties must be configured to accept SNMP packets from any host.

 

 

Unmanaged computers are not applied to agentless monitor policies when using filters

If a discovered computer is unmanaged (does not have the Altiris Agent installed), then it cannot be applied to agentless monitor policies with a filter. There is an issue that prevents the unmanaged computers from being targeted correctly, even if the computer is discovered and is contained in a filter.

To apply unmanaged computers to agentless monitor policies, you must manually add the computers using the resource selector. Managed computers are unaffected and can be added to agentless monitor policies using the filter.

  1777487

Agentless monitoring is not available for targets that have been discovered through an Active Directory Import

You cannot apply agentless monitor policies to targets that have been discovered through an Active Directory Import. To work around this issue, use a Network Discovery or a WINS import instead of an Active Directory Import.

  1777769

When the Remote Monitoring Server computer’s password is about to expire, agentless monitoring is unavailable

When a Remote Monitoring Server computer has either of the following:

  • A password has expired or is within 14 days of expiration
  • The option for a user to change the password on first start has been enabled

Then the PPA agent/plug-in is unable to connect through WMI. In this case, the Remote Monitoring Server is then unavailable because the Remote Monitoring Server depends on the PPA agent/plug-in for communications.
To work around this issue you must ensure that the Remote Monitoring Server computer’s password does not come within 14 days of expiration. If the password does expire, then resetting the password resolves the issue until the next time the password comes within 14 days of expiration.
As a possible means of prevention, you can set the Remote Monitoring Server computer’s Windows password to never expire.

  1778033

Known Issue when Exporting a monitor pack to Windows Vista and Windows Server 2008 when IE Protected Mode is On

When all of the following are true:

  • You are exporting a monitor pack to a Windows Vista or a Windows Server 2008 computer
  • Internet Explorer protected mode is set to ON
  • The Symantec Management Console is open

Then the monitor pack's .XML file is copied to the \temp\ folder instead of the intended path. In this case, completing the import process from this location would fail. You must copy the .XML file manually to the correct location first.

  1774708

The Process Control task only supports 32-bit systems

At this time, Monitor Solution 7.0 does not support the controlling of 64-bit Windows processes.

   

Agentless Smart WMI Metrics do not work on Windows 2000 Server target computers

Agentless Smart WMI Metrics do not work on Windows 2000 Server target computers.

   

Log Event metric supports ANSI-only

The Log Event metric supports ANSI-only log files. When parsing, the Log Event metric assumes a Windows Latin-1 encoding.

If characters that require UTF-8 encoding (for example, when using non-English languages) are contained within either a Log Event metric or within the log, then the metric fails.

  1776492

The Log Event metric fails to open client side Altiris log files

The Log Event metric is only capable of parsing Notification Server’s a.log file and, therefore, can only monitor the local Notification Server computer’s log. The Log Event Metric fails to open Altiris log files on remote client computers that contain the Monitor Agent.

  1776511

ASP.NET metric enters retry state when ASP.NET is installed but not registered

This issue occurs when ASP.NET is installed but not registered. To work around the issue, register ASP.NET by running the following command on the target computer:

aspnet_regiis.exe -i

   

Known Issues with reports

  • Reports are run first using default parameters. To receive reports with adjusted parameters, wait until the default parameter graph is displayed, change the parameters, and then run the report again.
  • After drilling down into a report's details, you cannot change parameters and see new graph results. To return to the initial view of the report, right-click the report in the left pane, and click Open.

 

 

A Monitor Solution report’s customized view is not preserved after the report refreshes

After customizing the view of a Monitor Solution report, once the report is refreshed the customizations to the view are lost and the default view is displayed.

  1776999

Agent uptime via Heartbeat report not reporting the correct uptime percentage after crash

For the "Agent uptime via Heartbeat" reports to accurately reflect uptime, the Monitor Agent service must be started again after a critical system crash. If the agent is not started again, this period will be erroneously reported as uptime instead of downtime. If you receive an alert that an agent heartbeat has failed, make sure that there is connectivity from the Altiris Agent to Notification Server, and make sure that the Monitor Agent service is running on the monitored computer.

  1778045

Issues with IIS Memory Performance Report

When viewing the IIS Memory Performance report, some metrics are not displayed, and an exception is logged in the NS log.

The following metrics are not displayed:

  • Internet Information Services Global - File Cache Flushes (Avg)
  • Internet Information Services Global - File Cache Flushes (Max)
  • Internet Information Services Global - File Cache Hits % (Avg)
  • Internet Information Services Global - File Cache Hits % (Max)
  • Page Reads per Second (Avg)
  • Page Reads per Second (Max)

To work around this issue, either view these metrics in the Table View of the report or view them from within the Historical Performance Viewer.

   

Issues with Disk Paging Activity Report

The Disk Paging Activity report displays incomplete data when it is viewed in the Chart View.
To work around this issue and view all data values, use the Grid View to display this report.

   

You must reconnect the Real-time Performance Viewer if metric data becomes unavailable

When using the Real-time Performance Viewer, if a metric becomes unavailable and then becomes available again, updated data is not displayed. The viewer continues to display the data value that was last received before the metric became unavailable. The Real-time Performance Viewer must be re-connected to the target computer before updated data is reflected in the viewer.

  1777708

When using the Historical Performance Viewer, the value displayed at the mouse pointer may not update

This issue is known to occur when the chart area of the Historical Performance Viewer does not have the current cursor focus, for example when the "refresh" button has been clicked. To work around this issue, click the mouse cursor within the chart, and then hover the mouse cursor over the desired data point.

  1776753

Limited monitoring of ESX Servers

Monitoring of ESX Servers is limited when using the WS-MAN Agentless metric because of limitations in Pluggable Protocol Architecture (PPA)

Only the CIMV2 namespace can be used for monitoring ESX servers. The following vendor namespaces are not currently supported:

  • OMC=http://schema.omc-project.org/wbem/wscim/l/cim-schema/2
  • VMware=http://schemas.vmware.com/wbem/wscin/l/cim-schema/2
  • PRS

 This issue is caused by limitations of PPA. Only namespaces defined in the PPA repository can be used.

  1836738

Performance issues with a resource target that is running Windows Server 2003

If a resource target is running Windows Server 2003 and has the Monitor Agent installed, the resource target runs slowly.

   1850535

Event Console purges all events during purging maintenance

During purging maintenance, Event Console purges all alerts including active events.

   1852012

Issues with “UNIX and Linux servers requiring Monitor Agent upgrade” filter

Error occurs when attempting to open the "UNIX and Linux servers requiring Monitor Agent upgrade” filter.

   1859383
 

Custom filters do not update if applied to an agentless based Monitor policy

If a custom filter is applied to an agentless based Monitor policy, the filter does not update when the asset status of a resource changes.

   1916834

Power Monitoring stops working after 4 weeks

After 4 weeks, Power Monitoring does not correctly report the state of the servers it is monitoring.  

   1956540

Error with Historical Performance Viewer

When viewing Historical Performance Viewer from a workstation, the following error occurs: "There was an error in the callback." When viewing historical data for the same computer directly from the Notification Server, the following error occurs: "column 'instancekey' is constrained to be unique. value '13932' is already present". 

   1982867

Monitor Agent can crash on service stop/restart when NT Event Log monitoring is performed

When large amount of NT events are parsed by metric provider, the Monitor Agent can crash on service stop/restart and create gaps of monitored data in Historical Performance Viewer.

   2059336

Metric provider does not properly parse NT events on Windows 2008 SP1 Server

Metric provider does not properly parse description of NT events according to configured NT Event Rule.

   2059665
 

App detector does not run on a scheduled interval

On a Linux server, when app detector is not able to pass any detection method due to a locked RPM database, all packs are set to inactive state and the monitor agent will not invoke app detector again until it receives a new configuration.

   2061301

Percent Disk Utilization metric returns incorrect values

Percent Disk Utilization metric is returning incorrect values causing
incorrect rule trigger.

   2070138

Symantec Management Agent log does not contain monitor's messages

By default, Monitor Agent does not log warning and error messages to the Symantec Management Agent log.

   2078770

Actual state of a device and the state reflected in the console are sometimes out of sync

When monitoring 500 or more devices using agentless monitoring, the state of the actual device and the state reflected in the console are sometimes out of sync. The actual device might be in a critical state and the console would indicate that it is in a normal state. 

   2085502
 

Windows Service metric based rule always reverts to "Is not equal to" with query type of "Installed"

A rule which references a Windows Service metric that has a query type of
"Installed" always reverts to a condition of "Is not equal to". If you modify the rule's condition to "Equal to installed", save it, then modify it again, it reverts back to "Is not equal to installed". 

   2087925

Metric provider crashes on AIX computers

Metric provider crashes on AIX computers and leaves a core dump error of "SOFTWARE PROGRAM ABNORMALLY TERMINATED". The Monitor Agent then restarts on its own after a period of time.  

   2091762

Command metric with incorrect command specified never gets into Retry/Unavailable mode

A Command metric never gets into Retry/Unavailable mode if an incorrect command is specified. This metric is also shown as available in Real-
time Viewer and always return 0. 

   2120363

Cannot open the "Monitor Table Space Used by Monitored Resources" report

After monitoring a group of computers for a period of time, you cannot open the "Monitor Table Space Used by Monitored Resources" report. When you try to open the report, a timeout error message appears.

   2122275

Incorrect heartbeat alert behavior on a Virutal Machine

A heartbeat alert may be raised in Event Console from a monitored resource, which runs on Virtual Machine, even if it is online and metric provider is running. This incorrect behavior is caused becase of a known issue with VMware virtual machines. The following link describes this issue and how to resolve this problem:  http://www.vmware.com/pdf/vmware_timekeeping.pdf

   

1982360

A single ping rule in two different agentless Monitor policies only works in the first policy

If two different agentless Monitor policies contain the same ping rule, only the first occurrence of the rule will trigger and generate alerts.

   2136417

A second Monitor Solution is created when you upgrade to Monitor Solution 7.0 SP5

If you have an off-box Remote Montioring Server and you upgrade to Monitor Solution 7.0 SP5, a second Monitor Service is created on the Notification Server. To resolve this issue after the upgrade, do the following:

1. In the Symantec Management Console, on the Settings menu, click Notification Server > Site Server Settings.
2. In the left pane, under Site Management, click Site Servers > Notification Server.
3. In the right pane, in the Monitor Service section, click Install/remove services.
4. In the Add/Remove Services dialog box, uncheck Monitor Service.
5. You must then manually install the SP5 version of the PPA Agent on the Remote Monitoring Server where the SP4 version of the PPA Agent is installed.

After you install the SP5 version of the PPA Agent SP5 on the remote server, the PPA inventory is sent to the Notification Server and the upgraded off-box Remote Monitoring Server will be shown as correctly installed on the Site Management Page.

   2131401

Unable to manually resolve agent-based legacy alerts in Event Console after upgrade from 7.0 SP4 HF1

After you upgrade from 7.0 SP4 HF1, legacy alerts that were raised from agent-based resources could not be properly resolved from the Event Console when using manual resolve. This issue doesn't affect agentless alerts or alerts resolved by a metric value change.

The workaround is to reset all agent-based monitored resources after the server and clients are upgraded to the 7.0 SP5 version.
To reset the agent-based monitored resources, create a new "Reset Monitored Resource" task. Add a rule to the target that excludes resources that are not in the filter "Computers with Monitor Agent installed." The task will then not target Remote Monitoring Servers so agentless alerts will not be reset. After you run the task, all agent-based alerts will be resolved both in Event Console and on the client, and you will be able to  resolve new alerts that are raised raised in the Event Console.

   

 

Back to top

 

 


Legacy ID



53583


Article URL http://www.symantec.com/docs/DOC2183


Terms of use for this information are found in Legal Notices