4.7.00 enhancements


This topic provides information about the enhancements and features introduced in PATROL for Microsoft Windows Servers 4.7.00.

Enhancements

BMC ProactiveNet Central Monitoring Administration support

With version 4.7.00 of PATROL for Microsoft Windows Servers and version 9.5.00 of BMC ProactiveNet Central Monitoring Administration, you can monitor the following monitoring profiles. Monitoring profiles provide you the capability of monitoring various aspects of the Windows components. You can directly apply the monitoring profile to enable default monitoring for the areas (monitor types) available under that profile. You can also manually configure some of the monitor types that are available for manual configuration.

Some monitoring profiles contain monitor types that were independently available earlier, without being a part of a monitoring profile. Some of these monitor types are renamed in this version of the product.

The following table provides details about the changes as compared to the earlier release:

Monitor type (old name)

Monitor type (new name, if any)

Monitoring profile container

Remote Host Configuration

Process Configuration

Windows Event Log

Microsoft Clusters Monitoring

Services Configuration

Executing agent actions

Besides configuring monitor types, you can now execute agent actions available on the BMC ProactiveNet Performance Management Operations Console. Agent actions provide menu commands that are available on BMC PATROL for performing functions such as refreshing parameters of an application class, configuring trace options, viewing reports, and so on. For more information, see Executing-agent-actions-on-a-monitor.

Support for dynamically monitoring Perfmon instances

You can dynamically monitor all the Perfmon instances available in your environment. You can do this by using the asterisk (*) wildcard character as the value for the following Agent configuration variable:

/Perfmon/NT_PERFMON_WIZARD/object/Instances (object refers to the Permon object)

Thresholds disabled for parameters

With this release, thresholds such as the Border Range, Alarm1, and Alarm2 are disabled for the availability parameters.

The following table lists the parameters along with the application classes to which they belong.

Application class

Parameter

PATROL_NT

NT_SYSTEM

NT_REGISTRY

NT_PROCESS

NT_PHYSICAL_DISKS

NT_NTFS_QUOTA

NT_NTFS_MOUNT

NT_MEMORY

NT_LOGICAL_DISKS

NT_JOBS_PROCESS

NT_JOBS

NT_HYPERV_PART_VIRTUAL_PRCR

NT_HYPERV_PARTITION_VHD

NT_HYPERV_LOGICAL_PROCESSOR

NT_HEALTH


NT_EVLOGFILES

NT_CPU


NT_CACHE

MCS_Quorum

MCS_Performance

MCS_Nodes

MCS_Group_Resources

MCS_Groups

AD_AD_LOST_FOUND_OBJECTS

AD_AD_LDAP

AD_AD_DNS

RDS_USER

NT_SHARES

NT_DHCP_SCOPE

NT_DHCP

NT_DFS_ROOT

MQ_SERVER

MQ_QUEUES


COM_APPLICATION

Package change notice

With BMC PATROL for Microsoft Windows Servers 4.7.00 release, packaging of BMC PATROL Agent with this KM has been discontinued.

Related topics

Known-and-corrected-issues

Downloading-the-installation-files

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*