Use this Knowledge Script to modify the maximum number of events or data points that can be stored in the managed client’s local repository. If the managed client is not able to communicate with the management server for any reason, the local repository for the managed client stores the most recent events and data points up to this limit until communication with the management server is restored.
If the number of events or data points exceeds the limit you have set (for example because of an extended network interruption), the oldest events or data records are lost as new events or data points are recorded.
Setting this registry key to 0 may affect the performance on the managed computer when a large number of records are inserted into the local repository (for example, because the management server is down, communication is disabled, or the managed computer is between scheduled uploads). If you are using ODBC, no changes are required.
Windows 2003 Server or later
The default interval for this script is Run once.
Set the following parameters as needed:
|
Parameter |
How to Set It |
|---|---|
|
Change maximum number of data points to store? |
Set to y to change the maximum number of data points that can be added to the local repository. The default is y. |
|
Maximum number of data points to store |
Specify the maximum number of data points that can be added to the local repository. Enter 0 if you do not want to set a limit on the maximum number of data points. The default is 10,000 data points. |
|
Change maximum number of events to store? |
Set to y to change the maximum number of events that can be added to the local repository. The default is y. |
|
Maximum number of events to store (0 for no limit) |
Specify the maximum number of events that can be added to the local repository. Enter 0 if you do not want to set a limit on the number of events. The default is 10,000 events. |
|
Raise event if repository configuration succeeds? |
Set to y to raise an event indicating the success or failure of the operation. The default is n. |
|
Event severity when repository configuration... |
Set the event severity level, from 1 to 40, to reflect the importance when the job: ... succeeds. If you set this script to raise an event when the job succeeds, set the event severity level for a successful discovery. The default is 25 (blue event indicator). ... fails. The default is 5 (red event indicator). |