• |
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 and the user must be a part of the Performance Logs user group. |
It is also possible that the CPU load has increased due to some pathological condition in a particular application. For instance, Active Directory® itself requires substantial CPU resources when it is processing inherited Access Control Lists (ACLs). Active Directory can also require a lot of CPU resources when it processes complex, non-indexed directory searches.
• |
Supported on: Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, and Windows Server 2019 |
• |
Required permissions: Domain user privileges with rights to list contents, create objects, read and write properties under the AATemp organizational unit in the domain root. |
Indicates the Distributed File System (DFS) namespace service is stopped.
• |
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. |
This test checks if the DFS Namespace service is running.
Use the Services MCC snap-in or another SCP application to restart the DFS Namespace 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 administer privilege is required. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 利用規約 プライバシー Cookie Preference Center