Client can't determine site
I have a two trier (Central & Primary sites) SP2 R2 site running mixed mode. Schema has been extended and verified. MP's are installed, publishing enabled both to AD & DNS. Site boundries have been verified (using AD site, double checked network assignments). When I install SCCM client it does not find configmgr site. There is no fallback status point. When I run manual discover, I get this in the locationservices.log: <![LOG[A Fallback Status Point has not been specified. Message with STATEID='500' will not be sent.]LOG]!><time="17:14:54.102+300" date="11-23-2010" component="LocationServices" context="" type="1" thread="2988" file="fspclientdeployassign.cpp:53"> <![LOG[Current AD site of machine is Cambridge]LOG]!><time="17:14:54.211+300" date="11-23-2010" component="LocationServices" context="" type="1" thread="2988" file="lsad.cpp:457"> <![LOG[Attempting to retrieve SLPs from AD]LOG]!><time="17:14:54.211+300" date="11-23-2010" component="LocationServices" context="" type="1" thread="2988" file="lsad.cpp:2261"> <![LOG[Failed to resolve 'SMS_SLP' to IP address from WINS]LOG]!><time="17:15:03.676+300" date="11-23-2010" component="LocationServices" context="" type="3" thread="2988" file="lswins.cpp:324"> <![LOG[LSGetSLP : Failed to resolve SLP from WINS, is it published]LOG]!><time="17:15:03.676+300" date="11-23-2010" component="LocationServices" context="" type="3" thread="2988" file="lsad.cpp:2277"> <![LOG[LSGetAssignedSiteFromSLP : Unable to get the list of SLPs]LOG]!><time="17:15:03.676+300" date="11-23-2010" component="LocationServices" context="" type="3" thread="2988" file="lsad.cpp:1986"> <![LOG[A Fallback Status Point has not been specified. Message with STATEID='606' will not be sent.]LOG]!><time="17:15:03.676+300" date="11-23-2010" component="LocationServices" context="" type="1" thread="2988" file="fspclientdeployassign.cpp:53"> <![LOG[Current AD site of machine is Cambridge]LOG]!><time="17:20:21.494+300" date="11-23-2010" component="LocationServices" context="" type="1" thread="3276" file="lsad.cpp:457"> <![LOG[Attempting to retrieve SLPs from AD]LOG]!><time="17:20:21.494+300" date="11-23-2010" component="LocationServices" context="" type="1" thread="3276" file="lsad.cpp:2261"> <![LOG[Failed to resolve 'SMS_SLP' to IP address from WINS]LOG]!><time="17:20:30.665+300" date="11-23-2010" component="LocationServices" context="" type="3" thread="3276" file="lswins.cpp:324"> <![LOG[LSGetSLP : Failed to resolve SLP from WINS, is it published]LOG]!><time="17:20:30.665+300" date="11-23-2010" component="LocationServices" context="" type="3" thread="3276" file="lsad.cpp:2277"> <![LOG[LSGetAssignedSiteFromSLP : Unable to get the list of SLPs]LOG]!><time="17:20:30.665+300" date="11-23-2010" component="LocationServices" context="" type="3" thread="3276" file="lsad.cpp:1986"> I ran Wireshark: Shows name query for NB SMS_SLP but none for MP. I have no SLP...shouldn't need it. Any help will be much appreciated.
November 23rd, 2010 5:30pm

Have you verified that the bondaries and ConfigMgr site information are indeed published in AD and accesible to clients? Are the clients in question part of the domain? What client installation method are you using?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
November 23rd, 2010 6:59pm

I've verified Configmgr site info per http://technet.microsoft.com/en-us/library/bb693614.aspx The site boundary has also been verified. I'm using AD site boundaries, and in fact the locationservices.log shows that the correct site is being identified. The clients are part of the domain. I have installed the client both as part of the OSD process and also by going directly to the client folder on the site server share and running ccmsetup.exe. I'm really puzzled as to why the clients aren't even looking for the MP, as evidenced by both the locationserives.log & the Wireshark sniff. I've also verified that the MP is responding with http://<MP name>/sms_mp/.sms_aut?mplist & http://<MP name>/sms_mp/.sms_aut?mpcert
November 23rd, 2010 10:58pm

What happens if you enter the sitecode manually on the client? Does the assignment work then? Which command line parameters did you use for installing the client?
Free Windows Admin Tool Kit Click here and download it now
November 24th, 2010 2:48am

Manual entry doesn't work. That's shwon in the second round attempt in the log (above). I've installed using just the straight ccmsetup.exe & also ccmsetup.exe SMSSITECODE=XXX (mysite). CCMSETUP should work since the client ought to query AD for an MP...but it doesn't appear to??!!!
November 24th, 2010 7:16am

Hi, When you attempt to discover using he control panel app, what new entries appear in the clientlocation.log? In locationservices.log, do you have any entries that start with LSVerifySiteVersion?Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Free Windows Admin Tool Kit Click here and download it now
November 25th, 2010 12:03am

The log is above and no, I don't see LSVerifySiteVersionDan Gleason
November 25th, 2010 11:37pm

Oops...on clientlocation.log, I'll need to get THAT info on SundayDan Gleason
Free Windows Admin Tool Kit Click here and download it now
November 26th, 2010 10:14am

locationservices.log does not have any entries that start with LSVerifySiteVersion. Here's a piece of it (this series just repeats): <![LOG[Current AD site of machine is Cambridge]LOG]!><time="20:58:29.924+300" date="11-27-2010" component="LocationServices" context="" type="1" thread="4180" file="lsad.cpp:457"> <![LOG[Retrieved Proxy Management Point from AD: CAM-SCCMSITE.CORP.ABTASSOC.COM]LOG]!><time="20:58:29.940+300" date="11-27-2010" component="LocationServices" context="" type="1" thread="4180" file="lsproxymp.cpp:945"> <![LOG[Unknown task LSProxyMPModificationTask in non-quarantine - ignoring.]LOG]!><time="20:58:29.956+300" date="11-27-2010" component="LocationServices" context="" type="2" thread="5116" file="scheduledcleanupendpoint.cpp:404"> <![LOG[Attempting to retrieve local MP from AD]LOG]!><time="20:58:29.956+300" date="11-27-2010" component="LocationServices" context="" type="1" thread="4180" file="lsad.cpp:3778"> <![LOG[Current AD site of machine is Cambridge]LOG]!><time="20:58:29.956+300" date="11-27-2010" component="LocationServices" context="" type="1" thread="4180" file="lsad.cpp:457"> <![LOG[Retrieved local Management Point from AD: CAM-SCCMSITE.CORP.ABTASSOC.COM]LOG]!><time="20:58:29.956+300" date="11-27-2010" component="LocationServices" context="" type="1" thread="4180" file="lsad.cpp:3790"> <![LOG[Attempting to retrieve default management point from AD]LOG]!><time="00:57:46.163+300" date="11-28-2010" component="LocationServices" context="" type="1" thread="5356" file="lsad.cpp:2537"> <![LOG[Retrieved Default Management Point from AD: CAM-SCCMSITE.CORP.ABTASSOC.COM]LOG]!><time="00:57:46.273+300" date="11-28-2010" component="LocationServices" context="" type="1" thread="5356" file="lsad.cpp:2543"> <![LOG[Persisting the default management point in WMI]LOG]!><time="00:57:46.273+300" date="11-28-2010" component="LocationServices" context="" type="1" thread="5356" file="lsad.cpp:3878"> <![LOG[Persisted Default Management Point Location locally]LOG]!><time="00:57:46.273+300" date="11-28-2010" component="LocationServices" context="" type="1" thread="5356" file="lsad.cpp:3891"> <![LOG[Attempting to retrieve proxy MP from AD]LOG]!><time="00:57:46.289+300" date="11-28-2010" component="LocationServices" context="" type="1" thread="5356" file="lsproxymp.cpp:938"> <![LOG[Unknown task LSProxyMPModificationTask in non-quarantine - ignoring.]LOG]!><time="00:57:46.289+300" date="11-28-2010" component="LocationServices" context="" type="2" thread="3540" file="scheduledcleanupendpoint.cpp:404"> Dan Gleason
November 28th, 2010 10:28am

Well after many hours I believe I have this working, though I'm not yet 100% certain why. I believe the fix was adding Everyone/Read to the Systems Management container. In the middle of everything, I also lost the ability to install clients at all, receiving a WEBDAV error every time I did. In the end I've removed my MP from my Server 2008 Site Server and moved it to an R2 DP. THAT solved the install problem, and I'm now thinking this may have all been 2008/WEBDAV related all along. A bit more testing to go, but hopefully there's something in this conclusion that may help someone along the way. Happy Thanksgiving!Dan Gleason
Free Windows Admin Tool Kit Click here and download it now
November 28th, 2010 3:38pm

Do you see any error messages under System status --->component status ? SMS_site_component_Manager something similar ? You can also check if the clients are able to talk to Management point or not with URl's •http://MP_Server/sms_mp/.sms_aut?mplist - This returns a blank screen if the MP is working correctly. •http://MP_Server/sms_mp/.sms_aut?mpcert - This returns a hex string if the MP is working correctly.//Eswar Koneti @ http://eskonr.wordpress.com/
November 29th, 2010 1:42am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics