Configuration of ADWSEvtLogTest

This test scans the Active Directory Web Services event log for current and probable problems related to the ADWS, and brings the count and details of such problems to the notice of administrators.

The default parameters associated with this test are as follows:

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

• Specify host for which the test is to be configured, in the HOST text box.

• Enter the port number on which the server is listening in the PORT text box.

• The LOGTYPE parameter refers to the type of event logs to be monitored. By default, this is set to Active Directory Web Services.

• Using this page, administrators can configure the event sources, event IDs, and event descriptions to be monitored by this test. In order to enable administrators to easily and accurately provide this specification, this page provides the following options:

  • Manually specify the event sources, IDs, and descriptions in the FILTER text area, or,

  • Select a specification from the predefined filter policies listed in the FILTER box

  For explicit, manual specification of the filter conditions, select the No option against the POLICY BASED FILTER field. This is the default selection. To choose from the list of pre-configured filter policies, or to create a new filter policy and then associate the same with the test, select the Yes option against this field.

• By default, the all filter policy is set for this test. This filter policy is pre-configured to monitor all events in the Active Directory Web Services log, regardless of the event source or event ID. If required, you can modify this filter policy definition by clicking the encircled ‘+’ icon alongside the FILTER text area. Clicking on this icon leads you to a page where you can modify the all filter policy by specifying a different policy name and/or by by including/excluding specific event sources, event ids, and event descriptions in the Active Directory Web Services log.

  Note:

  The Event sources and Event IDs specified here should be exactly the same as that which appears in the Event Viewer window.  

• The eG agent can either use WMI to extract event log statistics or directly parse the event logs using event log APIs. If this flag is Yes, then WMI is used. If not, the event log APIs are used. This option is provided because on some Windows 2000 systems (especially ones with service pack 3 or lower), the use of WMI access to event logs can cause the CPU usage of the WinMgmt process to shoot up. On such systems, set this parameter value to No.

• eG Enterprise also provides you with options to restrict the amount of storage required for event log tests. Towards this end, the DDFORINFORMATION flag is made available in this page. By default, this flag set to No, indicating that by default, the test conserves space in the eG database by not generating and storing detailed measures for information events. If you want to view and analyze information events, then set the DDFORINFORMATION flag to Yes.

• The DD FREQUENCY refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD FREQUENCY.

• To make diagnosis more efficient and accurate, the eG Enterprise suite embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the DETAILED DIAGNOSIS capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

  The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability

  • Both the normal and abnormalfrequencies configured for the detailed diagnosis measures should not be 0.

• If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS check box will appear in this page. Clicking on this check box will allow you to apply the configuration to all/selected components of that type.

• Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$“ or contain a series of “*”. A value of "none" in the parameter value indicates that the corresponding parameter value can be changed if required.