locked
Failed to get DP locations as the expected version from MP 'myserver.sccm.local'. Error 0x87d00215 RRS feed

  • Question

  • Hi, I've seen many people with this error, but none of the solutions I found worked for me.

    Here's a little more on my setup

    • 1 Standalone Primary Site (with DP, MP, FSP etc roles installed)
      Windows 2008 R2 SP1
      SQL 2008 STD R2 SP2  (installed on the same box)
      IIS 7 + BITS + WEBDAV installed
      WSUS
    • 1 Domain Controler
      Windows 2008 R2 SP1 
    • 1 Client Windows 7 machine

    In Configuration Manager,

    • I have  created my 1 and single Boundary based on a AD site
    • I have boundary group that includes my single Boundary

    In Active Directory,

    • 1 subnet 192.168.1.0/24
    • 1 site with the subnet assign to

    So basically, this is a new setup and I tought I was all set and ready to push a client. Looks like it's not working.

    For what I see, when I deploy to 1 client, I can see in task manager CCMSETUP.EXE running and hanging there for a while. The client never gets installed. Here's the log of this client:

    ==========[ ccmsetup started in process 2716 ]========== ccmsetup 10/18/2013 12:54:59 PM 1940 (0x0794)
    Running on platform X64 ccmsetup 10/18/2013 12:54:59 PM 1940 (0x0794)
    Updated security on object C:\Windows\ccmsetup\cache\. ccmsetup 10/18/2013 12:54:59 PM 1940 (0x0794)
    Launch from folder C:\Windows\ccmsetup\ ccmsetup 10/18/2013 12:54:59 PM 1940 (0x0794)
    CcmSetup version: 5.0.7804.1000 ccmsetup 10/18/2013 12:54:59 PM 1940 (0x0794)
    In ServiceMain ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Running on OS (6.1.7601). Service Pack (1.0). SuiteMask = 256. Product Type = 1 ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Ccmsetup command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required. ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Command line: "C:\Windows\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    SslState value: 224 ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    CCMHTTPPORT:    80 ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    CCMHTTPSPORT:    443 ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    CCMHTTPSSTATE:    192 ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    CCMHTTPSCERTNAME:     ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    FSP:    SCCM-CFG1 ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    CCMFIRSTCERT:    1 ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Config file:      C:\Windows\ccmsetup\MobileClientUnicode.tcf ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Retry time:       10 minute(s) ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    MSI log file:     C:\Windows\ccmsetup\Logs\client.msi.log ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    MSI properties:    INSTALL="ALL" SMSSITECODE="MTL" FSP="SCCM-CFG1" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="192" CCMFIRSTCERT="1" ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Source List: ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
                      \\sccm-cfg1.sccm.local\SMSClient ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
                      \\SCCM-CFG1.SCCM.LOCAL\SMSClient ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    MPs: ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
                      sccm-cfg1.sccm.local ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    No version of the client is currently detected. ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Updated security on object C:\Windows\ccmsetup\. ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Sending Fallback Status Point message to 'SCCM-CFG1', STATEID='100'. ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Failed to get client version for sending messages to FSP. Error 0x8004100e ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Params to send FSP message '5.0.7804.1000 Deployment ' ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    State message with TopicType 800 and TopicId {34EDA920-0FA3-4C06-A89F-9CE79CC38F28} has been sent to the FSP FSPStateMessage 10/18/2013 12:54:59 PM 1368 (0x0558)
    Running as user "SYSTEM" ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Detected 51019 MB free disk space on system drive. ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Checking Write Filter Status. ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    This is not a supported write filter device. We are not in a write filter maintenance mode. ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Performing AD query: '(&(ObjectCategory=mSSMSManagementPoint)(mSSMSDefaultMP=TRUE)(mSSMSSiteCode=MTL))' ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    OperationalXml '<ClientOperationalSettings><Version>5.00.7804.1000</Version><SecurityConfiguration><SecurityModeMask>0</SecurityModeMask><SecurityModeMaskEx>192</SecurityModeMaskEx><HTTPPort>80</HTTPPort><HTTPSPort>443</HTTPSPort><CertificateStoreName></CertificateStoreName><CertificateIssuers></CertificateIssuers><CertificateSelectionCriteria></CertificateSelectionCriteria><CertificateSelectFirstFlag>1</CertificateSelectFirstFlag><SiteSigningCert>308202F1308201D9A003020102021031FB10A0DE3FF58244637AAF9411755E300D06092A864886F70D01010B05003016311430120603550403130B53697465205365727665723020170D3133313031343137333432335A180F32313133303932313137333432335A3016311430120603550403130B536974652053657276657230820122300D06092A864886F70D01010105000382010F003082010A0282010100DC49751B1C571D994BB012F4BA5FF3EC37044AF0D89C4FF6E789BD67F861999946387A25A3AE52B0093F3674E89675315F1EF5593C6D2DC51DA66835A228A911D6E71C86466E7EF00BB752FBD85AF004DA3C643EE028990A7085748BF682E3A7B4DD40548C42A249C356CC0526C33A9FD88106490E78F5699C5EDF465D7EE25749B03A5E0455DFC9B50E33F52D8F8C4EF325882567EB8F4A2099C9776604A2A486E027CD30CA5FE830DCF07A6C7ECE55DDC96805037E2DA9B84E9F23F618D4FE6DF052B427CB52242278FD822CA2C6E194BCC75324F2FCBEF84965D14EC90448E68EABB662A4C69B4575A8EAFA077485C8F77EE3193C00660F438FEE012918D90203010001A3393037301F0603551D110418301682147363636D2D636667312E7363636D2E6C6F63616C30140603551D25040D300B06092B060104018237650B300D06092A864886F70D01010B050003820101003AF560C5D14325F782E5CE21B5990C47E4ECDF3B98F31797012E8AD75393972530A23451E37B932C6967B840D1567EC03B416DA2FCEFF2B2678683886D455C97727FFB25009F331A7C74B0DBD2427418CB56D2E1DBDA230E848F7EF5CDA0ED7568D9F862464934F45749243BB43B4810A8C62258BA64153AC1A85C072524995AEDFE273871177E94E4B61F46BFB82B74B95F9327DE023E325248BB6F6F6B9E3D5A152E6E338105B20111E58AD7733296087F40D49CD1A076090B98C07D047713325DFE8124B24B950128652982073797A554B49B439AFD309834AB9BA4FF15E7CE93C7B4946355ACC458238E2B53C0EC3D11E03F7232C0466C5178ACDDE46EAE</SiteSigningCert></SecurityConfiguration><RootSiteCode>MTL</RootSiteCode><CCM> <CommandLine>SMSSITECODE=MTL FSP=SCCM-CFG1</CommandLine> </CCM><FSP> <FSPServer>sccm-cfg1.sccm.local</FSPServer> </FSP><Capabilities SchemaVersion ="1.0"><Property Name="SSLState" Value="0" /></Capabilities><Domain Value="sccm.local" /><Forest Value="sccm.local" /></ClientOperationalSettings>' ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Unable to open Registry key Software\Microsoft\CCM. Return Code [80070002]. Client HTTPS state is Unknown. ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    The MP name retrieved is 'sccm-cfg1.sccm.local' with version '7804' and capabilities '<Capabilities SchemaVersion="1.0"><Property Name="SSLState" Value="0"/></Capabilities>' ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    MP 'sccm-cfg1.sccm.local' is compatible ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Retrieved 1 MP records from AD for site 'MTL' ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Retrived site version '5.00.7804.1000' from AD for site 'MTL' ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    SiteCode:         MTL ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    SiteVersion:      5.00.7804.1000 ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Ccmsetup is being restarted due to an administrative action. Installation files will be reset and downloaded again. ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Only one MP sccm-cfg1.sccm.local is specified. Use it. ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Searching for DP locations from MP(s)... ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Current AD site of machine is Default-First-Site-Name LocationServices 10/18/2013 12:54:59 PM 1368 (0x0558)
    Local Machine is joined to an AD domain LocationServices 10/18/2013 12:54:59 PM 1368 (0x0558)
    Current AD forest name is sccm.local, domain name is sccm.local LocationServices 10/18/2013 12:54:59 PM 1368 (0x0558)
    DhcpGetOriginalSubnetMask entry point is supported. LocationServices 10/18/2013 12:54:59 PM 1368 (0x0558)
    Begin checking Alternate Network Configuration LocationServices 10/18/2013 12:54:59 PM 1368 (0x0558)
    Finished checking Alternate Network Configuration LocationServices 10/18/2013 12:54:59 PM 1368 (0x0558)
    Adapter {43FCEE5E-C088-44E3-B24F-2E8E656D0350} is DHCP enabled. Checking quarantine status. LocationServices 10/18/2013 12:54:59 PM 1368 (0x0558)
    Sending message body '<ContentLocationRequest SchemaVersion="1.00">
      <AssignedSite SiteCode="MTL"/>
      <ClientPackage/>
      <ClientLocationInfo LocationType="SMSPACKAGE" DistributeOnDemand="0" UseProtected="0" AllowCaching="0" BranchDPFlags="0" AllowHTTP="1" AllowSMB="0" AllowMulticast="0" UseInternetDP="0">
        <ADSite Name="Default-First-Site-Name"/>
        <Forest Name="sccm.local"/>
        <Domain Name="sccm.local"/>
        <IPAddresses>
    <IPAddress SubnetAddress="192.168.1.0" Address="192.168.1.100"/>
        </IPAddresses>
      </ClientLocationInfo>
    </ContentLocationRequest>
    ' ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Sending message header '<Msg SchemaVersion="1.1"><ID>{CAA5E4C3-81C5-4EF6-814D-E5D3BB7CF87C}</ID><SourceHost>SCCM-CL1</SourceHost><TargetAddress>mp:[http]MP_LocationManager</TargetAddress><ReplyTo>direct:SCCM-CL1:LS_ReplyLocations</ReplyTo><Priority>3</Priority><Timeout>600</Timeout><ReqVersion>5931</ReqVersion><TargetHost>sccm-cfg1.sccm.local</TargetHost><TargetEndpoint>MP_LocationManager</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2013-10-18T16:54:59Z</SentTime><Body Type="ByteRange" Offset="0" Length="1120"/><Hooks><Hook3 Name="zlib-compress"/></Hooks><Payload Type="inline"/></Msg>' ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    CCM_POST 'HTTP://sccm-cfg1.sccm.local/ccm_system/request' ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Content boundary is '--aAbBcCdDv1234567890VxXyYzZ' ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Received header '<Msg SchemaVersion="1.1">
    <ID>{045BD14B-2800-4118-ACE8-92E35EAA32DF}</ID>
    <SourceID>GUID:30B1ECB3-781C-4742-BE5A-B2861D57C2A8</SourceID>
    <SourceHost>SCCM-CFG1</SourceHost>
    <TargetAddress>direct:SCCM-CL1:LS_ReplyLocations</TargetAddress>
    <ReplyTo>MP_LocationManager</ReplyTo>
    <CorrelationID>{00000000-0000-0000-0000-000000000000}</CorrelationID>
    <Priority>3</Priority>
    <Timeout>600</Timeout>
    <TargetHost>SCCM-CL1</TargetHost><TargetEndpoint>LS_ReplyLocations</TargetEndpoint><ReplyMode>Sync</ReplyMode><Protocol>http</Protocol><SentTime>2013-10-18T16:54:59Z</SentTime><Body Type="ByteRange" Offset="0" Length="1254"/><Hooks><Hook3 Name="zlib-compress"/><Hook Name="authenticate"><Property Name="Signature">3082019106092A864886F70D010702A08201823082017E020101310B300906052B0E03021A0500300B06092A864886F70D0107013182015D308201590201013036302231123010060355040313095343434D2D43464731310C300A06035504031303534D5302104840D0E9BCB431B142E4DD992D399950300906052B0E03021A0500300D06092A864886F70D010101050004820100AFCDFCA0B8227D3C57BC7A780ADF1AC6C1FF83B3ECED57827618A7B5F9DA61CBBACEFDB3C039C28FF35EAA62ABF234FDF9A70EECBFA806D4ABFAA2CAB0C6400A02179C9CA2B3BB53558FA489AD3D0DF718E34741304D79DAB40909A866929F551AF3C5871A3B23F0427D01BA6B680EDE91526ABD2D993950E97895D7A1CEEDCB1309667545A3648682973C67CAE8C24C0F9978ACBB587FD028DE0838F81157B64D4095ACE55703451A411F14545BCA4D148D283955CC4B694A1BAE4BA63FD0FA8AA79121FDE072DC6E1E6C81FAC3B3F4C823737648644FE1F82C715EC56D88FD8149715A42A33BD795AEABE999B11C42847146B44094980A2FB1F4C39A148153</Property><Property Name="AuthSenderMachine">SCCM-CFG1;sccm-cfg1.sccm.local;</Property><Property Name="MPSiteCode">MTL</Property></Hook></Hooks><Payload Type="inline"/></Msg>' ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Received reply body '<ContentLocationReply SchemaVersion="1.00"><ContentInfo PackageFlags=""><ContentHashValues/></ContentInfo><Sites><Site><MPSite SiteCode="MTL" MasterSiteCode="MTL" SiteLocality="LOCAL" IISPreferedPort="" IISSSLPreferedPort=""/><LocationRecords/></Site></Sites><ClientPackage FullPackageID="MTL00002" FullPackageVersion="2" FullPackageHash="5EF3A189C48F3469440A83026EC8ECD36EAD6EAF3B5D35663F8201BDE175413C" MinimumClientVersion="5.00.7804.1000" RandomizeMaxDays="7" ProgramEnabled="false" LastModifiedTime="30329258;3128053632" SiteVersionMatch="true" SiteVersion="5.00.7804.1000" EnablePeerCache="true"/></ContentLocationReply>' ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Failed to get DP locations as the expected version from MP 'sccm-cfg1.sccm.local'. Error 0x87d00215 ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Sending Fallback Status Point message to 'SCCM-CFG1', STATEID='101'. ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Failed to get client version for sending messages to FSP. Error 0x8004100e ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    Params to send FSP message '5.0.7804.1000 Deployment ' ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)
    State message with TopicType 800 and TopicId {40838B6E-D862-417D-BB74-12907358D8D9} has been sent to the FSP FSPStateMessage 10/18/2013 12:54:59 PM 1368 (0x0558)
    Next retry in 10 minute(s)... ccmsetup 10/18/2013 12:54:59 PM 1368 (0x0558)

    I looked in the logs I can see errors for the DP, the MP and FSP

    I reinstalled each of these roles many time, reinstall IIS and still can't figure it out.

    Can anybody help me out with this.

    Thank you

    Friday, October 18, 2013 4:57 PM

All replies

  • How are you initiating the client setup (I'm assuming client push)?

    Are the the site systems configured for HTTPS or HTTP?

    Is the MP healthy?


    Jason | http://blog.configmgrftw.com

    Friday, October 18, 2013 9:14 PM
  • hi, thanks for the reply i do use push agent site is configured to be http im not sure how to tell you if MP is healthy, im new to sccm so please bare with me. thanks again for your help
    Friday, October 18, 2013 9:24 PM
  • I'm in EXACTLY the same scenario and also getting the error 'Failed to get DP locations as the expected version from MP'.  Is there anyone out there that can help?

    Wednesday, November 27, 2013 12:14 PM
  • I changed the httpsstate to match the httpsstate from a working machine.  It's located at HKLM\SOFTWARE\Microsoft\CCM or HKLM\SOFTWARE\Wow6432Node\Microsoft\CCM on 64-bit clients.  In my case, it was 224, and I changed it to 192.  This resolved the issue.  There's more info here:

    http://social.technet.microsoft.com/Forums/en-US/67d85763-f787-4a8f-99c4-0ffa1a392829/client-install-via-wsus-fails?forum=configmanagerdeployment

    Monday, February 3, 2014 10:11 PM
  • what does the MPSetup log file say?  its located under configuration manager\logs
    Monday, February 3, 2014 10:27 PM
  • I was facing the same issue with this error code

    Failed to get DP locations as the expected version from MP 'sccm-cfg1.sccm.local'. Error 0x87d00215ccmsetup 10/18/2013 12:54:59 PM1368 (0x0558)
    Sending Fallback Status Point message to 'SCCM-CFG1', STATEID='101'.ccmsetup 10/18/2013 12:54:59 PM1368 (0x0558)
    Failed to get client version for sending messages to FSP. Error 0x8004100eccmsetup 10/18/2013 12:54:59 PM1368 (0x0558)

    On CM 2012 SP1 with CU4 installed, we redistributed the default Config Manager client package to all DP's and this fixed our issues.

    Hope this helps someone.

    • Proposed as answer by Ray Koukari Wednesday, September 23, 2015 2:28 PM
    Wednesday, August 27, 2014 11:18 PM
  • I know this is an old thread. But posting here so that it helps someone.

    I am just adding to what Rich has said earlier.

    To distribute the default config manager client package. First create a distribution point group if none exist from Administration-Distribution point groups. And add your distribute point to it. The select the config mgr client package from Software library-Packages and click distribute content in the top ribbon. Select your distribution group in the Specify content destination window.


    • Edited by Shrimp Taco Saturday, May 21, 2016 12:37 PM
    Saturday, May 21, 2016 12:36 PM
  • Sorry, but that's incorrect. The default client agent installation package is automatically and always distributed to *every* DP. You don't have to do anything at all. If this is not happening, then there us something failing that you need to troubleshoot.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Saturday, May 21, 2016 5:48 PM
  • That was my issue, the Client package had failed to distribute, fixed that and client install worked.
    Wednesday, December 14, 2016 3:27 PM
  • I had a similar issue, for whatever Reason my Distribution Point was not added to a Boundary Group. 

    Under Administration -- Distribution Points -- Boundary Groups --> ADD

    Hope this helps!

    Tuesday, April 9, 2019 4:39 PM