Contributed By: Cliff Hobbs [MVP SMS]
If you're having problems with your Management Points this checklist should help:

1. Load IE and in the “Address:” bar type “http://<MP_name>/sms_mp/.sms_aut?mplist” which will return a blank screen if the MP is working.
    

2. Run “http://<MP_name>/sms_mp/.sms_aut?mpcert” which will return a long string of numbers if the MP is working.
    

3. Run the “MPTroubleshooter” tool in the SMS 2003 Toolkit 2.
    

4. Verify IIS and BITS are installed.
    

5. Verify the “Distributed Transaction Coordinator” service is “Enabled” and started.
    

6. Verify the “COM+ System Application” service is “Enabled” and started.
    

7. Verify the “Task Scheduler” service is “Enabled” and started.
    

8. Verify the “Windows Management Instrumentation” service (not the “Windows Management Instrumentation Driver Extensions” service) is “Enabled” and started.
    

9. Verify the “SMS Agent Host” service is “Enabled” and started.
    

10. Verify the “World Wide Web Publishing Service” is “Enabled” and started.
     

11. Verify that the Default Web Site is running on Port 80 (unless you’ve explicitly changed it for a reason).
     

12. Verify that the Computer account of the machine the MP is running on has been added to the “SMS_SiteSystemToSQLConnection_<site_code>” group (if the MP is on a Secondary this group exists on the Parent Primary).
     

13. Verify that the Computer account of the machine the MP is running on has been added to the “SMS_SiteSystemToSiteServerConnection_<site_code>” group (if the MP is on a Secondary this group exists on the Parent Primary).
     

14. Verify that both “TCP/IP” and “Named Pipes” are present in the “Enabled protocols by order” column in the “SQL Server Client Network Utility” as detailed in the “How do I create a Proxy MP?” FAQ.
     

15. You may need to update MDAC, the process for which is detailed in Microsoft Knowledge Base Article 820910 “How to obtain the latest MDAC 2.7 service pack”.
     

16. If you are running SQL using a user account rather than under the System context you will need to update the Service Principal Name (SPN), in AD as detailed in Microsoft Knowledge Base Article 829868 “Systems Management Server 2003 Advanced Security Site with Remote SQL Does Not Connect to SQL Server”.
     

17. If the SQL Server your MP connects to is in a different Domain you may also need to update the SPN as detailed in the previous step.
     

18. Make sure you have applied the relevant SMS-specific template from the SMS Toolkit 2 for the version of IIS you are using (IIS Lockdown for IIS5 and URLScan for IIS 6).

If none of this works you might need to:

1. Remove the MP role from the server.
    

2. Disable IIS then uninstall it and reboot the server.
    

3. Verify the “Distributed Transaction Coordinator” service is “Enabled” and started.
    

4. Verify the “COM+ System Application” service is “Enabled” and started.
    

5. Verify the “Task Scheduler” service is “Enabled” and started.
    

6. Verify the “Windows Management Instrumentation” service is “Enabled” and started.
    

7. Reload IIS making sure that BITS and WebDAV are installed and allowed as part of installing IIS.
    

8. Verify the “World Wide Web Publishing Service” is “Enabled” and started.
    

9. Verify that the Default Web Site is running on Port 80 (unless you’ve explicitly changed it for a reason).
    

10. Verify that the Computer account of the machine the MP is running on has been added to the “SMS_SiteSystemToSQLConnection_<site_code>” group (if the MP is on a Secondary this group exists on the Parent Primary).
     

11. Verify that the Computer account of the machine the MP is running on has been added to the “SMS_SiteSystemToSiteServerConnection_<site_code>” group (if the MP is on a Secondary this group exists on the Parent Primary).
     

12. Reconfigure the MP Site System role on the SMS Site Server.