I'm trying to get SCCM going for use with Forefront Endpoint Protection. We have an existing WSUS set up on this same server. I'd like to leave this alone and use the custom SMSWEB site in IIS as I've seen described in various places. This has been set up, including Webdav (with the weird manual change of schema.xml seen on multiple posts), checked the box in SCCM to use custom web site on the ports tab. I left it set to the standard ports, and have a WINS entry for SMSWEB. I'm not sure what I'm missing here. I've looked at forums, etc, and am getting frustrated. The very unhelpful error gives 5 different things to check, and I've checked them, so I'm obviously missing something. I'd like some specific step-by-step help on this if anyone is able to assist. I tried removing the ConfigMgr management point role and adding it back, and that didn't seem to help. Here's the server info: 64bit Server 2008 R2 Standard (on vmware) SCCM 2007 R3 Message ID: 5436 Process ID: 2252 Thread ID: 3296 Error: MP Control Manager detected management point is not responding to HTTP requests. The HTTP status code and text is 404, Not Found. Possible cause: Management point encountered an error when connecting to SQL Server. Solution: Verify that the SQL server is properly configured to allow Management Point access. Verify that management point computer account or the Management Point Database Connection Account is a member of SMS Management Point Role (msdbrole_MP) in the SQL Server database. Possible cause: The SQL Server Service Principal Names (SPNs) are not registered correctly in Active Directory Solution: Ensure SQL server SPNs are correctly registered. Review Q829868. Possible cause: Internet Information Services (IIS) isn't configured to listen on the ports over which SMS is configured to communicate. Solution: Verify that the designated Web Site is configured to use the same ports which SMS is configured to use. Possible cause: The designated Web Site is disabled in IIS. Solution: Verify that the designated Web Site is enabled, and functioning properly. Possible cause: The SMS ISAPI Application Identity does not have the requisite logon privileges. Solution: Verify that the account that the SMS ISAPI is configured to run under has not been denied batch logon rights through group policy. For more information, refer to Microsoft Knowledge Base article 838891.

Is this a new setup? Did the MP ever work? Was it installed successfully at all (mpsetup.log, mpmsi.log)? What have you already done to solve that error (except those things mentioned in the status message). See http://social.technet.microsoft.com/Search/en-US/systemcenter/cm?query=http%20404&rq=meta:Search.MSForums.GroupID(2a118fc8-6e85-4637-821e-4231d2eef7c9)+site:microsoft.com&rn=All+System+Center+Configuration+Manager+Forums as this was duiscussed numerous times yet.Torsten Meringer | http://www.mssccmfaq.de

Think I got the above problem fixed, don't have the links handy still, but there are solutions out there, regarding renaming a dll and running a hotfix again. I think it's all up and running ok now, with a custom FEP policy set, just need to figure out the deployment.

This is a new setup. I tried uninstalling all (including FEP) and starting from scratch. I guess using the custom site wasn't necessary, but tried that due to other unrelated errors that were resolved elsewhere. Got it to seemingly push a client to a test PC. The items showed up in the control panel, but didn't see anything in add/remove programs. Tried to install Forefront Endpoint Protection again to move forward, and now every time I open the Configuration Manager console, I get this when I click on Policies under Forefront Endpoint Protection (under computer management): http://i.imgur.com/tJJNn.jpg If I choose to unload and continue, I get this: http://i.imgur.com/V6vAV.jpg Text from Exception stack trace section: at Microsoft.ConfigurationManagement.AdminConsole.Common.UtilityClass.GetManagementObjectDescriptionFromConnectionManager(ConnectionManagerBase connectionManager, String className) at Microsoft.ConfigurationManagement.ManagementProvider.LoadXmlHelpers.GetManagementClassDescription(ConnectionManagerBase connectionManager, String className) at Microsoft.ConfigurationManagement.ManagementProvider.LoadXmlHelpers.GetManagementObjectDescription(ConnectionManagerBase connectionManager, String className) at Microsoft.ConfigurationManagement.AdminConsole.ConsoleView.ConsoleFormViewControl.CreateColumnListFromViewData(String managementClass) at Microsoft.ConfigurationManagement.AdminConsole.ConsoleView.ConsoleFormViewControl.AddColumnsAndRestoreSettingsForClassObjects(IResultObject resultObject) at Microsoft.ConfigurationManagement.AdminConsole.ConsoleView.ConsoleFormViewControl.AddColumnsAndRestoreSettings(IResultObject resultObject) at Microsoft.ConfigurationManagement.AdminConsole.ConsoleView.ConsoleFormViewControl.OnLoadCustomData(Byte[] customData) at Microsoft.ManagementConsole.View.ProcessRequest(Request request) at Microsoft.ManagementConsole.ViewMessageClient.ProcessRequest(Request request) at Microsoft.ManagementConsole.Internal.IMessageClient.ProcessRequest(Request request) at Microsoft.ManagementConsole.Executive.RequestStatus.BeginRequest(IMessageClient messageClient, RequestInfo requestInfo) at Microsoft.ManagementConsole.Executive.SnapInRequestOperation.ProcessRequest() at Microsoft.ManagementConsole.Executive.Operation.OnThreadTransfer(SimpleOperationCallback callback) Once past that, I can't get anything else in the console to work. This is a complete and utter cluster.