지금 지원 담당자와 채팅
지원 담당자와 채팅

Foglight for Active Directory 5.8.2 - User and Reference Guide

Navigation basics Exploring Foglight for Active Directory dashboards Managing Active Directory agents Reporting on your Active Directory enterprise Foglight for Active Directory views
Forest views Domain views Site views Domain Controller views Description of embedded views
Address Book view Agent State view Asynchronous Thread Queue view Core Services view Database Access view Database Cache view Database Log Access view Database Performance Health view Defragmentation Tasks view DFS Namespace Service API Queue view DFS Namespace Service API Requests view DFS Namespace Service Referrals view DFS Replicated Folders view DFS Replication Connections view DFS Replication Service Volumes view DFS-R Performance Health view Directory Replication Inbound view Directory Replication Outbound view Directory Replication Sync view Directory Replication USN view Directory Services General view Directory Services Performance Health view Directory Services Reads view Directory Services Searches view Directory Services Writes view Domain Controller Details view Domain Controllers view FileReplicaConn Authentications/Bindings view FileReplicaConn Change Orders view FileReplicaConn Fetch view FileReplicaSet Authentications/Bindings view FileReplicaSet Change Orders view FileReplicaSet DS Communications view FileReplicaSet Files view FileReplicaSet Local Change Orders view FileReplicaSet Packets view FileReplicaSet Remote Change Orders view FRS Performance Health view FRS Replica Sets view FRS Staging Files view FSMO Roles view (Domain) FSMO Roles view (Forest) Host Monitor view Inter-Site Transports view Inventory By Category view IP Subnets view Key Distribution Center view LDAP view Memory view Network view Processor view Replication Performance Health view Resource Utilization view Security Accounts Manager view Server Health view Statistics view Storage view Summary and Resource Information view Top AD Metrics view Top 3 Consumers view Top 3 CPU Consumers view Top 3 DS Directory Reads/sec view Top 3 LDAP Bind Times view Top 3 Memory Consumers view Top 3 Network Consumers view Top 3 Replication Queue Length view Top 3 Storage Consumers view Trusts view USN Records view
Foglight for Active Directory rules Running diagnostic tests Managing Active Directory metrics

Diagnostic Tests reference

This section provides a description of the diagnostic tests available in Foglight for Active Directory:

•
DNS Entries diagnostic
•
DNS Partners diagnostic
•
File Replication diagnostic
•
FSMO Best Practices diagnostic
•
GPO Sync diagnostic
•
Hotfix and Service Pack diagnostic
•
Replication Failure diagnostic
•
Replication Link diagnostic
•
Schema Consistency diagnostic
•
Service Status diagnostic
•
Site Configuration diagnostic
•
Time Differential diagnostic
•
Time Parent Sync diagnostic
•
Track Replication diagnostic

DNS Entries diagnostic

Verifies that the DNS entries registered by a specific domain controller can be found on the DNS servers. It finds and parses the following file for pertinent DNS information (which should work for non-MS DNS references): C:\Windows\System32\config\netlogon.dns. This functionality is mostly redundant with the reported ‘isSrvRegistered’ value for each given domain controller.

If this test fails, you should:
•
Ensure that the selected server is operational.
•
Ensure that you have access to the admin$ share on the selected server. This test requires access to the netlogon.dns file stored in admin$\System32\config.
•
Verify that you can make DNS requests from your computer. This test contacts the default DNS server for the local computer.

DNS Partners diagnostic

Verifies that the DC can find the DNS records of each of its inbound replication partners on the DNS server that it is using. To accomplish this, the test works in unison with LDAP and NSLOOKUP utilities.

If this test fails, you should:
•
Ensure that the DC and its partners are operational.
•
Ensure LDAP connectivity is available against the target DC (access via ntdsConnection object).
•
Verify (either using nslookup or the Microsoft® DNS snap-in) that the entries are actually registered.

File Replication diagnostic

Allows you to check the presence of any file on other domain controllers. This test verifies that the files stored on all shares are physically the same files. It verifies the file size in bytes, file date, and file name between the source server and all other selected servers.

To run this test, select the replication partners and enter the name of the file or folder you want confirmed. The test continues through all DCs, recording errors as it processes differences that are found.

* 
NOTE: Select only one target server when running this test.
 
Table 90. File Replication diagnostic
Test Input
Description

Select Replication Partners

Select this button to select the servers where tests should compare the most recent update with that of the target server. Selecting this button displays the Select Target dialog which provides a list of replication partners to choose from.

NOTE: The credentials for the domain controller selected on the Test Targets page will be used to query the replication partner servers selected here. Therefore, the user account used by the selected target server must also have access to these replication partners.
NOTE: Be sure to select servers (both the target servers and replication partners) that are within the same forest. Selecting servers that reside in different forests will result in communication errors.

File Name

Enter the name of the file or folder you want to compare.

Enter in the following format:

c:/Windows/System32/drivers/etc/hosts

Compare File Size

This check box is selected by default indicating that the diagnostic test is to compare the file size. Clear this check box if you do not wish to compare the file size.

Compare File Date

This check box is selected by default indicating that the diagnostic is to compare the file date. Clear this check box if you do not wish to compare the file date.

If this test fails, you should:
•
Ensure that you have access to the admin$ share on the selected server.
관련 문서

The document was helpful.

평가 결과 선택

I easily found the information I needed.

평가 결과 선택