Error: "Failed to retrieve Default Management Point from SLP"
I have some machines (maybe 5-7% of the fleet) that are not reporting software inventory information to SCCM. The only errors I can find in the SCCM logs on an affected machine are the following: ------------------------------------------- 12/10/2010 11:44:04 AM Failed to retrieve Default Management Point from SLP 12/10/2010 11:44:04 AM Unable to retrieve default management point from AD, DNS and SLP. Client is in Native mode which prevents failover to WINS for lookup. 12/10/2010 11:44:21 AM Failed to resolve 'SMS_SLP' to IP address from WINS 12/10/2010 11:44:21 AM LSGetSLP : Failed to resolve SLP from WINS, is it published 12/10/2010 11:44:21 AM LSGetManagementPointForSiteFromSLP : No Default MP returned from SLP for site <CEN> 12/10/2010 11:44:21 AM Failed to retrieve Default Management Point from SLP 12/10/2010 11:44:21 AM Unable to retrieve default management point from AD, DNS and SLP. Client is in Native mode which prevents failover to WINS for lookup. 12/10/2010 11:44:21 AM There are no management points to send the MPLIST1 request to. 12/10/2010 11:44:21 AM Failed to retrieve MP List for site code 'CEN' 12/10/2010 11:44:21 AM Failed to update security settings over AD with error 0x80004005. SCCM is in native mode, and the schema was extended successfully for SCCM some months back. The SLP for site CEN is published in the AD, and can be viewed manually with adsiedit.msc. The agents on most machines are working OK. Re-installation of the agent that has the above errors "resolves" its issues, but I need to understand what the underlying cause of the problem is. Thanks in advance.
October 11th, 2010 9:32pm
Are these workgroup clients? What installatio method was used to install them and what installation method is being used to re-install them?Jason | http://myitforum.com/cs2/blogs/jsandys | http://blogs.catapultsystems.com/jsandys/default.aspx | Twitter @JasonSandys
October 11th, 2010 11:23pm
They were installed via a mixture of push installation from the console (to upgrade from SMS 2003), as well as installation at build time using ccmsetup.exe with a fully unattended commandline. All machines are domain members. Machines are not imaged, so no issue with dup GUIDs. Re-installation as above - either via the console or using ccmsetup. Have noticed that attempting repair of the client initiates the cycle of log messages above. Netmon shows no attempt by the client to make any outbound connections whatsoever in the timeframe of the logged events. Cheers
October 12th, 2010 1:38am
Hi, I am facing the same issue. Any solutions??
August 31st, 2012 11:15am
What issue? You need to start a new thread and provide exact details of what you are experiencing and your site configuration along with troubleshooting steps you've done already.Jason | http://blog.configmgrftw.com
August 31st, 2012 12:28pm