Chat now with support
Chat mit Support

Active Administrator 8.7 - 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
•
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
•
Required permissions: Domain user privilege is required.
Description

Active Administrator® Data Service (ADS) periodically monitors for conflicting objects in the domain and generates an alert when it encounters one.

Conflicts arise when two objects are created independently at separate locations in the domain. When a conflict is detected during replication, Active Directory® creates a conflict entry appending the following to the domain name of the object:

CNF:<GUID-of-authoritative-object>

Resolution
•
If the conflict object contains useful information, move that information into a different directory object, and then delete the object.
•
If the conflict object does not contain useful information, delete the object.

DNS server missing domain SRV records

Previous Next


•
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
•
Required permissions: Domain user privilege is required.
Description

Service Records or SRV records are registered specifically for domain controllers when a member server is promoted to a domain controller. The Netlogon service on the domain controller is responsible for registering SRV records. Because Active Directory® depends on DNS, if SRV records of domain controllers are missing from the DNS Zone of the domain, critical failures of Active Directory services can occur.

Resolution

The following methods can be used to re-register SRV records of a domain controller in the domain DNS zone:

•
Restart the Netlogon service on domain controller.
•
Run DcDiag /fix.
•
Run NetDiag /fix.
•
Re-register from Netlogon.dns file in \Windows or Winnt\System32\Config directory.
Related article

https://support.microsoft.com/en-us/help/241505/srv-records-missing-after-implementing-active-directory-and-domain-name-system

Domain FSMO role placement

Previous Next


•
Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022
•
Required permissions: Domain user privilege is required.
* 
NOTE: As part of the data collector setup, you can select to validate the RID Master, the Naming Master, the Schema Master, and the Infrastructure Master role. By default, all are selected for validation. You must, however, select at least one FSMO role validation option to enable the data collector.
Description

The Active Directory Installation Wizard performs the initial placement of roles on domain controllers and is often correct for directories that have just a few domain controllers. A directory that has many domain controllers may require manual intervention to optimize placement.

Resolution
•
Place the schema master on the PDC of the forest root domain.
•
Place the domain naming master on the forest root PDC.
•
Place the RID master on the domain PDC in the same domain.
•
Legacy guidance suggests placing the infrastructure master on a non-global catalog server.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen