Export (0) Print
Expand All

How to Verify That Site Information Is Published to Active Directory Domain Services

Updated: March 1, 2010

Applies To: System Center Configuration Manager 2007, System Center Configuration Manager 2007 R2, System Center Configuration Manager 2007 R3, System Center Configuration Manager 2007 SP1, System Center Configuration Manager 2007 SP2

After you enable a Configuration Manager site to publish site information, you can verify that the site information is published to the Active Directory Domain Services by using the Active Directory Users and Computers administrative tool or the Active Directory Service Interfaces Editor (ADSI Edit).

noteNote
For more information about how to install and use ADSI Edit, see ADSI Edit (adsiedit.msc) Overview (http://go.microsoft.com/fwlink/?LinkId=183662).

You can also verify that hierarchy manager has created the site code object by reviewing the hman.log file, and you can verify that site component manager has created the management point and server locator point information by reviewing the sitecomp.log file.

Verifying That Site Information Is Published to Active Directory Domain Services by Using Active Directory Users and Computers

Use Active Directory Users and Computers to verify that the site and related information is published to Active Directory Domain Services when you do not need to confirm the values that are associated with the individual Configuration Manager Active Directory classes and attributes.

To verify that site information is published to Active Directory Domain Services by using Active Directory Users and Computers

  1. Click Start, click Run, and enter dsa.msc to open the Active Directory Users and Computers administrative tool.

  2. Click View, and then click Advanced Features.

  3. In the console pane, expand the System container.

  4. Click the System Management container.

  5. In the results pane, verify that the site object, the management point and server locator point, and boundary information have been published for each site in the domain that has publishing enabled:

    SMS-Site-<site code>

    SMS-MP-<site code>-<site system server name>

    SMS-SLP-<site code>-<site system server name>

    SMS-<site code>-<Active Directory site name or subnet>

    noteNote
    If a site does not contain a site system server that hosts the management point or server locator point server roles, there will be no information published to Active Directory Domain Services for those roles. For example, a secondary site with publishing enabled, but without a management point server role enabled, will publish only its site code object to Active Directory Domain Services.

Verifying That Site Information Is Published to Active Directory Domain Services by Using the ADSI Edit

Use ADSI Edit to verify that the site and related information is published to Active Directory Domain Services and confirm the values that are associated with the individual Configuration Manager Active Directory classes and attributes.

To verify the creation of the site code object

  1. Click Start, click Run, and enter adsiedit.msc to run ADSI Edit.

  2. If necessary, connect to the site server's domain.

  3. In the console pane, expand the site server's domain, expand DC=<server distinguished name>, expand CN=System, and then click CN=System Management.

  4. In the results pane, right-click CN=SMS-Site-<site code>, and then click Properties.

  5. Verify that the following attributes appear:

 

Attribute Property

Syntax

Value

msSMSAssignmentSiteCode

Case-Insensitive String

<site code>

msSMSRoamingBoundaries

Case-Insensitive String

<Active Directory site name or subnets>

msSMSSiteCode

Case-Insensitive String

<site code>

noteNote
Configuration Manager 2007 does not use the msSMSSiteBoundaries attribute.

If the site object is not published or contains incorrect data, review the hman.log file in the <ConfigMgrInstallationPath>\Logs folder to identify the failure.

To verify the creation of the management point information

  1. Click Start, click Run, and enter adsiedit.msc to run ADSI Edit.

  2. If necessary, connect to the site server's domain.

  3. In the console pane, expand the site server's domain, expand DC=<server distinguished name>, expand CN=System, and then click CN=System Management.

  4. Verify that for each management point there is a
    CN=SMS-MP-<site code>-<management point computer name> object.

  5. Right-click CN=SMS-MP-<site code>-<default management point computer name>, and then click Properties.

  6. Verify that the following attributes appear:

 

Attribute Property

Syntax

Value

msSMSDefaultMP

Boolean

TRUE

msSMSMPName

Case-Insensitive String

<default management point computer name>

msSMSSiteCode

Case-Insensitive String

<site code>

If you do not have an object published for each management point, or if the information for the default management point is not correct, review the Sitecomp.log file in the <ConfigMgrInstallationPath>\Logs folder to identify the failure.

To verify the creation of the server locator point information

  1. Click Start, click Run, and enter adsiedit.msc to run ADSI Edit.

  2. If necessary, connect to the site server's domain.

  3. In the console pane, expand the site server's domain, expand DC=<server distinguished name>, expand CN=System, and then click CN=System Management.

  4. Verify that for each server locator point there is a
    CN=SMS-SLP-<site code>-<server locator point computer name> object.

  5. Right-click CN=SMS-SLP-<site code>-<server locator point computer name>, and then click Properties.

  6. Verify that the following attributes appear:

 

Attribute Property

Syntax

Value

msSMSMPName

Case-Insensitive String

<default management point computer name>

msSMSSiteCode

Case-Insensitive String

<site code>

If you do not have an object published for the server locator point or if the information for the server locator point is not correct, review the Sitecomp.log file in the <ConfigMgrInstallationPath>\Logs folder to identify the failure.

See Also

For additional information, see Configuration Manager 2007 Information and Support.
To contact the documentation team, email SMSdocs@microsoft.com.
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft