Unable to Retreive AD Site Membership

[Mikey C]

We have had SCCM up and running for a few months now. Very few problems, ultimately it is excellent (especially in comparison to LANDesk which we found to be dreadful and utterly unreliable - steer clear!!!).

 

We are in the process of setting up AD sites so that we can more effectively handle the differences in bandwidth available over the different links (until now we have had to apply differetn BITS settings by OU, but that has its obvious limitations when roaming laptop users).

 

However, since creating our first site (using a subnet), the SCCM client will not install using WSUS with the error message listed in the log below. The only boundary we have setup is Default-First-Site-Name (if that makes any difference), but the PC we are testing the client installation is not in the new site.

 

1. What have we not configure correctly?

2. Can you not tell WSUS to use an MP in the command line?

 

 

A typical succcessful log

==========[ ccmsetup started in process 2336 ]==========

Version: 4.0.6487.2000

GetAdaptersAddressess entry point is supported.

DhcpGetOriginalSubnetMask entry point not supported.

Adapter {97300C4F-87EF-4EB5-A7C5-F4FE06CF6620} is DHCP enabled. Checking quarantine status.

Current AD site of machine is Default-First-Site-Name

Attempting to query AD for assigned site code

Executing query (&(ObjectCategory=MSSMSRoamingBoundaryRange)(|(&(MSSMSRangedIPLow<=174336851)(MSSMSRangedIPHigh>=174336851))))

Executing query (&(ObjectCategory=mSSMSSite)(|(mSSMSRoamingBoundaries=10.100.43.0)(mSSMSRoamingBoundaries=Default-First-Site-Name)))

LSGetAssignedSiteFromAD : Trying to Assign to the Site <S02>

The MP name retrieved is 'columbus.ad.lancscc.net' with version '6487l' and capabilities '<Capabilities SchemaVersion="1.0"></Capabilities>'

Retrieving client operational settings from AD.

ClientOperationalSettings search filter is '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=S02))'

Command line: "C:\WINDOWS\SoftwareDistribution\Download\Install\ccmsetup.exe"

 

UNSUCCESSFUL INSTALLATION LOG

==========[ ccmsetup started in process 2776 ]==========

Version: 4.0.6487.2000

GetAdaptersAddressess entry point is supported.

DhcpGetOriginalSubnetMask entry point not supported.

Adapter {AD57F1FD-7260-4877-AA76-071695B8CC46} is DHCP enabled. Checking quarantine status.

Unable to retrieve AD site membership

Attempting to query AD for assigned site code

Executing query (&(ObjectCategory=MSSMSRoamingBoundaryRange)(|(&(MSSMSRangedIPLow<=174336897)(MSSMSRangedIPHigh>=174336897))))

Executing query (&(ObjectCategory=mSSMSSite)(|(mSSMSRoamingBoundaries=10.100.43.0)))

Command line: "C:\WINDOWS\SoftwareDistribution\Download\Install\ccmsetup.exe"

Ccmsetup was run without any user parameters specified. Assume AUTO sitecode and run without registering ccmsetup as a service.

CCMHTTPPORT: 80

CCMHTTPSPORT: 443

CCMHTTPSSTATE: 2147483648

CCMHTTPSCERTNAME:

FSP:

No MP or source location has been explicitly specified. Trying to discover a valid content location...

Current directory is not a valid source location.

Looking for an MP source through SLP...

IPv6 entry points already initialized.

DHCP entry points already initialized.

Adapter {AD57F1FD-7260-4877-AA76-071695B8CC46} is DHCP enabled. Checking quarantine status.

Unable to retrieve AD site membership

Attempting to query AD for assigned site code

Executing query (&(ObjectCategory=MSSMSRoamingBoundaryRange)(|(&(MSSMSRangedIPLow<=174336897)(MSSMSRangedIPHigh>=174336897))))

Executing query (&(ObjectCategory=mSSMSSite)(|(mSSMSRoamingBoundaries=10.100.43.0)))

Couldn't find an MP source through SLP.

No valid source or MP locations could be indentified to download content from.Ccmsetup.exe cannot continue.

Invalid ccmsetup command line: "C:\WINDOWS\SoftwareDistribution\Download\Install\ccmsetup.exe"

A Fallback Status Point has not been specified. Message with STATEID='100' will not be sent.

A Fallback Status Point has not been specified. Message with STATEID='307' will not be sent.

[Eswar Koneti]

For unsuccessfull clients,looks like the client ran with no parameters specified or invalid parameters, it is assuming AUTO assignment.That means it needs to find a boundary match in order to identify a suitable site and then look for that site's default MP.

 

Can you check,if the IP address/subnet for the Unsuccessful client machines are added to the SCCM Boundaries ?

 

To fix this you will either need to provide matching boundaries to use AUTO assignment or will need to provide the site code on the command line.

 

Also check if site components are throwing errors attempting to publish to AD (status system) ?

Try running the ccmsetup like CCMSetup.exe /mp:SMSMP01 /logon SMSSITECODE=C01 (http://technet.microsoft.com/en-us/library/bb680980.aspx)

 

For more information about client Assignment http://technet.micro...y/bb681005.aspx

[Mikey C]

For unsuccessfull clients,looks like the client ran with no parameters specified or invalid parameters, it is assuming AUTO assignment.That means it needs to find a boundary match in order to identify a suitable site and then look for that site's default MP.

 

Can you check,if the IP address/subnet for the Unsuccessful client machines are added to the SCCM Boundaries ?

 

To fix this you will either need to provide matching boundaries to use AUTO assignment or will need to provide the site code on the command line.

 

Also check if site components are throwing errors attempting to publish to AD (status system) ?

Try running the ccmsetup like CCMSetup.exe /mp:SMSMP01 /logon SMSSITECODE=C01 (http://technet.microsoft.com/en-us/library/bb680980.aspx)

 

For more information about client Assignment http://technet.micro...y/bb681005.aspx

 

Thanks for your quick reply -

 

We want to install the client using WSUS in which you cannot specify the site code (as far as i know?), so how else could we get around that?

[Peter van der Woude]

Then you to, or Extend the AD, or apply a GPO. Take a look here for more information: http://technet.microsoft.com/en-us/library/bb633194.aspx

[anyweb]

Thanks for your quick reply -

 

We want to install the client using WSUS in which you cannot specify the site code (as far as i know?), so how else could we get around that?

 

as Peter says, extend the active directory schema as explained here - http://www.windows-noob.com/forums/index.php?/topic/488-how-can-i-extend-the-active-directory-schema-in-windows-server-2008/

[Mikey C]

as Peter says, extend the active directory schema as explained here - http://www.windows-noob.com/forums/index.php?/topic/488-how-can-i-extend-the-active-directory-schema-in-windows-server-2008/

 

Thanks both.

 

We had already extended the schema when we first setup SCCM and successfully tested that it was working (WSUS Client Installs work fine).

 

The problem has neen identified with AD sites, as it has become clear that in order to setup AD Sites based on subnets - you must set them up in their entirety in the first place. For any undefined subnet that a PC is in, the PC will fail to correctly determine the site and will not install the client.

 

So for an organisation with hundreds of subnets - sites is a difficult 'solution' to impliment!!

[Peter van der Woude]

Correct, using AD Sites is only a solution if they are setup in the AD Sites and Services.