Agent Site Detection is broke
I'm trying to install and use SCCM 2007 SP1, with very, very little luck. First, schema extensions are out of the question. Second, so are any AD modifications such as creating any SCCM objects. This is a test environment, too. Due to firewall issues, I am trying to manually install an agent on a server. I'm using ccmsetup /mp:<server> smssitecode=<id>. The client will install, but whenI click on the advanced tab there is no site code listed. Discovery of the site code also fails. What's going on? I told it the site code and MP so why on earth can't it talk to my MP?
June 12th, 2008 10:15pm

Do you have a SLP registered in WINS? Maybe this will help you: http://technet.microsoft.com/en-us/library/bb932178(TechNet.10).aspx
Free Windows Admin Tool Kit Click here and download it now
June 12th, 2008 10:41pm

Well I'm trying to manually set the site code. In the SCCM SP1 client I get "failed to update site assignment" when I manually type it in. I don't care about auto-discovery in this environment..I'll be manually installing the client anyways.
June 12th, 2008 11:04pm

The flow chart covers manual assignment too.
Free Windows Admin Tool Kit Click here and download it now
June 12th, 2008 11:06pm

Yes, and it's not working.
June 12th, 2008 11:08pm

What does clientlocationservices.log say on the client???? If Configuration Manager 2007 clients successfully install but fail to assign to a site, a likely reason is that the check for site compatibility failed during the assignment process. Solution Ensure that clients have a mechanism to check for site compatibility. This is achieved in one of two ways: Active Directory Domain Services is extended for Configuration Manager 2007, and clients belong to this forest. Clients can find a server locator point that's published in WINS, or they are reinstalled and assigned to a server locator point during installation. How Manual Site Assignment Works Clients can be manually assigned to a site using the following two methods: A client installation property which specifies the site code. Specifying the site code in Configuration Manager in the computer's Control Panel. Note If you manually assign a client computer to a Configuration Manager 2007 site code that does not exist, site assignment will fail. The client will remain installed but unmanaged until it is assigned to a valid Configuration Manager 2007 site.
Free Windows Admin Tool Kit Click here and download it now
June 12th, 2008 11:12pm

John Marcum wrote: What does clientlocationservices.log say on the client??? Actually it's LocationServices.log or ClientLocation.log ...
June 13th, 2008 10:24am

Thanks, I knew that log file name didn't sound right I was just being lazy and didn't want to look it up
Free Windows Admin Tool Kit Click here and download it now
June 13th, 2008 2:23pm

Do I have tosetup either AD or WINS SLP information? Neither is really a choice for me. I can't see why just telling it my MP and site during the install is insufficient. Why must it be so difficult? SCOM agents functions just fine by telling it the RMS server. <![LOG[Assigning to site 'AAA']LOG]!><time="10:05:32.096+300" date="06-13-2008" component="LocationServices" context="" type="1" thread="144" file="lsad.cpp:3334"><![LOG[LSVerifySiteVersion : Verifying Site Version for <AAA>]LOG]!><time="10:05:32.096+300" date="06-13-2008" component="LocationServices" context="" type="1" thread="144" file="lsad.cpp:5279"><![LOG[LSGetSiteVersionFromAD : Failed to retrieve version for the site 'AAA' (0x80004005)]LOG]!><time="10:05:34.002+300" date="06-13-2008" component="LocationServices" context="" type="3" thread="144" file="lsad.cpp:5081"><![LOG[Attempting to retrieve SLPs from AD]LOG]!><time="10:05:34.018+300" date="06-13-2008" component="LocationServices" context="" type="1" thread="144" file="lsad.cpp:2261"><![LOG[Failed to resolve 'SMS_SLP' to IP address from WINS]LOG]!><time="10:05:39.096+300" date="06-13-2008" component="LocationServices" context="" type="3" thread="144" file="lswins.cpp:324"><![LOG[LSGetSLP : Failed to resolve SLP from WINS, is it published]LOG]!><time="10:05:39.096+300" date="06-13-2008" component="LocationServices" context="" type="3" thread="144" file="lsad.cpp:2277"><![LOG[LSGetSiteVersionFromSLP : Unable to get the list of SLPs]LOG]!><time="10:05:39.096+300" date="06-13-2008" component="LocationServices" context="" type="3" thread="144" file="lsad.cpp:5152"><![LOG[LSVerifySiteVersion: Failed to get Site Version from AD and SLP]LOG]!><time="10:05:39.096+300" date="06-13-2008" component="LocationServices" context="" type="3" thread="144" file="lsad.cpp:5356"><![LOG[Won't send a client assignment fallback status point message because the last assignment error matches this one.]LOG]!><time="10:05:39.096+300" date="06-13-2008" component="LocationServices" context="" type="1" thread="144" file="fspclientdeployassign.cpp:201">
June 13th, 2008 6:13pm

Yes you will either have to have a SLP or your MP's in AD. Can you explain why neither of those options are possible? Just adding the SLP seems very simple and extending AD is also not a big deal, we all do it. WIth SCOM you tell your computers (servers generally) where the RMS server is and they talk to it because servers don't generally travel. ConfigMgr is generally working with workstations which tend to be more portable so by having the MP's in AD or by having a SLP the computers can always talk to the nearest server.
Free Windows Admin Tool Kit Click here and download it now
June 13th, 2008 6:35pm

Ok, by using the SMSSLP= client install option, that seems to have fixed my problem. The site code was assigned! This is just a test environment, so changes to AD are not possible. Should SCCM be approved for production use, then AD changes can be made at that time. In the mean time all configuration must be manual with no infrastructure changes.
June 13th, 2008 6:38pm

Oh, so you are testing on the live network? When you said test environment I assumed a lab off the live LAN. Good, glad to see you got it working. Please mark the question as answered.
Free Windows Admin Tool Kit Click here and download it now
June 13th, 2008 6:45pm

Hi,I am in the same situation, doing some tests in the live environment, without extending the AD-schema. I can install the client with the correct sitecode, but they do not show up in the SCM console. How can I make them visisble in the SCM? (SCM2007R2 running on Server2008)
February 18th, 2010 5:49pm

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

Other recent topics Other recent topics