There are several other things that you can examine:
• |
• |
During an Active Directory discovery, if collection issues are related to overloaded domain controllers, disable Create multiple tasks for each domain and specify multiple domain controllers for the domain instead. For details, see AD Discovery: Optionally select one or more domain controllers . |
• |
If your discovery fails for all tasks, it is possible that your shared data location is the problem. The shared data location may no longer exist, or the node may not have adequate access to it. Check the errors on the discovery task to investigate. For more information, see Viewing Errors and Error Suppressions . If this is the issue, ensure the shared data location belonging to the cluster exists and is properly permissioned. Shared data locations are not used for Active Directory, Exchange, or NTFS discoveries. |
• |
The node may not have access to that server. Check your credentials, and change them if necessary. For details, see Node credential and alternate credential details for on-premises discoveries . |
Retrieving addresses: access is denied Retrieving cached logon count: Requested registry access is not allowed |
|
Ensure that Windows Firewall exceptions are added for File and Printer sharing (SMB-In) and Windows Management Instrumentation (WMI). |
There are several features in Enterprise Reporter to help you solve problems.
© ALL RIGHTS RESERVED. 利用規約 プライバシー Cookie Preference Center