I suddenly have a large group of machines that are no longer reporting correctly to SCCM. In the "All Systems" collection under the "Client" column I see a bunch of "No" that used to say "Yes". The only commonality I see among them is that our desktop guys are doing some BIOS upgrades on these machines. Would this confuse SCCM to the point where it will not update correctly in the site database? I imagine a new GUID or some type of identifer might be generated after the upgrade. Repairing the client doesn't seem to work. I have to uninstall/reinstall but that's going to be very labor intensive. Checling logs on the clients I find: ClinetIDManager log. This same error repeats over and over again: <![LOG[RegTask: Failed to refresh site code. Error: 0x80004005]LOG]!><time="09:51:52.066+240" date="05-23-2011" component="ClientIDManagerStartup" context="" type="3" thread="3268" file="regtask.cpp:172"> <![LOG[RegTask: Initial backoff interval: 1 minutes]LOG]!><time="09:52:58.072+240" date="05-23-2011" component="ClientIDManagerStartup" context="" type="1" thread="3268" file="regtask.cpp:1830"> <![LOG[RegTask: Reset backoff interval: 257 minutes]LOG]!><time="09:52:58.072+240" date="05-23-2011" component="ClientIDManagerStartup" context="" type="1" thread="3268" file="regtask.cpp:1831"> <![LOG[Already refreshed within the last 10 minutes, Sleeping for the next 8 minutes before reattempt.]LOG]!><time="09:52:58.103+240" date="05-23-2011" component="ClientIDManagerStartup" context="" type="1" thread="3268" file="regtask.cpp:146"> LocationServices Log. This error also repeats over and over again: <![LOG[Won't send client assignment fallback status point message because last assignment message was sent too recently.]LOG]!><time="09:51:42.643+240" date="05-23-2011" component="LocationServices" context="" type="1" thread="3268" file="fspclientdeployassign.cpp:184"> <![LOG[Processing pending site assignment.]LOG]!><time="09:51:42.643+240" date="05-23-2011" component="LocationServices" context="" type="1" thread="3268" file="lsad.cpp:3328"> <![LOG[Assigning to site 'HV1']LOG]!><time="09:51:42.643+240" date="05-23-2011" component="LocationServices" context="" type="1" thread="3268" file="lsad.cpp:3334"> <![LOG[LSVerifySiteVersion : Verifying Site Version for <HV1>]LOG]!><time="09:51:42.643+240" date="05-23-2011" component="LocationServices" context="" type="1" thread="3268" file="lsad.cpp:5321"> <![LOG[LSGetSiteVersionFromAD : Failed to retrieve version for the site 'HV1' (0x80004005)]LOG]!><time="09:51:42.893+240" date="05-23-2011" component="LocationServices" context="" type="3" thread="3268" file="lsad.cpp:5123"> <![LOG[Attempting to retrieve SLPs from AD]LOG]!><time="09:51:42.893+240" date="05-23-2011" component="LocationServices" context="" type="1" thread="3268" file="lsad.cpp:2261"> <![LOG[Failed to resolve 'SMS_SLP' to IP address from WINS]LOG]!><time="09:51:52.066+240" date="05-23-2011" component="LocationServices" context="" type="3" thread="3268" file="lswins.cpp:324"> <![LOG[LSGetSLP : Failed to resolve SLP from WINS, is it published]LOG]!><time="09:51:52.066+240" date="05-23-2011" component="LocationServices" context="" type="3" thread="3268" file="lsad.cpp:2277"> <![LOG[LSGetSiteVersionFromSLP : Unable to get the list of SLPs]LOG]!><time="09:51:52.066+240" date="05-23-2011" component="LocationServices" context="" type="3" thread="3268" file="lsad.cpp:5194"> <![LOG[LSVerifySiteVersion: Failed to get Site Version from AD and SLP]LOG]!><time="09:51:52.066+240" date="05-23-2011" component="LocationServices" context="" type="3" thread="3268" file="lsad.cpp:5398"> <![LOG[Won't send a client assignment fallback status point message because the last assignment error matches this one.]LOG]!><time="09:51:52.066+240" date="05-23-2011" component="LocationServices" context="" type="1" thread="3268" file="fspclientdeployassign.cpp:201"> Not sure what it's trying to get from WINS... Most other logs stopped updating in late April. On this particular workstation it was April 22nd. An y ideas? Thanks!

It is obviously related to the BIOS and not to ConfigMgr. I don't think the BIOS upgrade will change the GUID of the SCCM client. The WINS message in the log can be ignored. Follow me through my blog and Twitter!

It is obviously related to the BIOS and not to ConfigMgr. I don't think the BIOS upgrade will change the GUID of the SCCM client. The WINS message in the log can be ignored. Follow me through my blog and Twitter!

Hi, From your logs, the client can’t locate the site code from AD, and the SLP isn’t working, so it can’t figure out how to assign to the site. It could be an issue with boundaries, and the site can’t publish information to AD for some reason. Please check the sitecomp.log on the site server to see if there’s any error for publishing to AD. You may try to add the IP range as boundary for one of the machine with problem and monitor sitecomp.log to see if the AD is getting updated successfully. Regards, Sabrina This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |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.