Chat now with support
Chat mit Support

Active Administrator 8.5 - User Guide

Active Administrator Overview 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

Security Accounts Manager Service is not running

Indicates the Security Accounts Manager Service is currently not running on the domain controller.

Data collector
•
Category: Windows Services
•
Name: Security Accounts Manager Service
•
Supported on: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019
•
Required permissions: When monitored locally or remotely, domain administrator privilege is required.
Description

The Directory Analyzer agent periodically checks to ensure the Security Accounts Manager Service is running.

Resolution

Use the Services MCC snap-in or another SCP application to restart the Security Accounts Manager Service.

SRV record is not registered in DNS

Indicates that a record from the netlogon.dns file is not registered in DNS.

Data collector
•
Category: General
•
Name: Compare SRV DNS records with netlogon.dns file
•
Supported on: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019
•
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

The Directory Analyzer agent checks each domain controller for service records. If a service record is missing, check the details for the alert. See Viewing alerts and alert history.

Resolution

Stop and start the Netlogon service to force the domain controller to re-register the appropriate SRV records.

Related article

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

SYSVOL not shared

Indicates that the SYSVOL 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 SysVol shared
•
Supported on: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019
•
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

The SYSVOL folder is shared on an NTFS volume on all the domain controllers in a particular domain and is used to deliver the policy and logon scripts to domain members. By default SYSVOL includes two shared folders, where the scripts folder is shared with the name NETLOGON:

•
%SystemRoot%\Sysvol\Sysvol\domain_name\Policies
•
%SystemRoot%\Sysvol\Sysvol\domain_name\Scripts

The file replication service (FRS) replicates these folders among all domain controllers in the domain. If this folder is not shared, the FRS cannot replicate it.

The alert checks the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanserver\Shares\ SYSVOL registry key. If the key is not present, the SYSVOL folder is not shared and cannot be replicated and this alert is triggered. The alert is removed when the SYSVOL folder status is set to be shared.

Resolution

SYSVOL directory structure:

Domain

DO NOT REMOVE NtFrs PreInstall Directory
Policies
{GUID}
Adm
Machine
User
{GUID}
Adm
Machine
User
{etc.,}
Scripts
Staging
Staging Areas
MyDomainName.com

Scripts

Sysvol( sysvol share )
MyDomainName.com
DO NOT REMOVE NtFrs PreInstall Directory
Policies
{GUID}
Adm
Machine
User
{GUID}
Adm
Machine
User
{etc.,}
Scripts(NETLOGON share)
To set the SYSVOL 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 SYSVOL, and select Modify.
4
In the Value data box, enter the new path, including the drive letter, and click OK.
5
Close the Registry Editor.
* 
NOTE: The path in the registry points to the SYSVOL folder located inside the SYSVOL folder that is under the root. When updating the path in the registry, ensure that it still points to the SYSVOL folder inside the SYSVOL folder that is under the root.
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.
3
Navigate to the SYSVOL folder.
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.

W32Time service is not running

Indicates the Windows® Time (W32Time) service is not currently running on the domain controller.

Data collector
•
Category: Windows Services
•
Name: Windows Time service
•
Supported on: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019
•
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 W32Time service is running.

Resolution

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

Verwandte Dokumente

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating