Build number: 7.0.7416.0
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:
See the following sections for information about this release:
The following are features of this release:
Added support for Microsoft Internet Explorer 8. The Symantec Management Platform and Monitor Solution for Servers can run from Internet Explorer 8.
The WS-MAN metric uses the Web Services for Management (WS-Management) specification to poll data for metrics.
This section lists the client computer operating systems that are supported by Monitor Solution.
The following are issues and things to know about upgrading Monitor Solution 7.0.
Issue | Article ID | Internal ID |
Agent update issue
|
||
Issues when upgrading from previous 7.0 versions (SP1 and SP2) to the final release version
|
102363 102758 |
|
An import of 6.x items after an import of 7.0 items always overwrites
|
102756 | |
Referenced items are migrated
|
102233 102282 |
|
Monitor Server Purging Maintenance Settings are not migrated
|
102363 | |
Custom collections associated with custom Monitor packs are not updated |
43769 | |
Issues with migrating Monitor tasks/actions from 6.x to 7.0
|
102640 | |
Known Issue when Upgrading Windows Monitor Agents
|
102823 | |
Issues with upgrading Agents when Notification Server is a new computer
|
102377 102795 |
|
SQL metrics do not upgrade properly after performing an upgrade from MS 6.0 SP5If in Monitor Solution 6.0 SP5 you set custom credentials for "SQL Authentication" or "Windows Authentication" and also selected the "Use Multiple instances" checkbox, then after migrating to Monitor Solution 7.0, the associated SQL metrics do not work. The reason for this is: 1. After migration, custom credentials are encrypted and cannot be used. You must manually reapply the appropriate credentials. 2. After migration, the "Use Multiple instances" checkbox is not selected. You must manually reselect this option to restore your previous settings. |
104136 | |
The "SNMP," "Performance Counter," and "SQL" metrics are not correctly migrated from Monitor Solution 6.0 into Monitor Solution 7.0 SP2
|
104301 | |
Monitor Agent service stops after upgrading the Altiris AgentThe Monitor Agent service is stopped if you upgrade the Altiris 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. |
104221 |
The following are things to know about in this release.
Things to know | Article ID | Internal ID |
Monitor Solution 7.0 cannot be hosted on a Windows Server 2008
|
||
The Monitor Agent plug-in supports Windows 64-bit platforms
|
||
You may need to install sysstat on your monitored Linux computers
|
102733 | |
If you install the Remote Monitoring Server on a dedicated computer, the PPA agent and the Credential Manager are required
|
102601 | |
Network Discovery found devices may not be listed in the targeted filters of the default agentless policy
|
102685 | |
Activated Monitor Policies web part only shows policies that the Monitor Agent has activated
|
102692 | |
Purging Log Event and Sys Log data
|
15117 | |
The Poll Metric on Demand task cannot poll agent-based metrics on a computer that does not have the Monitor Agent
|
102809 | |
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
|
102671 | |
There are time drifting issues when monitoring heartbeats on Linux computers that are hosted on VMware
|
103524 | |
HTTP metrics do not support virtual hosts
|
43762 | 100496 |
There is a specific setup required to enable Smart Metrics using SNMP
|
100808 | |
|
10401 | |
When "Altiris" log type is selected, the Log Event metric only supports Windows platforms
|
101685 | |
The reports "Alert History" and "Most Active Hosts" are located in the Event Console Reports folder
|
101828 | |
There is a delay in the Computers Lists for the Real-time and Historical Performance Viewers
|
101834 | |
Metrics do not work if Credential Manager is installed by pull to Remote Monitor Server
|
||
The repeat count feature specifies the number of times the rule must trigger in a row before an action is taken
|
1776239 | |
Agentless monitoring uses Pluggable Protocol Architecture (PPA) connection profiles
|
1850105 |
The following are unresolved issues in this release.
Known Issues | Article ID | Internal ID |
Issues with agentless monitoring
|
||
Unmanaged computers are not applied to agentless monitor policies when using filters
|
102332 | |
Agentless monitoring is not available for targets that have been discovered through an Active Directory Import
|
102605 | |
All resource types are displayed in the Computer List drop-down list when you are creating an agentless monitor policy
|
103186 | |
When the Remote Monitoring Server computer’s password is about to expire, agentless monitoring is unavailable
|
102843 | |
Known Issue when Exporting a monitor pack to Windows Vista and Windows Server 2008 when IE Protected Mode is On
|
14577 | |
The Process Control task only supports 32-bit systems
|
||
Agentless Smart WMI Metrics do not work on Windows 2000 Server target computers
|
101848 | |
Log Event metric supports ANSI-only
|
101202 | |
The Log Event metric fails to open client side Altiris log files
|
101224 | |
ASP.NET metric enters retry state when ASP.NET is installed but not registered
|
102091 | |
Known Issues with reports
|
||
A Monitor Solution report’s customized view is not preserved after the report refreshes
|
101766 | |
Agent uptime via Heartbeat report not reporting the correct uptime percentage after crash
|
102858 | |
Issues with IIS Memory Performance Report
|
103476 | |
Issues with Disk Paging Activity Report
|
103495 | |
You must reconnect the Real-time Performance Viewer if metric data becomes unavailable
|
102541 | |
When using the Historical Performance Viewer, the value displayed at the mouse pointer may not update
|
101488 | |
Monitor Agent PULL installation fails on the Solaris platform with BASH
|
103745 | |
How WMI Metric handles WMI property arrays
|
||
Timed rules are no longer supported
|
103912 | |
Changes made to default configuration policies are lost after reconfiguration to a backup SQL database
|
1778562 | |
Limited monitoring of ESX Servers
|
1836738 | |
Issues with upgrading the monitor agent
|
1884392 | |
Unnecessary Monitor Agent Upgrade rollout
|
1950897 | |
Duplicate Monitor plug-in upgrade policies may appear after upgrading to SP4
|
1940104 |
The following issues have been resolved in this release:
Internal ID | Fix |
1810282 | Rule condition doesn't work properly because it is raising alerts if "Doesn't contain" is set as the rule condition. |
1888717 | Group metric does not work if any targeted device does not return data. |
1878569 | Cannot monitor AIX 5.3 data in Real Time Performance Viewer because metricprovider doesn’t open a listening port. |
1888703 | A When a group metric is monitored in a policy, data is not added to the MonitorMetricData table and there is not instance in the MonitorMetricInstances table. |
1861842 | When a custom DLL metric policy is assigned to the Windows 2008 x64 client, the Metric Provider service crashes. |
1878643 | When the agentless ping metric/rule is configured with a repeat count greater than 1, a false normal alert is triggered followed by a critical alert. |
1888682 | Added retry logic for drilldown metrics. |
1880003 | If a single agentless metric is referenced by two different rules which reside in two different monitor policies, two alerts get generated for a resource from both rules. |
1855806 | NT events from monitored Windows 2008 R2 are not collected in Historical Performance Viewer. |
Subscribing will provide email updates when this Article is updated. Login is required.
7.0
This will clear the history and restart the chat.
Thanks for your feedback. Let us know if you have additional comments below. (requires login)