PATROL KM for Microsoft Windows OS configuration variables

Specifies whether the KM inactivates itself when a Microsoft performance object is disabled.

This configuration variable can also be associated with any other KM.

Specifies whether a cache is created for pconfig variables in PATROL Agent namespace.

BMC does not recommend to enable this option for PATROL Agent 9.0.20 or later.

• integer > = 0
• -1 turns off this feature

Specifies whether the KM automatically creates instances for the PATROL group

Note: You must also remove the instances from the list of monitored instances using the Configure Manual Process Monitoring > Remove Processes menu command.

• 0 = instances are created
• 1 = instances are not created

• Integer > = 0
• All

Length of time (in minutes) that the process can remain in a run-away state before the KM terminates the process.

A run-away process is defined as a process that exceeds the PROCProcessorTimePercent parameter alarm threshold for the length of time specified by this variable.

Valid values are:

• 0: annotation on
• 1: annotation off

Valid values are:

• 0 = disabled
• 1 = enabled

Valid values are:

• 0 or blank = enabled
• 1 = disabled

Global setting that specifies restart properties for all services.

For more information about using this variable, see Ensuring that services are restarted as desired.

Valid values are:

• 0 = yes, automatic restart
• 1 = no automatic restart

Valid values are:

• 0 = by default all services are monitored
• 1 = disables service monitoring

Valid values are:

• 0 = disabled, manual services are not monitored
• 1 = enabled, manual services are monitored

Enables you to remove the SERVICES prefix from NT_SERVICES instance names

Note: You must enter this variable manually; the KM does not create it.

In version 3.9.00 of PATROL KM for Microsoft Windows OS, the NT_SERVICES instance names were changed; they were prefixed with SERVICES. This naming convention is not fully backward compatible.

Valid values are:

• 0 or blank = prefix
• 1 = no prefix

Specifies whether the service is trigger start or non-trigger start.

Valid values are:

• Y = Trigger start
• N = Non trigger start

Comprises of the following variables:

• OverrideGlobalServiceMonitoring
• IgnoreAutoResetConfig
• Alarm
• WarningAlarm
• AutoRestart
• Monitor
• MonitorProcess
• MonitorNotRespond
• OverrideGlobalServiceRestart
• OverrideMonitorManualServices (Note: This variable is available since version 4.8.00 of the KM.)
  

To activate a particular service, set the value of the corresponding bit to 1 in /PSX_P4WinSrvs/PWKPKMforMSWinOS_config/ServiceMonitoring/ServiceList/Service Name/SvcConfigVars" = {REPLACE = "0,0,0,0,0,1,0,0,0,0"}

The comma separated values correspond to the variables in the order as mentioned above.

Service Startup Type configuration variable has to be applied along with "SvcConfigVars" variable to override default monitoring.
/PSXP4WinSrvs/PWK_PKMforMSWinOS_config/ServiceMonitoring/ServiceList/ServiceName/StartupType
Value = "Automatic" / "Manual" / "Disabled" (startup type Service)

Valid values are:

• 0 = no alarm
• 1 = yes, alarm

Valid values are:

• 0 = no restart
• 1 = yes, restart

Valid values are:

• 0 = yes, automatic reset
• 1 = no automatic reset

Valid values are:

• 0 = no monitoring
• 1 = yes, monitor

Valid values are:

• 0 = no
• 1 = yes

• 0 = no
• 1 = yes

Specifies whether the AutoRestart variable for the monitored service overrides the global DisableServiceRestart variable.

You can set this variable only by using PATROL Configuration Manager.

Valid values are:

• 0 = do not override
• 1 = override

Specifies whether the MonitorProcess variable for the monitored service overrides the global DisableServiceMonitoring variable

You can set this variable only by using PATROL Configuration Manager.

Valid values are:

• 0 = do not override
• 1 = override

Valid values are:

• 0 = alarm
• 1 = warning

Specifies the location of the backup directory for the event log.

Note: If the directory entered for the backup directory does not exist, the Backup and Clear Eventlog recovery action fails.

Valid values are:

• 0 = only configured
• 1 = all

Specifies whether to automatically activate and automatically inactivate event log parameters based on the current configuration.

You can also use this variable to inactivate or activate other parameters.

For example, you could use the following variable to inactivate the NT_HEALTH parameters: .../HealthMonitoring/OverrideParameterAutoActivate

Valid values are:

• 0 = use auto configure
• 1 = do not use auto configure

Specifies whether the parameter ELMEvFileFreeSpacePercent automatically activates and inactivates based on the current configuration.

This variables applies to all event logs. You can also apply this variable to specific event logs.

Valid values are:

• 0 = use auto configure
• 1 = do not use auto configure

Specifies whether the event log uses a checkpoint value to guarantee that no events are missed if the PATROL Agent is not running or the KM is not loaded for a period of time.

This is a global setting that can be overridden by individual event log configurations.

Valid values are:

• 0 = do not use
• 1 = use

Valid values are:

• 0 = do not disable information events
• 1 = disable information events

Valid values are:

• 0 = event log name format
• 1 = detailed format

Valid values are:

• 0 = do not send
• 1 = send

Valid values are:

• 0 = do not send
• 1 = send

Valid values are:

• 0 = do not override (create)
• 1 = yes, override (do not create)

Specifies whether the parameter ELMEvFileFreeSpacePercent automatically activates and inactivates based on the current configuration.

This variable applies to a specific event log. You can also apply this variable globally to all event logs.

Valid values are:

• 0 = use auto configure
• 1 = do not use auto configure

Valid values are:

• 0 = do not use
• 1 = use

Valid values are:

• 0 = not enabled
• 1 = enabled

Specifies whether an application instance is created for the event filter.

An application instance is not required to collect data.

However, if an instance is not created, the only way to retrieve the data collected by the event filter is too subscribe to the event filter data.

Valid values are:

• 0 = not created
• 1 = created

Allows the parent application instance of an event filter to be changed.

If this value is set, the event filter instance is created with the specified parent instance.

Valid values are:

• 0 = do not annotate
• 1 = annotate

Valid values are:

• 0 = do not consolidate
• 1 = consolidate

Valid values are:

• 0 = do not report
• 1 = report

• 1 = Error
• 2 = Warning
• 4 = Information
• 8 = AuditSuccess
• 16 = AuditFailure
• 32 = OtherType
• 64 = Critical
• 128 = Verbose

A valid value is any summation of these types. For example, to monitor both Warning and AuditFailure events, use a value of 18 (2 +16).

Specifies whether all event categories are monitored.

If all categories are monitored (1), then the CategoryList variable represents an exclusion list. Otherwise, it represents an inclusion list.

Specifies whether all event IDs are monitored If all event IDs are monitored (1), then the EventIdList variable represents an exclusion list.

Otherwise, it represents an inclusion list.

Valid values are:

• 0 = not monitored
• 1 = monitored

Specifies whether all sources are monitored If all sources are monitored (1), then the SourceList variable represents an exclusion list.

Otherwise, it represents an inclusion list.

Valid values are:

• 0 = not monitored
• 1 = monitored

Specifies whether all text strings are monitored If all text strings are monitored (1), then the StringList variable represents an exclusion list.

Otherwise, it represents an inclusion list.

Valid values are:

• 0 = not monitored
• 1 = monitored

Specifies whether all users are monitored If all users are monitored (1), then the UserList variable represents an exclusion list.

Otherwise, it represents an inclusion list.

Valid values are:

• 0 = not monitored
• 1 = monitored

Valid values are:

• 0 = do not retain
• 1= retain

Valid values are:

• 0 = Notification
• 1 = Polling
• 2 = Both

Specifies the label that the KM places under the filter instance

Note: You must manually enter this variable; the KM does not create it.

Setting this variable does not change the instance name/namespace. This variable is read only at initial filter creation or parent instance change.

Specifies whether the filter comparisons are made in a case-independent manner.

This variable has five bit values, depending upon case sensitivity, one bit corresponding to each of Source, User, Category, String, and Computer name, respectively.

If any bit value is 1, a case-independent filter comparison is made for the corresponding field.

Valid values are:

• 00000 = none checked (default)
• 11111 = all 5 categories checked
• a combination of 0s and 1s, depending on which of the 5 categories were checked

Valid values are:

• 0 = none of the computers are monitored by default, and the ComputerNamesList variable is an inclusion list
• 1 = all of the computers are monitored, and the ComputerNamesList variable is an exclusion list

Specifies the location of the

Added a new PCONFIG variable for filtering Windows events while subscribing it from Windows Event System. The value of this variable will be XML query.

Valid values are:

• 0 = auto configure
• 1 = do not auto configure

Valid values are:

• 0 = auto acknowledge
• 1 = manually acknowledge

Valid values are:

• 0 = do not monitor
• 1 = monitor

Valid values are:

• 0 = only configured objects
• 1 = all

Valid values are:

• 0 = no
• 1 = yes

Valid values are:

• 0 = no
• 1 = yes

Valid values are:

• 0 = no
• 1 = yes

Valid values are:

• 0 or blank = enabled
• 1 = disabled

Valid values are:

• 0 = no
• 1 = yes

Valid values are:

• 0 = no
• 1 = yes

The pagefiles that are monitored.

This variable is ignored unless the /PagefileMonitoring/IncludeAll variable is set to 0.

Valid values are:

• 0 = no
• 1 = yes

Valid values are:

• 0 = no
• 1 = yes

Valid values are:

• 0 = no
• 1 = yes

Valid values are:

• 0 = no
• 1 = yes

Valid values are:

• 0 = no
• 1 = yes

Valid values are:

• 0 = no
• 1 = yes

Valid values are:

• 0 = no
• 1 = yes

Valid values are:

• 0 = no
• 1 = yes

Valid values are:

• 0 = no
• 1 = yes

Valid values are:

• 0 = no
• 1 = yes

Valid values are:

• 0 = no
• 1 = yes

Changes the values generated by the following parameters:

• LDldFreeSpacePercent
• LDldFreeMegabytes
• LDldDiskSpaceUsed

Valid values are:

• 1 = values shown for a particular drive instance do not consider the mount drives
• 0 = value shown is an aggregate of a particular drive instance and all of its mount drives

Valid values are:

• 0 = no
• 1 = yes

Valid values are:

• 0 or blank = enabled
• 1 = disabled

Valid values are:

• 0 = no
• 1 = yes

Valid values are:

• 0 = no
• 1 = yes

Valid values are:

• 0 = auto configure
• 1 = do not auto configure

Valid values are:

• 0 = auto correct
• 1 = do not auto correct

Allows you to configure the KM by using three options.

The KM looks for a crash dump file as well as the event (ID 6008).

Valid values are:

• 1 = Event (ID 6008) - only monitors the event id, 6008.
• 2 = Crash Dump - only monitors the crash, Dump.
• 3 = Default - monitors crash dump or event as per registry configuration.

Allows you to provide a valid user name and password for the PATROL Agent default account.

The KM functions without specifying the PATROL Agent default account. Except for the Windows event log KM, the PATROL KM for Microsoft Windows works with a blank user name and password for the PATROL Agent default account. When you enter a blank user name and password for the PATROL Agent default account, XPC (psx_server.xpc ) runs under the local system account.

The Windows event log KM requires a valid user name and password to connect to the PATROL Agent using PEMAPI.

winRMTimeOut

Provides a way to configure the timeout that is used, when the following WinRM error is encountered:

The WS-Management service cannot complete the operation within the time specified

The timeout value must be specified in milliseconds.

For example: For 5 minutes set the value as 300000

Valid values are:

• 1: HTTP
• 2: HTTPS