hello TechNet, let me give you a brief run-down of what our problem was and what the problem now is, please keep in mind we are on Server 2008 SP1. Our First Problem (Resolved): our reporting point wasn't functioning correctly and we had determined this to be related to the IIS installation. therefore, we removed the Web Server Role (IIS) and removed the following roles in ConfigMgr 2007. management point and reporting point. We are not currently using the software update point, as we have a primary SUS server already on-site. SCCM is currently only being used to deploy and update third-party software (Adobe Reader, Adobe Flash, Citrix, etc). We followed the step-by-step Microsoft TechNet article: http://technet.microsoft.com/en-us/library/cc431377.aspx After completing this, and re-adding the management point and reporting point roles; the reporting point role is now working, and we can pull valid reports. However, this created the following two errors: Our Second Problem (Not Resolved): #1. We are no longer able to push updates to any clients on site; however, we can push out the client-install. Awkward, and go figure. #2. Management Point Error 5438: MP Control Manager detected MP is not responding to HTTP requests. The http error is 12030 and Management Point Error 5481: MP Control Manager detected DMP is not responding to HTTP requests. The http error is 12030. On the management point issue, we have run the mplist / mpcert from both the local-host and on the client side, and receive a valid returned value of the site and certificate. We downloaded ConfigMgr Toolkit V2 and ran the test, and received Pass for all test. Any help would be greatly appreciated at this point.

First of all remove the DMP unless you are actually managing mobile devices which I doubt you are. It's just a checkbox "Allow devices to connect to this management point" on the MP properties. Once that's done your errors will probbaly go away. Next we will need to find the real cause of your problems because I don't think those errors are it. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

ok. i've taken care of the DMP removal; definitely no mobile device management.

Cool. Let's see if that clears up the 12030 errors. Then we can find the real problem. What happens when you push updates to the clients? What errors are in the client logs? Can you test your MP using the MP troubleshooter in the SCCM toolkit v2? John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

Still receiving Message ID: 5438, MP Control Manager detected MP is not responding to HTTP requests. Successfully ran the SCCM ConfigMgr Toolkit V2 - MP Troubleshooter. All tests run come back with a value of Pass. Checking the logs.

are you running native or mixed mode?Kent Agerlund | http://scug.dk/ | The Danish community for System Center products

Mixed mode.

Can you post locationservices.log in client workstationand can you post your mpsetup.log in the server. can you access the MP url from the client end.can you initiate a update scan from a workstation and check the WUAHandler.log Sanka Perera

Hi, For pushing software updates issue, try to remove SUP and re-add it to see what will happen. And for the error 12023, if you installed your MP on a Windows Server 2003 computers, see the following solution: Go to the InetSrv directory and confirm the following IIS files match the Windows Server 2003 Service Pack version. This is an issue we have mostly seen with Microsoft Internet Information Services 6.0, when used with Microsoft Windows Server 2003 Service Pack 2 In the Known Issues section of article 973917, the KB describes an issue with the update when it is installed on Windows Server 2003 with IIS6. More information about the known issue is also described in the following article: Internet Information Services 6.0 may not function correctly after installing KB973917 http://support.microsoft.com/kb/2009746/ To mitigate the known issue, server administrators should ensure all of the IIS components are at the Windows Server Service Pack 2 version or later. The KB973917 article lists the component names and the version numbers to check for. http://blogs.iis.net/webtopics/archive/2009/12/18/sample-script-to-verify-iis-file-versions-for-kb973917.aspxhttp://blogs.iis.net/webtopics/archive/2009/12/18/sample-script-to-verify-iis-file-versions-for-kb973917.aspx 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.

as of Friday, the pushing of updates issue has been resolved. i was able to reinstall the client on our all-devices via push and this allowed us to begin the process pushing out our third-party updates again; not sure why that affected it, as no configuration settings have changed from original configuration. we are still researching the management point issue, this is installed on Server 2008 SP1.