How to Verify Site Information is Published to Active Directory Domain Services

How to Verify Site Information is P...

To verify that site information is published to Active Directory® Domain Services after enabling a Configuration Manager site to publish site information, you can use the Active Directory Users and Computers administrative tool. To view the values associated with the individual Configuration Manager Active Directory classes and attributes, you can use the ADSIEdit MMC console.

Note
To open an ADSIEdit MMC console, you must first install the Microsoft Windows Server support tools. These tools are included in the support tools folder on both Windows 2000 Server and Windows Server 2003 CDs. To install the Windows Server support tools, navigate to \SUPPORT\TOOLS\ on the server's installation CD and run suptools.msi.

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 Site Information is Published to Active Directory® Domain Services Using the Active Directory Users and Computers Administrative Tool

To verify site information is published to Active Directory® Domain Services using the Active Directory Users and Computers Administrative tool.

Click Start, Click Run, and enter dsa.msc to open the Active Directory Users and Computers administrative tool.
Click View, and then click Advanced Features.
In the console pane, expand the System container.
Click the System Management container.

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

SMS-Site-xxx

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

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

Note
If a site does not contain a site system hosting 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 Site Information is Published to Active Directory® Domain Services Using the ADSIEdit MMC Console.

To verify creation of the site code object

Click Start, click Run, and enter adsiedit.msc to launch the ADSIEdit MMC console.
If necessary, connect to the site server's domain.
In the console pane, expand the site server's domain, expand DC=<server distinguished name>, expand CN=System, and click CN=System Management.
In the results pane, right-click CN=SMS-Site-xxx and click Properties.
Verify that the following attributes appear:

Attribute Property	Syntax	Value
msSMSAssignmentSiteCode	Case-Insensitive String	<sitecode>
msSMSRoamingBoundaries	Case-Insensitive String	<ADsite or subnets>
msSMSSiteBoundaries	Case-Insensitive String	<ADsite or subnets>
msSMSSiteCode	Case-Insensitive String	<sitecode>

Note
If the site object is not published or contains incorrect data, review the hman.log file in the \sms\logs folder to identify the failure.

To verify creation of the management point information

Click Start, click Run, and enter adsiedit.msc to launch the ADSIEdit MMC console.
If necessary, connect to the site server's domain.
In the console pane, expand the site server's domain, expand DC=<server distinguished name>, expand CN=System, and click CN=System Management.
Verify that for each management point there is a CN=SMS-MP-<sitecode>-<management point computer name> object.
Right-click CN=SMS-MP-<sitecode>-<default management point computer name> and click Properties.
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	<sitecode>

Note
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 <ConfigMgrInstallDir>\logs folder to identify the failure.

To verify creation of the server locator point information

Click Start, click Run, and enter adsiedit.msc to launch the ADSIEdit MMC console.
If necessary, connect to the site server's domain.
In the console pane, expand the site server's domain, expand DC=<server distinguished name>, expand CN=System, and click CN=System Management.
Verify that for each server locator point there is a CN=SMS-SLP-<sitecode>-<server locator point computer name> object.
Right-click CN=SMS-SLP-<sitecode>-<server locator point computer name> and click Properties.
Verify that the following attributes appear:

Attribute Property	Syntax	Value
msSMSMPName	Case-Insensitive String	<default management point computer name>
msSMSSiteCode	Case-Insensitive String	<sitecode>

Note
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 \sms\logs folder to identify the failure.