Management Server Global Settings

The following settings are specific to the Management Server(s).

Discovery Tab

Interval for running attribute discovery

Description: How often the Management Servers will run an attribute discovery against all agents they service and the agents run attribute discovery for themselves.

Default: 60 minutes.

Override: Yes.

Impact: Increasing the value lowers resource overhead on the Management Server, agents, and the network; however, the attributes on the agents might become asynchronous more frequently. Decreasing the value increases resource overhead, but agent attribute information will be better synchronized in a dynamic environment. This setting should be tuned with the following factors in mind:

  • How often will the attributes change for managed computers?

  • What attributes are being collected (depending on rules that are applied to managed computers)?

  • How much resource overhead can the MOM environment incur before performance degradation occurs?

  • How important is it that attributes synchronization is immediate?

Caution: Lowering this value to 5 minutes might present an unnecessary load on resources, especially if you do not expect attributes to change frequently.

Recommendations: For typical conditions, use the default setting.

Interval for computer discovery

Description: How often the Management Servers will run an attribute discovery against all of the agents they manage.

Default: 1 day.

Override: Yes.

Impact: Increasing the value lowers resource overhead on the Management Server, agents, and the network; however, the attributes on the agents might become asynchronous more frequently. Decreasing the value increases resource overhead, but agent attribute information will be better synchronized in a dynamic environment.. This setting should be tuned with the following factors in mind:

  • How often will new computers be added to the network that will need to have agents installed?

  • How much resource overhead can the MOM environment incur before performance degradation occurs?

  • How important is having computers discovered, and agents installed, immediately?

Responses Tab

Simultaneous responses allowed

Description: The number of rule-based, server-side responses that can be run simultaneously, on the Management Server. This setting is global, but can be overridden per agent.

Default: 20 responses.

Override: Yes.

Impact: Increasing the value uses more resources. Be sure to monitor for failed responses and decrease the value, as needed. The value depends on the hardware resources, the services and applications running on the managed computer, network bandwidth, and other factors.

Caution: Setting the value too high can consume resources on the computer, causing it to hang or restart. Do not set this value to 0 because there will be no available queue threads which will cause the queues to fill.

Temporary Storage Tab

Maximum disk space

Description: The size of the Management Server cache, in KB, on the disk drive. This cache is used to temporarily store operational data while the data is being sent to the MOM Database.

Default: 3,000 KB.

Override: Yes.

Impact: You might want to increase the value, if any of the MOM database is down, full, or unavailable.

Caution: Decreasing this value by too much might cause WMI and performance counter data to be dropped. Increasing this value by too much, without cause, might consume needed disk space. If the file must be greater than 100 MB, this might indicate a problem with agent communications, or it might indicate that the agent is collecting too much data.

Rule Change Polling Tab

Interval to check for rule changes

Description: The interval for determining how often the Management Server looks for rule changes in the Management Packs.

Default: 5 minutes.

Override: No.

Heartbeat Checking Tab

Interval to scan for agent heartbeats

Description: The time interval for scanning for agent heartbeats.

Default: 30 seconds.

Override: No.

Description: Specifies the number of times the Management Server will scan agentless managed computers. The number of scans is directly linked to the elapsed time for the scans. For example, completing 2 scans takes 60 seconds.

Number of ping attempts

Description: How many "ping" attempts the Management Server will send to the managed computer per "ping session." Each ping is equivalent to a command-line ping command.

Default: 1.

Override: No.

Time between pings

Description: How many seconds MOM will wait between ping attempts during a ping session.

Default: 0 seconds.

Override: No.

Ping time out

Description: How many milliseconds each ping attempt waits to receive a response, before failing.

Default: 500 milliseconds.

Override: No.

Number of scans before generating service unavailable

Description: How many scans will occur before MOM will generate a Service Unavailable alert for a managed computer.

Default: 3 scans.

Override: No.