locked
Client failing to install RRS feed

  • Question

  • Hi

    I’ve been attempting to setup our first SCCM server in our company and have hit a brick wall.

    I’ve installed a standalone primary site, issued it a certificate from our internal CA, created a boundary based on our offices AD site. I’ve also set the site to be a distribution point as well as set it as a fallback site.

    The laptop I’m trying to deploy it to has been used a computer certificate from our internal CA. It’ doesn’t have any AV installed and the firewall has been disabled to prevent interference.

    When I try to push the client out, it fails to copy the client to the C:\Windows\ccmssetup folder. It copies the ccmsetup.exe file and creates the MobileClient.tcf and MobileClientUnicode.tcf. However, no other files are copied and therefore cannot execute.

    I just tried posting with the ccmsetup.log but I couldn’t because it’s more than 60,000 characters. However, I believe these are the lines showing where it’s failing, which appear after it validates the certificate:

    <![LOG[Failed to receive ccm message response. Status code = 403]LOG]!><time="17:25:32.552-60" date="08-20-2015" component="ccmsetup" context="" type="2" thread="4388" file="httphelper.cpp:1694">

    <![LOG[GetDPLocations failed with error 0x80004005]LOG]!><time="17:25:32.552-60" date="08-20-2015" component="ccmsetup" context="" type="3" thread="4388" file="siteinfo.cpp:532">

    <![LOG[Failed to get DP locations as the expected version from MP 'HTTPS://SCCM.domain.local'. Error 0x80004005]LOG]!><time="17:25:32.552-60" date="08-20-2015" component="ccmsetup" context="" type="2" thread="4388" file="ccmsetup.cpp:11261">

    <![LOG[A Fallback Status Point has not been specified.  Message with STATEID='101' will not be sent.]LOG]!><time="17:25:32.552-60" date="08-20-2015" component="ccmsetup" context="" type="1" thread="4388" file="ccmsetup.cpp:9763">

    <![LOG[Next retry in 10 minute(s)...]LOG]!><time="17:25:32.552-60" date="08-20-2015" component="ccmsetup" context="" type="0" thread="4388" file="ccmsetup.cpp:8835">

    Any help would be greatly appreciated.

    Friday, August 21, 2015 12:52 PM

Answers

  • After days of hunting, I solved the problem by following the guidance in the article below. Thanks for all the suggestions, it's really tricky to narrow down where the problem is as it encompasses so many different components

    http://blogs.technet.com/b/configurationmgr/archive/2013/08/13/support-tip-a-configmgr-2012-management-point-enabled-for-ssl-fails-with-403-forbidden.aspx

    • Edited by Daverino Friday, August 21, 2015 3:29 PM Forgot URL
    • Proposed as answer by Richard.Knight Friday, August 21, 2015 4:43 PM
    • Marked as answer by Joyce L Monday, August 24, 2015 8:54 AM
    Friday, August 21, 2015 3:28 PM

All replies

  • Hi,

    is the site information published in AD? Have you created Boundary and Boundary group for the network the client is on?

    Also what command-line did you use to install the client?

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Friday, August 21, 2015 1:16 PM
  • Thanks for replying.

    The SCCM server is in the same subnet and AD site as the client. The site data is published to AD ( there is a CN=SMS-Site-CCS entry in CN=System Management,CN=System container)

    I didn't use a command-line to install, I'm attempting to use the Client-Push from the SCCM console.

    I created a test environment using the Microsoft test lab documents and everything worked fine, including the client install but when using the same procedure on our production network (obviously making the appropriate changes based on IP addresses etc) it's failing.

    The IIS logs mention a lot of the errors below:

    fe80::omitted:ccb6%12 GET /SMS_MP/.sms_aut MPLIST 443 - fe80::omitted:ccb6%12 SMS_MP_CONTROL_MANAGER - 403 16 2148204809 5381 16

    However, these errors appear in my test environment and everything there works fine.

    Friday, August 21, 2015 2:11 PM
  • Well you are getting this error :Status code = 403

    HTTP 403.x-Forbidden would it be possible to look at the IIS log of the MP to see what the reason is ?

    Friday, August 21, 2015 3:02 PM
  • After days of hunting, I solved the problem by following the guidance in the article below. Thanks for all the suggestions, it's really tricky to narrow down where the problem is as it encompasses so many different components

    http://blogs.technet.com/b/configurationmgr/archive/2013/08/13/support-tip-a-configmgr-2012-management-point-enabled-for-ssl-fails-with-403-forbidden.aspx

    • Edited by Daverino Friday, August 21, 2015 3:29 PM Forgot URL
    • Proposed as answer by Richard.Knight Friday, August 21, 2015 4:43 PM
    • Marked as answer by Joyce L Monday, August 24, 2015 8:54 AM
    Friday, August 21, 2015 3:28 PM