Thursday, 21 June 2012

The AD Global Catalog Search Response is above the configured threshold



The AD Global Catalog Search Response is above the configured threshold

Operational States

Name State Description
General Response OK Success
General Response Warning Warning

Overridable Parameters

Parameter Name Default Value Description Override
Interval (sec) 300
Log Success Event false
Query (String) (objectCategory=DMD)
Failure Threshold 4
Timeout Seconds 120

Alert Details

Monitor State Message Priority Severity Auto Resolution
General Response Warning (Warning) The AD Global Catalog Search Response is above the configured threshold Medium Warning Yes

Run As Profiles

Name
Default

Monitor Knowledgebase

Summary
AD Global Catalog Reponse Monitor. This monitor measures the time that is required to perform a Global Catalog search. The query to be executed can be passed as a parameter (see configuration). The measurement is reported as performance data, and related rules generate alerts for abnormally slow conditions
Causes
This unit monitor does not contain any causes.
Resolutions
See additional alerts for details.
External References
This monitor does not contain any external references.

related posts

Source - MajiAai


Submit your suggestion / comments / complaints / Takedown request on lookyp.com@gmail.com
Posted by Mona at 07:54 0 comments

Recover An Unsaved Document When Word Crashes



Recover An Unsaved Document When Word Crashes

How to turn on AutoRecovery:

Select Tools, Options, Check ‘Save AutoRecover info every:‘ and provide the interval.
Then click on the File Locations tab, Select AutoRecover Files, Click on “Modify…” & provide a location for its to save the files.
How does it work:
When AutoRecover is turned on, the changes you make are saved at set intervals in a separate, temporary recovery file. Then, if you have to restart Word or your computer without saving your work, Word automatically opens the recovery file. In some cases it doesn’t. In such situations you have to try out the above solution. The recovery file contains your changes up until the last time AutoRecover saved the document. For example, if you set AutoRecover to save every 7 minutes, you don’t lose more than 7 minutes of work. All documents that were open at the time of the power failure or similar problem appear for you. Only changes you made after the last AutoRecover save are lost.

related posts

Source - MajiAai


Submit your suggestion / comments / complaints / Takedown request on lookyp.com@gmail.com
Posted by Mona at 07:12 0 comments

A problem has been detected with the trust relationship between two domains Rule



A problem has been detected with the trust relationship between two domains Rule

 

Summary
A problem with a trust has been detected. The trust has been reset automatically in an attempt to correct the problem.
Causes
The alert description describes the error that occurred.
Resolutions
If this is the first alert, no further action is necessary. The script AD Trust Monitoring will attempt to fix the problem.

If you have received multiple alerts, use NLTEST /SC_RESET:xxx to manually reset the trust.

related posts

Posted by Mona at 06:46 0 comments

AD Replication Monitoring – Time skew detected



AD Replication Monitoring – Time skew detected

 

Alert: AD Replication Monitoring – Time skew detected

Issue: This was caused by domain controllers running on Virtual Servers which were synchronizing with the host operating system while the host operating system was not time synchronized.

Resolution: Fixed the actual time on the domain controllers and configured the Guest operating system in Virtual Server to not synchronize with the Host operating system. This was done through shutting down the Guest operating system, and configuring the Virtual Machine Addition Properties, under additional features uncheck Host Time Synchronization, and restart the Guest operating system.

related posts

Posted by Mona at 06:39 0 comments

A problem has been detected with the trust relationship between two domains



A problem has been detected with the trust relationship between two domains

 

Alert: A problem has been detected with the trust relationship between two domains

Additional Alert: A problem with the inter-domain trusts has been detected

Resolution :

1>Test first with the NETDOM command (override with parameters to do a dsquery /domain: /verify dc) first for the local domain (success) then for the remote domain reporting the failure (failed with cannot contact the remote domain).

2> Run nltest first for the local domain (success) then for the remote domain reporting the failure.

3>Run DCDIAG on the server.

4>Run the enumerate trusts task on the system (AD_Enumerate_Trusts.vbs).

5>Check DNS zone and make DNS consistent and flush dns on the server experiencing the alerts.

6>Use Active Directory Domains and Trusts UI to validate each of the trusts.

 

Issue:

This alert is occurring from domain controllers who cannot communicate with the domain controller in the trusted domain to validate this trust.

Resolution: Tested first with the NETDOM command (override with parameters to do a dsquery /domain: /verify dc) first for the local domain (success) then for the remote domain reporting the failure (failed with cannot contact the remote domain). T [...]


Submit your suggestion / comments / complaints / Takedown request on lookyp.com@gmail.com
Posted by Mona at 05:26 0 comments

Failed to ping or bind to the Schema Master FSMO role holder Rule



Failed to ping or bind to the Schema Master FSMO role holder Rule

Alert Details

Message Priority Severity
Failed to ping or bind to the Schema Master FSMO role holder. Medium Warning

Rule Knowledgebase

Summary
The AD Op Master Response monitor failed consecutive attempts to bind or ping the schema operations master (also known as the schema flexible single master operations (FSMO) role holder)

 

This is more than a transient error, and it should be investigated. However, because the schema master does not have a high-availability requirement, short-term outages are not necessarily a priority, and they can be deferred..
Causes
This rule does not contain any causes.
Resolutions
To view all the events that are generated by the AD Op Master Response monitor, open the AD MP Events view. These events provide more detailed information about the errors that occur during testing of the operations masters.

related posts

Posted by Mona at 05:07 0 comments

Failed to ping or bind to the Infrastructure Master FSMO role holder



Failed to ping or bind to the Infrastructure Master FSMO role holder

 

Overridable Parameters

Parameter Name Default Value Description Override
Priority 1
Severity 1

Alert Details

Message Priority Severity
Failed to ping or bind to the Infrastructure Master FSMO role holder. Medium Warning

Rule Knowledgebase

Summary
The AD Op Master Response monitor failed during consecutive attempts to bind or ping the infrastructure operations master (also known as the infrastructure flexible single master operations (FSMO) role holder). This is more than a transient error, and it s [...]


Submit your suggestion / comments / complaints / Takedown request on lookyp.com@gmail.com
Posted by Mona at 05:04 0 comments
Subscribe to: Posts (Atom)