Yep, the search function led me to using the V2 SCCM tool kit MP Troubleshooter which led me to the error above which led me to searching out the error which led to no useful results which led to this post! :-) p.s. I've opened a case with microsoft on this issue as well as the other one i'm having http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/12b0af6a-8e33-4b70-ad20-5b63c4f7a34a i'll post back with results if I get them.

I found something interesting in the object under AD for system/system Management then the SMS-MP objects..a Healthy object the below attribute set ServiceBindingInformation 308201E630..etc really long alphanumberic string But my MP site has the ServiceBindingInformation set to "notset" I believe this is the problem, but not sure how to resolve it.

When I run the latest release of the MP troubleshooter I get errors after successfully connecting to the SQL DB. Notably, even though the site server is a local admin of the SQL DB which resides in the root domain I have to run the Management Point Troubleshooter under other credentials to connect to the DB. The error I get is below " Test Name: If Active Directory is extended, confirm that the management point certificate is released to Active Directory. Test Result: Failed Detail result information: Exception Message:Verify whether the firewall is blocking the query. Can not found the property:[serviceBindingInformation] in the machine. Exception Message:Object reference not set to an instance of an object."

and what about running http://siteservername/SMS_MP/.sms_aut?MPLIST if that works then you are ok.Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

It's the trusted root key that is stored there. Check sitecomp.log and hman.log if the MP can publish to AD without problems.

Have you just tried using the search function. You will find tons of useful information about mplist, mpcert and the 500 error: http://social.technet.microsoft.com/Search/en-US/?query=mplist%20mpcert%20500&rq=meta:Search.MSForums.ForumID(3b2f8eba-27e4-41c9-bc61-7799a1507e9e)+site:microsoft.com&rn=Configuration+Manager+Setup%2fDeployment+Forum

No that's the problem, the mpcert and mplist fail. The server cannot get packages pushed to it either. When I run the tool kit V2 mp troubleshooted I get the below errors which is causing the mpcert and mplist to prompt a internal 500 error. Test Name: If Active Directory is extended, confirm that the management point certificate is released to Active Directory. Test Result: Failed Detail result information: Exception Message:Verify whether the firewall is blocking the query. Can not found the property:[serviceBindingInformation] in the machine. Exception Message:Object reference not set to an instance of an object.

Hi Mr. Potter, You need to have the Site server and database in the same domain. The SMS Provider must be installed on a computer in the same domain as the site server and site database server site systems - http://technet.microsoft.com/en-us/library/bb694113.aspx Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

We've been functioning with it in a separate domain since 2007's release, in fact right now we have two functioning secondary sites in a child domain. The primary site server and DB server are in the same domain, the above errors are from a secondary site server install, I should have specified my mistake.

Looks like it is updating it correctly, when I reinstalled the site it created all the objects and the secondary site server has full control to the object System Management container exists. SMS_HIERARCHY_MANAGER 1/20/2011 9:18:06 AM 6676 (0x1A14) Searching for SMS-Site-LKE Site Object. SMS_HIERARCHY_MANAGER 1/20/2011 9:18:06 AM 6676 (0x1A14) SMS-Site-LKE exists, updating. SMS_HIERARCHY_MANAGER 1/20/2011 9:18:06 AM 6676 (0x1A14) SMS-Site-LKE successfully updated. SMS_HIERARCHY_MANAGER 1/20/2011 9:18:06 AM 6676 (0x1A14) Checking configuration information for server: LAKEELMOSRV01. SMS_SITE_COMPONENT_MANAGER 1/20/2011 10:17:02 AM 6092 (0x17CC) LAKEELMOSRV01 is the Default MP. SMS_SITE_COMPONENT_MANAGER 1/20/2011 10:17:02 AM 6092 (0x17CC) MP Configuration for LAKEELMOSRV01 is correct. SMS_SITE_COMPONENT_MANAGER 1/20/2011 10:17:02 AM 6092 (0x17CC) Installing Security settings on site system ... SMS_SITE_COMPONENT_MANAGER 1/20/2011 10:17:02 AM 6092 (0x17CC) Security settings are up to date for LAKEELMOSRV01. SMS_SITE_COMPONENT_MANAGER 1/20/2011 10:17:02 AM 6092 (0x17CC) Installing DNS publishing settings on site system ... SMS_SITE_COMPONENT_MANAGER 1/20/2011 10:17:02 AM 6092 (0x17CC) DNS publishing settings are up to date for LAKEELMOSRV01. SMS_SITE_COMPONENT_MANAGER 1/20/2011 10:17:02 AM 6092 (0x17CC) Publishing LAKEELMOSRV01(LAKEELMOSRV01.PPF.FCS.FARM) as a Management Point into Active Directory. SMS_SITE_COMPONENT_MANAGER 1/20/2011 10:17:02 AM 6092 (0x17CC) SMS-MP-LKE-LAKEELMOSRV01 successfully updated. SMS_SITE_COMPONENT_MANAGER 1/20/2011 10:17:02 AM 6092 (0x17CC)

The problem was an sms DCOM object that wasn’t being removed with the deinstall, CCMclean (unsupported on sccm 2007) with the /mp switch removed the bad object and allowed for a full install. The MP is reporting properly now. I discovered this on my own, though the microsoft tech was helpful this appears to be a rare issue that occurs on 2003 server machines after a DC demotion then a promotion