Use this tab to specify Microsoft System Center Configuration Manager 2007 publishing to Active Directory Domain Services, publishing to DNS, and child site connection security requirements.
This tab contains the following elements:
- Publish this site in Active Directory Domain Services
- Publishes Configuration Manager 2007 site data to Active
Directory Domain Services.If you clear this check box, the
following message appears:"You have chosen to disable publishing of
identity data into Active Directory. This will not delete the
identity data that is already published. You must manually delete
this data from Active Directory."
Caution After Configuration Manager 2007 site data is published in Active Directory Domain Services, the published data persists in Active Directory Domain Services unless it is manually removed. If Active Directory Domain Services publishing is disabled and the default management point is changed, existing Configuration Manager clients continue contacting the previously defined management point until Configuration Manager 2007 data is deleted from Active Directory Domain Services.
- Publish the default management point in DNS (intranet only)
- Select this check box to publish the default management point in DNS as a Service Location (SRV) record.This option is only relevant if this site system is configured with the management point role.
- Require secure key exchange between sites
- Select this check box to allow communication between this site
and Configuration Manager 2007 child sites only when keys are
securely exchanged. Secure key exchange between sites is enabled by
default for Configuration Manager 2007 sites.
Important If the Require secure key exchange between sites check box is enabled and the site is not publishing site data to Active Directory Domain Services, you must use the hierarchy maintenance tool (Preinst.exe) to manually copy the child site's public key to the parent site.
- Conflicting Records
- Lets you decide if you want Configuration Manager 2007 to create new client records when it detects duplicate hardware IDs or if you want to manually decide to merge, block, or create new records. The default is to Automatically create new client records for duplicate hardware IDs because this allows sites to upgrade from SMS 2003 without requiring manual intervention if there are many conflicting records. Selecting Manually resolve conflicting records requires more administrative overhead, but helps remove the possibility of having clients in the database with duplicate hardware IDs.
- Saves the changes and exits the dialog box.
- Exits the dialog box without saving any changes.
- Saves the changes and remains in the dialog box.
- Opens the help topic for this tab of the dialog box.
TasksHow to Manage Conflicting Records for Configuration Manager Clients
How to Verify That Site Information Is Published to Active Directory Domain Services
ReferenceSite Properties: General Tab
Site Properties: Wake On LAN Tab
Site Properties: Ports Tab
Site Properties: Site Mode Tab
ConceptsConfiguration Manager Tasks for Configuring a Single Site
How to Use the Hierarchy Maintenance Tool (Preinst.exe)