Converse agora com nosso suporte
Chat com o suporte

Active Administrator 8.6.2 - User Guide

Active Administrator Overview User Provisioning Certificates Security & Delegation  Active Directory Health
Switching to Active Directory Health Using the Active Directory Health landing page Installing Active Directory Health Analyzer agents Using the Active Directory Health Analyzer agent configuration utility Excluding domain controllers Managing the Remediation Library Analyzing Active Directory health Analyzing Azure Active Directory Managing Active Directory Health Analyzer alerts Managing alert notifications Pushing alerts to System Center Operations Manager and SNMP managers Managing monitored domain controllers Managing data collectors Active Directory Health Templates Managing Active Directory Health Analyzer agents Using the Troubleshooter Recovering Active Directory Health data
Auditing & Alerting Group Policy Active Directory Recovery Active Directory Infrastructure DC Management DNS Management Configuration
Using the Configuration landing page Managing tasks Defining role-based access Setting email server options Configuring SCOM and SNMP Settings Setting notification options Setting Active Template options Setting agent installation options Setting recovery options Setting GPO history options Setting certificate configuration Setting service monitoring policy Managing archive databases Migrating data to another database Setting a preferred domain controller Setting up workstation logon auditing Managing configuration settings Setting user options Managing the Active Directory server
Diagnostic Console Alerts Appendix
Domain controller alerts
Active Directory Certificate Services service is not running Active Directory Domain Services is not running Active Directory Web Services service is not running Consecutive replication failures DC cache hits DC DIT disk space DC DIT log file disk space DC LDAP load DC LDAP response too slow DC Memory Usage DC properties dropped DC RID pool low DC SMB connections DC SYSVOL disk space DC time sync lost Detected NO_CLIENT_SITE record DFS Replication service not running DFS service is not running DFSR conflict area disk space DFSR conflict files generated DFSR RDC not enabled DFSR sharing violation DFSR staged file age DFSR staging area disk space DFSR USN records accepted DFSRS CPU load DFSRS unresponsive DFSRS virtual memory DFSRS working set DNS Client Service is not running Domain controller CPU load Domain controller page faults Domain controller unresponsive File Replication Service is not running File replication (NTFRS) staging space free in kilobytes GC response too slow Group policy object inconsistent Hard disk drive Intersite Messaging Service is not running Invalid primary DNS domain controller address Invalid secondary DNS domain controller address KDC service is not running LSASS CPU load LSASS virtual memory LSASS working set Missing SRV DNS record for either the primary or secondary DNS server NETLOGON not shared NetLogon service is not running Orphaned group policy objects exist Physical memory Power supply Primary DNS resolver is not responding Secondary DNS resolver is not responding Security Accounts Manager Service is not running SRV record is not registered in DNS SYSVOL not shared W32Time service is not running Workstation Service is not running
Domain alerts Site alerts Forest alerts Azure Active Directory Connect alerts
Event Definitions PowerShell cmdlets

Missing SRV DNS record for either the primary or secondary DNS server

Previous Next


Alerts Appendix > Domain controller alerts > Missing SRV DNS record for either the primary or secondary DNS server

Missing SRV DNS record for either the primary or secondary DNS server

Indicates one or more requisite Domain Name System (DNS) Service (SRV) entries are not defined. DNS SRV entries are vital to the proper functioning of Active Directory®.

Data collector
Category: General
Name: Missing domain controller SRV DNS record
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
Required permissions: When monitored locally and remotely, only domain user privilege is required. When monitored remotely, the target server must have WMI remote access enabled and the user must be a member of the Distributed COM Users group.
Description

Active Directory Health Analyzer queries the DNS service for the SRV entries required for each zone hosted on the server. Note that this applies exclusively to zones designated as primary. If any of the SRV entries are not present, this alert is raised. Active Directory Health Analyzer does not evaluate SRV entries for accuracy, but only checks if the entries are present.

Active Directory Health Analyzer confirms the existence of the following SRV entries for each zone hosted on the server:

_ldap._tcp.<zone-name>

This alert is accompanied by a list of the missing SRV entries.

Whenever a domain controller is promoted, the Microsoft NetLogon process registers the applicable SRV entries with the primary DNS server of the affected domain. As SRV entries are used to identify the constituent domain controllers, the Primary Domain Controller(PDC), and the owner of the global catalog of each zone, the absence of an SRV entry can have serious consequences for Active Directory.

The presence of all requisite SRV locator entries is evaluated for top-level zones exclusively. However, SRV locator entries of sub-zones that host at least one domain controller (with a Directory Analyzer agent) are evaluated.

Cause

Typically, missing SRV entries indicate that Dynamic DNS has been disabled for one or more DNS zones. Active Directory relies on Dynamic DNS to update all affected entries when network resources are altered or relocated. Other possible causes include DCPROMO failure, and erroneous manual configuration of SRV entries.

Resolution

Confirm that Dynamic DNS is enabled on all applicable zones. Either add the SRV entries manually in the DNS Management Console or cause the entries to be refreshed (for example, by demoting and subsequently promoting the effected domain controllers).

NETLOGON not shared

Previous Next



NETLOGON not shared

Indicates that the NETLOGON folder is not shared. File Replication Service requires this folder to be shared on domain controllers for replication to work correctly.

Data collector
Category: Validations
Name: Is the domain controller folder Netlogon shared
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
Required permissions: When monitored locally and remotely, only domain user privilege is required. When monitored remotely, the target server must have WMI remote access enabled and the user must be a member of the Distributed COM Users group.
Description

Logon scripts for a domain controller are found under the NETLOGON admin share for Windows NT. On Windows NT domain controllers, the %SystemRoot%\System32\Repl\Import\Scripts folder is shared as NETLOGON. Dcpromo modifies the registry value that defines the path to the NETLOGON share to %SystemRoot%\Sysvol\Sysvol\domain_name\Scripts.

The default folder structure is:

Any changes to the %systemroot%\SYSVOL folder on any domain controller are replicated to the other domain controllers in the domain. Replication is RPC based.

You can use NETLOGON and SYSVOL to distinguish between a domain controller and a member server. If both the NETLOGON and SYSVOL shares exist on a server, it is a domain controller. When dcpromo demotes a domain controller to a member server, the NETLOGON share is removed, so the presence of only SYSVOL indicates a member server.

Resolution

All potential source domain controllers in the domain should themselves have shared the NETLOGON and SYSVOL shares and applied default domain and domain controllers policy.

SYSVOL directory structure:

To set the Netlogon path
1
Click Start, Click Run, type regedit, and press ENTER.
2
Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters.
3
Right-click NetLogon, and select Modify.
4
In the Value data box, enter the new path, including the drive letter, and click OK.
To share folders with other users on your network
1
Open My Documents in Windows® Explorer.
2
Click Start, point to All Programs, point to Accessories, and click Windows Explorer.
4
Click Share this folder in File and Folder Tasks.
5
In the Properties dialog box, select Share this folder to share the folder with other users on your network.
Related articles

NetLogon service is not running

Previous Next


Alerts Appendix > Domain controller alerts > NetLogon service is not running

NetLogon service is not running

Indicates the NetLogon service is currently not running on the domain controller.

Data collector
Category: Windows Services
Name: Netlogon Windows Service
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
Required permissions: When monitored locally, only domain user privilege is required. When monitored remotely, domain administrator privilege is required.
Description

The Directory Analyzer agent periodically checks to ensure that the Net Logon service is running.

Resolution

Use the Services MCC snap-in or another SCP application to restart the Net Logon service.

Orphaned group policy objects exist

Previous Next


Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
Required permissions: When monitored locally or remotely, read access to SYSVOL.
Description

The Directory Analyzer agent compares the representation of GPOs stored in the local SYSVOL with GPOs found in Active Directory. This alert is active when a GPO represented in the local SYSVOL is not found in Active Directory.

Resolution

Review the reported orphaned GPO folders in the local SYSVOL and remove any that are obsolete.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação