Discovery identifies computer and user resources that you can manage by using Configuration Manager, and it also discovers network infrastructure in your environment. Use the information in the following sections to help you configure discovery in System Center 2012 Configuration Manager.
- How to Enable
a Discovery Method
Active Directory Discovery for Computers, Users, or Groups
Active Directory Forest Discovery
How to Enable a Discovery Method
With the exception of the Heartbeat Discovery method, you must enable all configurable discovery methods in Configuration Manager before they can discover resources on a network. You can also disable each method by using the same procedure you use to enable it.
In addition to enabling a discovery method, you might have to configure it to successfully discover resources in your environment.
|Heartbeat Discovery is enabled when you install a Configuration Manager primary site and does not have to be enabled. Keep Heartbeat Discovery enabled as this method ensures that the discovery data records (DDRs) for devices are up-to-date. For more information about Heartbeat discovery, see About Heartbeat Discovery.|
To enable a discovery method
Configure Active Directory Discovery for Computers, Users, or Groups
Use the information in the following sections to configure discovery of computers, users, or groups, by using one of the following discovery methods:
- Active Directory System Discovery
- Active Directory User Discovery
- Active Directory Group Discovery
|The information in this section does not apply to Active Directory Forest Discovery.|
While each of these discovery methods is independent of the others, they share similar options. For more information about these configuration options, see About Active Directory Discovery for Systems, Users, and Groups.
|The Active Directory polling by each of these discovery methods can generate significant network traffic. Consider scheduling each discovery method to run at a time when this network traffic does not adversely affect business uses of your network.|
Use the following procedures to configure each discovery method.
To configure Active Directory System Discovery
To configure Active Directory User Discovery
To configure Active Directory Group Discovery
Configure Active Directory Forest Discovery
To complete the configuration of Active Directory Forest Discovery, you must configure settings in two locations:
- In the Discovery Methods node, you can
enable this discovery method, set a polling schedule, and select
whether discovery automatically creates boundaries for the Active
Directory sites and subnets that it discovers.
- In the Active Directory Forests node,
you can add forests that you want to discover, enable discovery of
Active Directory sites and subnets in that forest, configure
settings that enable Configuration Manager sites to publish their
site information to the forest, and assign an account to use as the
Active Directory Forest Account for each forest.
Use the following procedures to enable Active Directory Forest discovery, and to configure individual forests for use with Active Directory Forest Discovery.
To enable Active Directory Forest Discovery
To configure a forest for Active Directory Forest Discovery
Configure Heartbeat Discovery
By default, Heartbeat Discovery is enabled when you install a Configuration Manager primary site. As a result, you only have to configure the schedule for how often clients send the Heartbeat Discovery data record (DDRs) to a management point.
Although Heartbeat Discovery is enabled by default, if it is disabled, you can re-enable it like any other discovery method. For more information, see How to Enable a Discovery Method.
|If both client push installation and the site maintenance task for Clear Install Flag are enabled at the same site, set the schedule of Heartbeat Discovery to be less than the Client Rediscovery period of the Clear Install Flag site maintenance task. For more information about site maintenance tasks, see Configure Maintenance Tasks for Configuration Manager Sites.|
To configure the Heartbeat Discovery schedule
Configure Network Discovery
Use the information in the following sections to help you configure Network Discovery.
About Configuring Network Discovery
Before you configure Network Discovery, you must understand the following:
- Available levels of Network Discovery
- Available Network Discovery options
- Limiting Network Discovery on the network
The following sections provide information about common configurations for Network Discovery. You can configure one or more of these configurations for use during the same discovery run. If you use multiple configurations, you must plan for the interactions that can affect the discovery results.
For example, you might want to discover all SNMP devices that use a specific SNMP Community name. Additionally, for the same discovery run, you might disable discovery on a specific subnet. When discovery runs, Network Discovery does not discover the SNMP devices with the specified community name on the subnet that you have disabled.
Determine your Network Topology
Limit Searches by Using Subnets
Search a Specific Domain
Limit Searches by Using SNMP Community Names
Search a Specific DHCP Server
How to Configure Network Discovery
Use the following procedures to first discover only your network topology, and then to configure Network Discovery to discover potential clients by using one or more of the available Network Discovery options.
To determine your network topology
To configure Network Discovery
How to Verify that Network Discovery Has Finished
The time that Network Discovery requires to complete can vary depending on a variety of factors. These factors can include one or more of the following:
- The size of your network
- The topology of your network
- The maximum number of hops that are
configured to find routers in the network
- The type of discovery that is being run
Because Network Discovery does not create messages to alert you when discovery has finished, you can use the following procedure to verify when discovery has finished.