System Center Configuration Manager TechCenter >
System Center Configuration Manager Forums
>
Configuration Manager General
>
Client Site Assignment Problem - Possible post SP2 Issue?
Client Site Assignment Problem - Possible post SP2 Issue?
- I've just installed SP2 on our SCCM 2007 R2 test environment and the installation completed with a state of 'unknown' for the management point. Upon checking the SMS_MP_CONTROL_MANAGER status messages I saw a few errors relating to HTTP 500 Internal Server Error. However, it seems to have managed to repair itself as there are no longer and error messages and the MP appears to be healthy. So what's the problem I hear you ask? Well...
The test environment hadn't been used for a while and so there were no clients in it. To confirm that everything was working okay I tried to install a client, which installed okay but the site code was blank. If I use the Discover button it returns the error 'Automatic site code discovery was unsuccessful. I've checked the LocationServices.log on the client and here are the entries that appear when the 'Discover' process is run:
LSGetAssignedSiteFromDirectories LocationServices 29/10/2009 17:34:21 2624 (0x0A40)
LSGetGPSiteCode LocationServices 29/10/2009 17:34:21 2624 (0x0A40)
LSGetGPSiteCode: Failed to Get Site Code from Group Policy Reg key [Software\Microsoft\SMS\Mobile Client] (80070002) LocationServices 29/10/2009 17:34:21 2624 (0x0A40)
LSJoinedToADDomain LocationServices 29/10/2009 17:34:21 2624 (0x0A40)
LSGetAssignedSiteFromAD LocationServices 29/10/2009 17:34:21 2624 (0x0A40)
Adapter {E3228ECC-B425-4176-838C-4A9A42553D3E} has 0 IPv4 address(es). LocationServices 29/10/2009 17:34:21 2624 (0x0A40)
Adapter {7AED1CF3-5FC2-4370-9069-35EA3DFFD9C9} has 1 IPv4 address(es). LocationServices 29/10/2009 17:34:21 2624 (0x0A40)
LSGetADSiteName LocationServices 29/10/2009 17:34:21 2624 (0x0A40)
Current AD site of machine is Salfords-NoHeaders LocationServices 29/10/2009 17:34:21 2624 (0x0A40)
LSGetAssignedSiteFromSLP LocationServices 29/10/2009 17:34:22 2624 (0x0A40)
LSGetSLP LocationServices 29/10/2009 17:34:22 2624 (0x0A40)
LSGetSLPFromRegistry LocationServices 29/10/2009 17:34:22 2624 (0x0A40)
LSGetSLPFromRegistry: Failed to get SLP from Registry (80004005) LocationServices 29/10/2009 17:34:22 2624 (0x0A40)
LSJoinedToADDomain LocationServices 29/10/2009 17:34:22 2624 (0x0A40)
Attempting to retrieve SLPs from AD LocationServices 29/10/2009 17:34:22 2624 (0x0A40)
LSGetSLPFromAD LocationServices 29/10/2009 17:34:22 2624 (0x0A40)
LSWinsResolveSMSName LocationServices 29/10/2009 17:34:22 2624 (0x0A40)
Failed to resolve 'SMS_SLP' to IP address from WINS LocationServices 29/10/2009 17:34:42 2624 (0x0A40)
LSGetSLP : Failed to resolve SLP from WINS, is it published LocationServices 29/10/2009 17:34:42 2624 (0x0A40)
LSGetAssignedSiteFromSLP : Unable to get the list of SLPs LocationServices 29/10/2009 17:34:42 2624 (0x0A40)
It seems odd to me that it only seems to be looking for a SLP. I don't have any SLPs because we've extended the Active Directory schema.
If I try to enter the site code manually I get the error 'Failed to update site assignment' and the following errors are logged in the ClientLocation.log file:
Setting Assigned Site ClientLocation 29/10/2009 17:28:18 2328 (0x0918)
Assigning client to site 'UKA' ClientLocation 29/10/2009 17:28:18 2328 (0x0918)
Unable to verify the sitecode 'UKA', AD schema is not extended or SLP is not present. Cannot continue site assignment. ClientLocation 29/10/2009 17:28:39 2328 (0x0918)
I've checked the Systems Management container in AD and it exists with the correct permissions and the MP object appears within it. The sitecomp.log also confirms that the MP is successfully published to AD. I've also followed Microsoft's MP troubleshooting guide and everything appears to check out (http://<ServerName>/sms_mp/.sms_aut?mplist & http://<ServerName>/sms_mp/.sms_aut?mpcert return information without any errors).
I'm now stuck. I really don't know if this was caused by the SP2 install but I need to get this working before I can install SP2 in our live environment. Anyone have any suggestions on what further steps I should take to troubleshoot this?
Regards,
Robin
All Replies
- I don't think this is an SP2 issue but who knows. The first things I would do would be check my boundaries. I really think it's a boundary issue but if not remove everything from the system management container then restart the server and try again.
John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum - Hi John, thanks for your reply.
I've checked the site boundaries and a boundry does exist for the subnet listed in System Properties on the client. As per you suggestion, I deleted the contents of the System Management container, restarted the server and then confirmed that the contents were re-created. I've also gone through the article http://technet.microsoft.com/en-us/library/bb693614.aspx and confirmed that all of the correct information has been published to AD.
Incidentally, if I run the Discover process on the server it completes successfully.
Any other ideas? - Out of curiosity is the sunet used as a boundary also in the "Salfords-NoHeaders" AD site? If not exactly what did you specify as the subnet boundaries? (subnet and mask)
John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum - The boundary is set using the Subnet ID '10.26.13.128'.
- The question should be, is that the subnet that the client thinks it is on? You can't just create your own subnet in Boundaries, it has to be a valid subnet (as identified by the client).
So what I'd do is to open the discovery properties of the client in the All Systems collection, and look for the value for IP Subnet. That is what you need to use as your subnet. If the client does not show 10.26.13.128 there, you can't use it as your Boundary.
Wally Mead It's been my experience that using anything other than a class C as a subnet doesn't generally work so I tend to use IP ranges when I am not using a full class C. What's the IP and subnet mask on the client?
John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum- The subnet listed in the discovery data is 10.26.13.128. The actual IP address and subnet are 10.26.13.159\255.255.255.128.
I have changed the boundary configuration to use an address range instead but the problem remains (we use the subnet ID in our live environment and it has always worked fine). Just to be sure I moved the computer into another subnet (a class C which was also defined within the site boundaries) and it still failed. - As Wally stated you can use the subnet ID as long as the clients report that they are on that subnet but it can be confusing sometimes so jut to rule things out using the range is a good idea. Since we have ruled out bounaries we should look at other things. Can you send me the mp logs? They all start with MPxxxx.log. Management point log files are stored in the SMS_CCM\LOGS folder on the management point computer.
May as well send me the client logs too, email them all to john marcum at gmail dot com. (no spaces or anything)
John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum - Log files sent.
Thanks again for looking at this.
Robin - Can you please verify that the schema has been extended and that the System Management container is populated?
John Marcum | http://www.TrueSec.com/en/Training.htm | http://myitforum.com/cs2/blogs/jmarcum
