立即与支持人员聊天
与支持团队交流

Enterprise Reporter 3.2.2 - Configuration Manager User Guide

Product Overview Understanding Discoveries Creating Discoveries
Step 1. Create the Discovery Step 2. Choose what to include in your discovery (Scopes) Step 2a. Choose scopes for your discoveries
Choosing your Active Directory Scopes Choosing your Computer Scopes Choosing Your Exchange Scopes Choosing Your File Storage Analysis Scopes Choosing Your Microsoft SQL Scopes Choosing Your NTFS Scopes Choosing Your Registry Scopes
Step 2b: Choose scopes for your Office 365 discoveries Step 3. Schedule your Discovery Step 4: Review the summary
Managing Discoveries Configuring the Configuration Manager
Starting the Configuration Manager Finding Answers and Getting Help An Overview of Enterprise Reporter Communications and Credentials Required Logged In User Details Setting Up Your First Collection Computers Modifying your Deployment Improving the Performance of Your Discoveries What does the status of a node or cluster indicate? Using the Credential Manager Changing the Credentials used by the Enterprise Reporter Server Configuring Global Settings Global Discovery Settings
Troubleshooting Issues with Enterprise Reporter Appendix: PowerShell cmdlets Appendix: Encryption Key Manager Appendix: Log Viewer

AD Discovery: Optionally refine your scope list with exclusions

AD Discovery: Optionally refine your scope list with exclusions

Active Directory® excluded objects are resolved after included objects. For example, if you include an object that exists below an excluded object in the AD structure, it will not be collected, as the exclusion will take precedence. For more information, see Using the Browser to Include and Exclude Scopes .

To explicitly exclude objects from your selected scope
1
Click Add.
2
Expand the treeview to locate the object you want to exclude.
You can press Ctrl to select multiple objects.
3
Click Exclude. 

AD Discovery: Optionally select one or more domain controllers

In order to enumerate your domain, Enterprise Reporter looks to domain controllers. Depending on the domain controllers chosen, the time it takes to perform the collection may vary. You can either allow Enterprise Reporter to choose the first available domain controller returned by Active Directory®, or you can select one or more that will optimize collection time. In this case, select one or more domain controllers that are located physically close to the cluster you assigned to the discovery, or one or more that you know are fast computers.

To set the domain controllers used to enumerate a domain
1
Add your scopes.
For more information, see AD Discovery: Include scopes or AD Discovery: Optionally refine your scope list with exclusions .
2
In the scopes list for the included domain you want to configure, click "..."
3
To use the first available domain controller returned by Active Directory®, select Automatic selection.
- OR -
To assign one or more specific domain controllers, choose Select available domain controllers, and then select the domain controllers from the list, or choose Select Available Domain Controllers from current Sub-Net and then select the domain controllers from the list.
4
Click OK.

AD Discovery: Decide what to collect from any domain in the discovery

When you run an Active Directory® discovery, it is resolved to a list of domains. You can collect a variety of information from these domains. The basic domain information, including a list of all OUs in the domain, is always collected.

The following table outlines the additional information that can be collected. Collecting additional information impacts discovery performance. Options with a high performance cost will slow discovery performance more than options with a medium or low performance cost.

 

Table 8. Active Directory Discovery: Optionally collect information for the following objects
Option
Notes
Performance Cost

Users

 

Medium

•
Token groups count

Collect the count of items in the TokenGroups attribute to monitor access token sizes and to assist with group cleanup and consolidation projects.

High

•
Query all domain controllers for last logon

The Active Directory® LastLogonTimestamp attribute is always collected for users and computers and can be used to determine if a user or computer account has recently logged onto the domain. To determine the actual time of the most recent logon for a user or computer account, enable this option to query all domain controllers for the LastLogon attribute. The LastLogon attribute is subsequently used to calculate the total number of times each domain user has successfully logged on (Number of Logons field).

There are two known cases where the Number of Logons total may be inaccurate.

•
Since the LastLogon attribute is not replicated, domain controllers that are retired, and are therefore not collected, may have contained logons for users that would be missing from the count.
•
The attribute can track up to 65535 logons. After this limit has been reached, it becomes an inaccurate indicator of user activity on this domain controller.

High

•
In addition, you may choose to collect remote desktop information for the accounts collected.

 

Medium

•
You may also choose to collect thumbnail photographs of domain users.

 

Medium

Groups and members

When this option is selected, groups and members are collected from the target domain.

High

•
Include members from foreign domains

When this option is selected, all members of the group are collected, even if those members are from other domains or other forests.

 

Medium

•
Collect nested groups and members from foreign domains

 

If Include members from foreign members is enabled, you can select this option to collect all nested groups and their members from foreign domains.

 

High

Computers

 

Medium

Domain Controllers

 

Low

Permissions

In addition to collecting Active Directory® objects, you may also choose to collect Active Directory® object permissions.

High

Contacts

 

Low

Trusts

 

Low

Sites

 

Low

Deleted Objects

 

Medium

Service Accounts

 

Low

Active Roles Virtual Attributes and Active Roles Server

When this option is selected, Active Roles virtual attributes are collected from all targets managed by the Active Roles Server.

NOTE: Collecting Active Roles attributes for users, groups, computers, and organizational units can significantly increase the collection time. Some attributes that are known to increase collection time are:
•
edsaDialinAccessPermissions
•
edsaDialinApplyStaticRoutes
•
edsaDialinApplyStaticIP
•
edsaDialinCallbackNumber
•
edsaDialinCallbackOptions
•
edsaDialinCallerID
•
edsaDialinStaticIP
•
edsaDialinStaticRoutes
•
edsaDialinVerifyCallerID

If Active Roles Virtual Attributes is enabled, you must specify the Active Roles Server that manages the target domains. Optionally, you may supply credentials to be used for contacting the Active Roles Server during collection. If these credentials are left empty, the node credentials or alternate credentials specified in on the Name page of the discovery in Step 1. Create the Discovery will be used.

High

The following options further refine how collection tasks are handled.When collecting additional attributes, especially ones with a high performance cost, consider enabling these performance options to help improve collection performance.

 

Table 9. Active Directory Discovery: Additonal Performance Options
Options
Notes

Performance Options

 

•
Do not collect object counts

When this option is cleared, the discovery collects the total number of users, groups, contacts, computers, and organizational units. To collect summary counts of these objects and to be able to display them, reports such as Domain Summary, require this option to be cleared.

•
Create multiple tasks for each domain

A collection task is always created for each domain in an Active Directory® discovery. Selecting this option will create individual tasks for domains, users, groups, computers, domain controllers, permissions, and deleted objects. This allows tasks to be load balanced using multiple nodes.

Choosing your Computer Scopes

Computer scopes determine what information will be collected when you run the discovery. There are several steps you should take to properly design your discovery.

See also:

•
Computer Discovery: Include scopes
•
Computer Discovery: Optionally refine your scope list with exclusions
•
Computer Discovery: Decide what to collect from any computer in the discovery
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级