I installed SCCM2007 on a test server last week. I thought that everything was fine but today I am coming across some issues relating to the installation of the client software on the server through <ccmsetup.exe> (my understanding is that I need to do this for the purpose of being able to import drivers for MDT2010/ZTI). When looking at the <ccmsetup.log>, the primary lines that seem to indicate a problem are as follows: -Fallback Status Point has not been specified -Client OS is not a supported Windows Embedded Platform -Failed to successfully complete HTTP request Furthemore, when I look at the <ComponentSetup.log> file, I am noticing these last two lines: -Install MP control manager: Unknown -Install management point: Unknown (every other component has a status of "Completed") Is there a way that I can "clean up" this SCCM installation (specifically, it seems, I need to add or configure these two components) without having to start from scratch? Any guidance here would be appreciated. -Brian McKnight

you need to make sure you have the required site systems installed prior to installing clients. Create boundaries Create a MP, SLP and a Fall back status point Configure client agent settings Configure client push command line properties You will find detailed information about all processes in these articles - http://technet.microsoft.com/en-us/library/bb680326.aspxKent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund

I seems to me that the first three of your points are set within my test box. -I am seeing one boundary within <SCCM/Site Database/Site Management/%Site Name%/Site Settings/Boundaries> -I am seeing the roles that you mentioned (along with a few others) within <SCCM/Site Database/Site Management/%Site Name%/Site Systems/%Server Name>, although I am not sure what to configure for the account that the SLP uses to connect to the database (I set the local administrator account for the server to be used as the "Site System Installation Point. . .hopefully that is OK) -Within <SCCM/Site Database/Site Management/%Site Name%/Site Settings/Client Agents>, I set the Hardware Inventory Client Agent to Enable Hardware Inventory on Clients, the Software Inventory Client Agent to Enable Software Inventory on Clients, the Advertised Programs Client Agent to Enable Software Distribution to Clients, and the Computer Client Agent/<BITS> tab Apply to Branch Distribution Points (I am not sure if I really need anything else in order to get MDT/ZTI running). Regarding the fourth, can't I just install manually by running <ccmsetup.exe> on the server. This is what I attempted after performing all this but I am still seeing the following problematic entries within the <ccmsetup.log> -Failed to successfully complete HTTP request (StatusCode at WinHttpQueryHeaders: 404) -Request failed: 500 Internal Server error (the "Fallback Status Point has not been specified" and the "Client OS is not a supported Windows Platform" messages seemed to have cleared) I was led to believe through another thread on TechNet that, once this client is installed correctly, I can verify by seeing either <HKLM\Software\Microsoft\CCM\Security> or <HKLM\Software\Software\Wow6432Node\Microsoft\CCM\Security> within the registry. Do you concur with that? -Brian McKnight

Hi Brian, First, have you extended AD schema before installing SCCM? Here is a Technet document about extending AD schema: http://technet.microsoft.com/en-us/library/bb680432.aspx If you did not extend AD schema, then SLP is need to help clients to locate SCCM server, MP, DP etc. Here is a reference from Technet: http://technet.microsoft.com/en-us/library/bb632435.aspx Make sure the System Management Container has correct permission for SCCM. Maybe this is an MP error, during client installation ccmsetup.exe will find MP to get client.msi and other requested files. So you should check whether MP works first, try the following two links in the start menu run button: http://<management point name>/sms_mp/.sms_aut?mplist if you see a blank screen instead of an error message, the request is successful. Next run the following link. http://<management point name>/sms_mp/.sms_aut?mpcert if the request is successful, you will see a long list of numbers and letters. Check your WebDAV settings: Make sure there is an authoring rule that allow "All users" read access to "All content". Make sure the WebDAV settings "Allow anonymous property queries" and "Allow property queries with infinite depth" are set to "true" [they are currently set to false] and "Allow Custom Properties" is set to false.[it's set to true] Thanks

The schema is properly extended. I confirmed this by looking at the <extADSch.log>. The WebDAV settings that you mentioned are set up correctly. What I am attempting to do (and I would welcome comments pertaining to whether this is common or proper to do) is make the server that I am running SCCM on basically a client to itself by running <ccmsetup.exe> on it. The reason for this is that I am being led to understand that this is necessary in order to import drivers into the Configuration Manager console so that I can go on and create driver packages for MDT2010/Zero Touch Installation. It seems a little weird for me to have to be able to do this (and it was not mentioned as a necessary step in the MDT 2010 Quick Start Guide for SCCM2007), but I am getting an error message when attempting to import a driver <.inf> file and was told that this is what was needed. I ran the "http://<management point name>/sms_mp/.sms_aut?mplist" diag ON THE SCCM SERVER ITSELF (again, hopefully not an issue) using the server's name as the "management point name" (please confirm if this is the right thing) and got an HTTP Error 404 ("The resource you are looking for has been removed, had it's name changed, or is temporarily unavailable"). I am going to attempt to wipe out and reinstall all the roles that I currently have within <SCCM/Site Database/Site Management/Site Systems/%name of SCCM server%>. One thing that I noticed within the New Site Role Wizard was that the Site System Installation Account (that is used to install site systems) was set for the FQDN of the local administrative account that I had originally configured for the server (which is set as a member of <Domain Admins>, <Enterprise Admins>, <SMS Admins>, and <Schema Admins>). I also noticed that, within the MP and SLP properties page, there is a setting for <Specify the account used by the management point to connect to the database> that is set for "Use the management points computer account". Since these two things to not appear to jive (at least this is the theory that I am working on for the moment. . .would appreciate feedback on this point as well please), I am going to re-create all the roles using the setting within the New Site Role wizard to <Use the site server's computer account to install the site system> instead. Hopefully that will have an effect when I run <ccmsetup.exe> again afterwards (and also when I run the two diags that you gave me pertaining to testing the health of the MP. . .I will actually run the diags prior to attempting to install the client again). I will post the results, but would still greatly appreciate feedback on: -Setting the SCCM server as it's own client -Running the diags you gave me directly from the SCCM server -Using the server's name as the "management point name" -The difference between using another account (like the local admin for the server) as opposed to the site server's computer account for "installing the site system", and how that selection relates to the settings in the MP and SLP (or whatever other roles) pertaining to the "account used to connect to the database". Thank you! -Brian McKnight

I was able to delete every role except for the following: -ConfigMgr component manager -ConfigMgr site server -ConfigMgr site system -ConfigMgr site database server Looks like these need to stay no matter what (there was no option to delete them). Now I am restarting the server and starting from scratch regarding the other roles.-Brian McKnight

Forgot to mention this. . . Within the <CN=System Management> Properties page, under the Security tab, settings are as follows: SELF = Special Permissions Authenticated Users = Read, (inherited) Special Permissions SYSTEM = Full Control Domain Admins = Full Control Enterprise Admins = (inherited) Full Control Administrators = (inherited) Read, (inherited) Write, (inherited) Create All Child Objects Pre-Windows 2000 Compatible Access = (inherited) Special Permissions ENTERPRISE DOMAIN CONTROLLERS = (inherited) Special Permissions Don't know whether or not these are the "correct" SCCM permissions for this container. I probably need someone else to review and confirm. Thanks, -Brian McKnight

That seems to be ok, but you forgot to add the siteserver (full control)...Miguel Rodriguez

OK, I went so far as to completely uninstall SCCM, remove the IIS server role, and build both back up from scratch (making sure that WebDAV was reset the same way that I confimed was correct before). I added the site server to the System Management container (with Full Control permission) I set the Communication Settings for the ConfigMgr Distribution Point to "Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS (required for device clients and Internet-based clients). I checked the option for the ConfigMgr Management point to "Allow devices to use this management point" I ran the "http://<management point name>/sms_mp/.sms_aut?mplist" diag again (using the name of my server as the "management point name" and GOT THE SAME 404 ERROR! I am officially desperate here! If I cannot get SCCM configured I might have to start considering LTI or a third-party deployment suite. Am I testing the MP health incorrectly? Is the presence of a SLP messing things up given that I have extended the schema? Honestly (even given my limited knowledge of SCCM configuration), I really do not see where I am going wrong! -Brian McKnight

OK, I went so far as to completely uninstall SCCM, remove the IIS server role, and build both back up from scratch (making sure that WebDAV was reset the same way that I confimed was correct before). I added the site server to the System Management container (with Full Control permission) I set the Communication Settings for the ConfigMgr Distribution Point to "Allow clients to transfer content from this distribution point using BITS, HTTP, and HTTPS (required for device clients and Internet-based clients). I checked the option for the ConfigMgr Management point to "Allow devices to use this management point" I ran the "http://<management point name>/sms_mp/.sms_aut?mplist" diag again (using the name of my server as the "management point name" and GOT THE SAME 404 ERROR! I am officially desperate here! If I cannot get SCCM configured I might have to start considering LTI or a third-party deployment suite. Am I testing the MP health incorrectly? Honestly (even given my limited knowledge of SCCM configuration), I really do not see where I am going wrong! -Brian McKnight

Hi Brian, could you check your installation with this article please, before giving up? http://myitforum.com/cs2/blogs/cnackers/archive/2010/09/20/configuration-manager-configuring-server-2008-r2-for-site-systems.aspx Assume you are using WS2008R2, right? Check the following logs on your siteserver and post back any errors: mpsetup.log mpmsi.log mpcontrol.log BTW: the option for the ConfigMgr Management point to "Allow devices to use this management point" is not necessary unless you plan to use mobile device management feature.Miguel Rodriguez

I am using W2k8Server R2. The only one of these log files that I found was the <mpsetup.log>, here is what is reported over and over. . . <06-08-2011 15:14:05> SMSMP Setup Started.... <06-08-2011 15:14:05> Parameters: C:\PROGRA~1\MIE096~1\bin\i386\ROLESE~1.EXE /install /siteserver:AFPDPLYMTTST SMSMP <06-08-2011 15:14:05> Installing Pre Reqs for SMSMP <06-08-2011 15:14:05> ======== Installing Pre Reqs for Role SMSMP ======== <06-08-2011 15:14:05> Found 1 Pre Reqs for Role SMSMP <06-08-2011 15:14:05> Pre Req MSXML60 found. <06-08-2011 15:14:05> No versions of MSXML60 are installed. Would install new MSXML60. <06-08-2011 15:14:05> Enabling MSI logging. msxml6_x64.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\msxml6_x64MSI.log <06-08-2011 15:14:05> Installing C:\Program Files\Microsoft Configuration Manager\bin\x64\00000409\msxml6_x64.msi <06-08-2011 15:14:09> msxml6_x64.msi exited with return code: 0 <06-08-2011 15:14:09> msxml6_x64.msi Installation was successful. <06-08-2011 15:14:09> ======== Completed Installion of Pre Reqs for Role SMSMP ======== <06-08-2011 15:14:09> Installing the SMSMP <06-08-2011 15:14:09> Passed OS version check. <06-08-2011 15:14:09> IIS Service is installed. <06-08-2011 15:14:09> checking WebDAV configuraitons <06-08-2011 15:14:12> Failed to get WebDAV settings on the machine (0x80070002) I have reviewed the WebDAV settings over and over and they are on the money. Somehow, it looks like SCCM is not able to see them. I am assuming at this point that the other log files never had a chance to generate themselves because of this. The only thing that I can think of as to why this might be is that, before I realized that WebDAV was included within Win2K8Server R2, I attempted to download/install a version of it (either for IIS 7 or IIS 7.5, I forget at this point) but the install failed. Could this be mucking up things even though it went nowhere? This is starting to look more and more like a rebuild of the server from bare metal (although I would hope to avoid this even in spite of the fact that it is a test server). -Brian McKnight

It was a <webdav_x64_75.msi > file that I attempted to run. The error message received was: ------------------------------------------ IIS version 7.0 is required to use WebDAV 7.5 for IIS 7.0 ----------------------------------------- I thought nothing of this once I realized that WebDAV was built into Win2k8Server R2, but now I cannot discount that the simple attempt to run this corrupted something. I found this. . . http://social.technet.microsoft.com/Forums/eu/configmgrgeneral/thread/3c7b1634-9ebb-46d9-a0d4-965cb2bfaf2e WebDav is installed on my Default website. I am not sure where to access the MP troubleshooter from ConfigMgr. Toolkit V2 that Kent mentioned. I will however check my <sitecomp.log> shortly. -Brian McKnight

First try removing and readding WebDAV(You will have to do the config again). Can be found under Role Service of IIS Role. Miguel Rodriguez

I think that I got somewhere. I wiped out SCCM and IIS again and reinserted, much like yesterday. This time the <mpsetup.log> read as follows: <06-09-2011 14:57:02> ==================================================================== <06-09-2011 14:57:02> SMSMP Setup Started.... <06-09-2011 14:57:02> Parameters: C:\PROGRA~1\MIE096~1\bin\i386\ROLESE~1.EXE /install /siteserver:AFPDPLYMTTST SMSMP <06-09-2011 14:57:02> Installing Pre Reqs for SMSMP <06-09-2011 14:57:02> ======== Installing Pre Reqs for Role SMSMP ======== <06-09-2011 14:57:02> Found 1 Pre Reqs for Role SMSMP <06-09-2011 14:57:02> Pre Req MSXML60 found. <06-09-2011 14:57:02> No versions of MSXML60 are installed. Would install new MSXML60. <06-09-2011 14:57:02> Enabling MSI logging. msxml6_x64.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\msxml6_x64MSI.log <06-09-2011 14:57:02> Installing C:\Program Files\Microsoft Configuration Manager\bin\x64\00000409\msxml6_x64.msi <06-09-2011 14:57:07> msxml6_x64.msi exited with return code: 0 <06-09-2011 14:57:07> msxml6_x64.msi Installation was successful. <06-09-2011 14:57:07> ======== Completed Installion of Pre Reqs for Role SMSMP ======== <06-09-2011 14:57:07> Installing the SMSMP <06-09-2011 14:57:07> Passed OS version check. <06-09-2011 14:57:07> IIS Service is installed. <06-09-2011 14:57:07> checking WebDAV configuraitons <06-09-2011 14:57:08> WebDAV is configured <06-09-2011 14:57:08> No versions of SMSMP are installed. Installing new SMSMP. <06-09-2011 14:57:08> Enabling MSI logging. mp.msi will log to C:\Program Files\Microsoft Configuration Manager\logs\mpMSI.log <06-09-2011 14:57:08> Installing C:\Program Files\Microsoft Configuration Manager\bin\i386\mp.msi CCMINSTALLDIR="C:\Program Files\SMS_CCM" CCMSERVERDATAROOT="C:\Program Files\Microsoft Configuration Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1 <06-09-2011 14:58:38> mp.msi exited with return code: 0 <06-09-2011 14:58:38> Verifying CCM_CLIENT virtual directory. <06-09-2011 14:58:38> Website path is IIS://LocalHost/W3SVC/1. <06-09-2011 14:58:38> Connecting to IIS. <06-09-2011 14:58:38> CCM_CLIENT is currently C:\Program Files (x86)\Microsoft Configuration Manager\Client. <06-09-2011 14:58:39> Setting CCM_CLIENT to C:\Program Files\Microsoft Configuration Manager\Client. <06-09-2011 14:58:39> Installation was successful. http://afpdplymttst/sms_mp/.sms_aut?mplist did not return a blank page, but did not return a 404 error either. . . - <MPList> - <MP Name="AFPDPLYMTTST" FQDN="AFPDPLYMTTST.DEPLOYMENTTST.LOCAL"> <Version>6487</Version> <Capabilities SchemaVersion="1.0" /> </MP> </MPList> http://afpdplymttst/sms_mp/.sms_aut?mpcert as advertised did retun a long alphanumeric string. . . - <MPCertificate> <Certificate>308201E830820151A00302010202103E9960EDF0703BBF4BEC1AC207B72BDE300D06092A864886F70D01010505003025311530130603550403130C41465044504C594D54545354310C300A06035504031303534D533020170D3131303630383231353833375A180F32313131303531363231353833375A3025311530130603550403130C41465044504C594D54545354310C300A06035504031303534D5330819F300D06092A864886F70D010101050003818D0030818902818100B08377E8EBF3196EA1300EC37C4890C8F6A9927908CE770C3F00FAA38E965C0B0D55E26B54B094F5EF76F5D8D4B96A9F1A8778E3E5B5B4F2FC553666F5B204AC8BCADC1F8BAA1359B7C0FCAA38FF39A1FC18E512CAAC46C8118C86EC00D2158864705CDB1C28AB9847313ECDAC96447663337A9FE407E006AC40C558450DB1B30203010001A317301530130603551D25040C300A06082B06010401823765300D06092A864886F70D01010505000381810041A49D7AC3AA1A17A54EB458C6F40768EC1C367DA4C4C15B24152E5E086CEC5472403BE0AA25EC1E31E75300A43F3AC2AFF70DF389DF2C2B1A26738A3B54809587E6A5CAD549082783F522EF5A995968A5120FD0E0750FB483D1796C62AB078424A6158146465E8FE9AE425FE688F7E81406703D07DFD7E358CCCE019847363A</Certificate> </MPCertificate> Now I will try running <ccmsetup.exe> again and will see what happens. I am thinking now that yesterday's IIS role removal did not take cleanly and that had an affect. -Brian McKnight

I think that I still have an issue or two. Here is my latest <ccmsetup.log>. . . <![LOG[==========[ ccmsetup started in process 5148 ]==========]LOG]!><time="15:51:00.809+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:9010"> <![LOG[Version: 4.0.6487.2000]LOG]!><time="15:51:00.809+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:2068"> <![LOG[GetAdaptersAddressess entry point is supported.]LOG]!><time="15:51:00.809+420" date="06-09-2011" component="ccmsetup" context="" type="0" thread="4060" file="ccmiputil.cpp:118"> <![LOG[DhcpGetOriginalSubnetMask entry point is supported.]LOG]!><time="15:51:00.809+420" date="06-09-2011" component="ccmsetup" context="" type="0" thread="4060" file="ccmiputil.cpp:181"> <![LOG[Current AD site of machine is Default-First-Site-Name]LOG]!><time="15:51:00.813+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="lsad.cpp:457"> <![LOG[Attempting to query AD for assigned site code]LOG]!><time="15:51:00.813+420" date="06-09-2011" component="ccmsetup" context="" type="0" thread="4060" file="lsad.cpp:1766"> <![LOG[Executing query (&(ObjectCategory=MSSMSRoamingBoundaryRange)(|(&(MSSMSRangedIPLow<=183894036)(MSSMSRangedIPHigh>=183894036))))]LOG]!><time="15:51:00.823+420" date="06-09-2011" component="ccmsetup" context="" type="0" thread="4060" file="lsad.cpp:1801"> <![LOG[Executing query (&(ObjectCategory=mSSMSSite)(|(mSSMSRoamingBoundaries=10.246.0.0)(mSSMSRoamingBoundaries=Default-First-Site-Name)))]LOG]!><time="15:51:00.839+420" date="06-09-2011" component="ccmsetup" context="" type="0" thread="4060" file="lsad.cpp:1862"> <![LOG[LSGetAssignedSiteFromAD : Trying to Assign to the Site <AFP>]LOG]!><time="15:51:00.863+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="lsad.cpp:1922"> <![LOG[The MP name retrieved is 'AFPDPLYMTTST.DEPLOYMENTTST.LOCAL' with version '6487l' and capabilities '<Capabilities SchemaVersion="1.0"> </Capabilities>']LOG]!><time="15:51:00.867+420" date="06-09-2011" component="ccmsetup" context="" type="0" thread="4060" file="lsad.cpp:2869"> <![LOG[Retrieving client operational settings from AD.]LOG]!><time="15:51:00.867+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="lsad.cpp:4931"> <![LOG[ClientOperationalSettings search filter is '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=AFP))']LOG]!><time="15:51:00.870+420" date="06-09-2011" component="ccmsetup" context="" type="0" thread="4060" file="lsad.cpp:4673"> <![LOG[Command line: "C:\Windows\ccmsetup\ccmsetup.exe" ]LOG]!><time="15:51:00.870+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:4102"> <![LOG[CCMHTTPPORT: 80]LOG]!><time="15:51:00.870+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:8008"> <![LOG[CCMHTTPSPORT: 443]LOG]!><time="15:51:00.871+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:8023"> <![LOG[CCMHTTPSSTATE: 0]LOG]!><time="15:51:00.871+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:8041"> <![LOG[CCMHTTPSCERTNAME: ]LOG]!><time="15:51:00.871+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:8069"> <![LOG[FSP: AFPDPLYMTTST.DEPLOYMENTTST.LOCAL]LOG]!><time="15:51:00.871+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:8084"> <![LOG[CCMFIRSTCERT: 0]LOG]!><time="15:51:00.871+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:8126"> <![LOG[Config file: ]LOG]!><time="15:51:00.871+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:4497"> <![LOG[Retry time: 10 minute(s)]LOG]!><time="15:51:00.871+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:4498"> <![LOG[MSI log file: ]LOG]!><time="15:51:00.871+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:4499"> <![LOG[MSI properties: SMSSITECODE=AFP CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" FSP="AFPDPLYMTTST.DEPLOYMENTTST.LOCAL" CCMFIRSTCERT="0"]LOG]!><time="15:51:00.871+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:4500"> <![LOG[Source List:]LOG]!><time="15:51:00.871+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:4508"> <![LOG[MPs:]LOG]!><time="15:51:00.871+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:4527"> <![LOG[ AFPDPLYMTTST.DEPLOYMENTTST.LOCAL]LOG]!><time="15:51:00.871+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:4542"> <![LOG[Updated security on object C:\Windows\ccmsetup\.]LOG]!><time="15:51:00.871+420" date="06-09-2011" component="ccmsetup" context="" type="0" thread="4060" file="ccmsetup.cpp:8849"> <![LOG[Sending Fallback Status Point message, STATEID='100'.]LOG]!><time="15:51:00.871+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:9326"> <![LOG[State message with TopicType 800 and TopicId {B9CAB0B8-9C43-4A2A-BD49-26EB0F47DAC7} has been sent to the FSP]LOG]!><time="15:51:01.089+420" date="06-09-2011" component="FSPStateMessage" context="" type="1" thread="4060" file="fsputillib.cpp:730"> <![LOG[Running as user "Administrator"]LOG]!><time="15:51:01.089+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:2690"> <![LOG[Detected 94618 MB free disk space on system drive.]LOG]!><time="15:51:01.089+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:463"> <![LOG[DetectWindowsEmbeddedFBWF() Detecting OS Version]LOG]!><time="15:51:01.089+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:509"> <![LOG[Client OS Version is 6.1, Service Pack Version 1]LOG]!><time="15:51:01.089+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:533"> <![LOG[Client OS is not a supported Windows Embedded Platform]LOG]!><time="15:51:01.090+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:535"> <![LOG[Successfully ran BITS check.]LOG]!><time="15:51:01.391+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:7105"> <![LOG[Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 500)]LOG]!><time="15:51:01.623+420" date="06-09-2011" component="ccmsetup" context="" type="3" thread="4060" file="ccmsetup.cpp:5969"> <![LOG[Sending Fallback Status Point message, STATEID='308'.]LOG]!><time="15:51:01.623+420" date="06-09-2011" component="ccmsetup" context="" type="1" thread="4060" file="ccmsetup.cpp:9326"> <![LOG[State message with TopicType 800 and TopicId {42B9FA2D-EF0C-4D06-8A63-6A389B0B2895} has been sent to the FSP]LOG]!><time="15:51:01.643+420" date="06-09-2011" component="FSPStateMessage" context="" type="1" thread="4060" file="fsputillib.cpp:730">-Brian McKnight

I made sure, before I ran the <ccmsetup.log> to: -Add a boundary -Add the Server Locator Point and Fallback Status Point roles The schema should (obviously) still be extended. ASAIK, you cannot really "unextend" a schema. -Brian McKnight

There are a couple of solved posts on the HTTP request failure. Have you checked them? e.g. http://social.technet.microsoft.com/Forums/en-US/configmgrsetup/thread/1989ab6a-28c0-48b1-9d73-47c8484010f3 Are there any errors in mpcontrol.log? If so please post them. Run the client deployment failure report on your site and see if it contains the machine in question. This way you can also see if your FSP is working correctly. Did you setup the site to run in native mode?Miguel Rodriguez

I went through a lot to get this resolved. In a nutshell, I needed to reinstall the server in order to get rid of a lot of "installation was corrupted" errors in the Event Log. Then, after that, there were still issues that needed to be manually resolved. The fact that I have SCCM/SQL installed on a domain controller in my test environment was likely the culprit. ISSUE ======== Unable to perform client push on SCCM site server. CAUSE ======= Settings for Webdav were not replicating to webdav_schema.xml file. Later IUSR did not have permission on client folder. RESOLUTION ============ - We found that the machine was a domain controller and we have DNS, DHCP, WSUS, IIS, and FTP installed on this SCCM site server. - We discussed that installing SCCM is not recommended but for testing, he can do that. - Later we mentioned an account for client push under installation methods\client push installation\accounts tab. - Tried to perform client push on the site server. It failed. No error in ccm.log but we had these errors- IIS log- 2011-06-29 21:20:37 ::1 GET /CCM_Client/ccmsetup.cab - 80 - ::1 ccmsetup 500 19 5 218 CCMsetup.log- Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 500) - Verified the webdav settings. It was installed and configured but it was disabled. Enabled it. - Ran iisreset but we got the same error again. - We then checked the permission on wevdav_schema.xml and found that system and administrators only have read permission on this file. - Gave them full rights. Also edited the file and found that webdav settings were not replicated as per IIS window. - We edited the settings manually and performed iisreset. - Performed client push again but it still failed with the same error. - We then uninstalled the management point. Uninstalled and reinstalled Webdav publishing component. - We configured the settings for Webdav. - We replaced the webdav_schema.xml with the backup file which we had created earlier. - We performed the client push again but it failed with a different error this time. It had error 401 instead of 500. - We got this information in IIS log then- 2011-06-29 22:02:41 ::1 GET /CCM_CLIENT/ccmsetup.exe - 80 - ::1 Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.1;+WOW64;+Trident/4.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729) 401 3 5 140 - Tried to browse the file using internet explorer and it gave the same error. - We went to Program files\Microsoft configuration manager\client folder and added IUSR account and gave it full permissions. - Performed client push again and this time it worked perfectly. -Brian McKnight