Chatee ahora con Soporte

Obtener ayuda en vivo
Completar registro

Iniciar sesión

Solicitar precios

Comuníquese con Ventas

Active Administrator 8.7 - Web Console User Guide

Navegación de contenido

Active Administrator Web Console Overview

About the Web Console Configuring the web server Opening the Web Console Using the Active Administrator dashboard

Displaying the dashboard Arranging the dashboard panels Setting refresh and rotation Configuring dashboard panels

Using the help menu

Active Directory Health

About Active Directory Health Using the Active Directory Health landing page Analyzing health of a domain controller Analyzing health of a domain Analyzing health of a site Analyzing the health of a forest

Viewing alerts Viewing alert details Adding an alert to notifications Creating a notification for an alert Viewing alert history

Filtering alert history

Generating an alert history report Muting alerts Clearing mutes Viewing mute history

About alert notifications Viewing alert notifications Creating alert notifications Pushing alerts to System Center Operations Manager Limiting notifications

Active Directory Health Check

Using the Health Check landing page Creating a Health Check Setting options for Health Check tests Purging Health Check History Health check tests

Forest details Naming operations master inconsistent Naming operations master is not a global catalog server Naming operations master not responding Schema operations master inconsistent Schema operations master not responding Schema version inconsistent

Conflict encountered during replication DC replication latency DNS domain missing SRV records Domain details FSMO placement GC replication latency Infrastructure master host GC Infrastructure master not responding Infrastructure operations master inconsistent Objects exist in the Lost and Found PDC master not responding RID master not responding RID operations master inconsistent Root PDC time source missing

Domain controller tests

Active Directory Domain Service Cache copy read hits Compare SRV DNS records with Netlogon.dns file Consecutive replication failures threshold exceeded CPU processor time DC replication latency DFS namespace service DFS replication service DFSRS % processor time DFSRS conflict area disk space DFSRS conflict files generated DFSRS private bytes DFSRS RDC is not enabled DFSRS sharing violation DFSRS staged file age DFSRS staging area disk space DFSRS USN records accepted DFSRS working set Domain controller relative identifier (RID) Domain controller responsive Domain controller time synchronization File replication (NTFRS) staging space free in kilobytes GC replication latency Group policy object inconsistent Installed applications Installed updates Invalid primary DNS domain controller IP address Invalid secondary DNS domain controller IP address Kerberos Key Distribution Center service LDAP response time Logic disk details LSASS % processor time LSASS private bytes LSASS working set Memory details Memory page faults a second Missing domain controller SRV DNS record NetLogon folder shared NetLogon Windows service Network adapter information NTDS DRA inbound properties filtered a second NTDS LDAP searches a second NTDS LDAP writes a second Operating system details Primary DNS resolver not responding Secondary DNS resolver not responding Server sessions SysVol details SysVol folder shared Windows Time service

No authority in site to resolve universal group memberships Inter-site replication manager Inter-site replication topology generation disabled Intra-site replication topology generation disabled Morphed directories exist in site Site details Too few global catalog servers in site

Active Directory Topology

Viewing Active Directory forest topology Viewing alerts Customizing the topology layout

Running reports Active Directory Health reports Active Directory Infrastructure reports DNS reports Security reports Certificates reports Server configuration report

Network Operations Center

Using the Network Operations Center

Viewing operations summary Viewing topology Viewing active alerts Viewing domain controllers

Managing diagrams

Adding a new diagram Editing a diagram Deleting a diagram

Managing profiles

Adding a new profile Editing profile settings Deleting a profile

DFSRS USN records accepted

Detects that there is heavy file replication traffic.

•

Performance counters

•

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 and the user must be a part of the Performance Logs user group.

Tests the DFSR USN records accepted performance counter on a domain controller to see if the value of this performance counter goes above the configured threshold for a period exceeding the configured duration.

Replication is triggered by entries to the NTFS update sequence number (USN) change journal. A high value on this counter, such as one every five seconds, indicates heavy replication traffic and may result in replication latency.

DFSRS working set

Indicates that the working set allocated to the DFS Replication service is too high.

•

Performance Counters

•

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 and the user must be a part of the Performance Logs user group.

Tests the DFSRS working set performance counter on the domain controller for the DFSR service to see if the value in the performance counter goes above the configured threshold for a period exceeding the configured duration.

Review the system configuration and tune the environment to optimize DFSRS performance as described in these references:

•

Common DFSR Configuration Mistakes and Oversights

Domain controller relative identifier (RID)

Indicates that the available pool of relative identifiers (RIDs) on the selected domain controller is less than or equal to the configured threshold.

•

•

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.

Tests the RID pool assigned to the domain controller to see if the number of RIDs available to the server goes below the threshold.

All security principals in the Windows® NT Security Architecture are assigned a unique security ID (SID). The SID is made up of a domain identifier and a RID. RIDs are sequential numbers issued by the domain each time a new security principal (for instance a user object) is created in that domain.

Because each domain controller can create security principals, Active Directory® breaks the available range of RIDs into allocation pools that it assigns to each domain controller. Active Directory assigns one domain controller in each domain to be responsible for allocating RID pools to all of the other domain controllers in the domain; this is the RID Operations Master. When a domain controller uses up its allocation, it requests a new range from the RID Operations Master.

If a domain controller has a problem contacting the RID Operations Master, the domain controller can actually use up its entire allocation of RIDs, and be unable to create new security principals, which can result in failures when adding new users, services, and domain controllers to the domain.

Contact your Microsoft® Windows® support representative.

Domain controller responsive

Indicates if the domain controller is responsive.

•

•

Supported on: Windows Server 2016, Windows Server 2019, and Windows Server 2022

•

Required permissions: Domain user privilege required.

If Active Administrator® Data Service (ADS) can connect to TCP port 135, the domain controller is reponsive.

If the domain controller is unresponsive, one or more of the following may be the reason:

•

The indicated server is not actually a domain controller.

•

The domain controller no longer has connectivity to the network.

•

The DNS records for the domain controller are incorrect.

•

Active Directory® on the domain controller has failed in some way.

•

Active Directory on the domain controller is overloaded and is taking too long to respond.

•

The domain controller is not running.

•

Make sure the indicated server is actually a domain controller. If it is not, run NTDSUTIL and select the metadata cleanup option to clean up the erroneous objects in the directory.

•

Make sure the domain controller is running. If the domain controller is not running, start it.

•

Ping the domain controller to see if there is connectivity. If there is not, fix that problem. The problem may be that DNS has the incorrect address or that the IP stack for the domain controller is misconfigured.

•

Check the LDAP response time for the domain controller. If it is too high, you may need to add another domain controller for the same domain in the same site.

If the domain controller is also a global catalog, you may need to add another global catalog to the site.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación

© ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center