none
Client installation failing in multiple servers with below error code. Any leads pls? RRS feed

  • Question

  • Current AD site of machine is SHA ccmsetup 9/20/2019 1:02:50 AM 6416 (0x1910)
    Attempting to query AD for assigned site code ccmsetup 9/20/2019 1:02:50 AM 6416 (0x1910)
    Performing AD query: '(&(ObjectCategory=MSSMSRoamingBoundaryRange)(|(&(MSSMSRangedIPLow<=2887354747)(MSSMSRangedIPHigh>=2887354747))))' ccmsetup 9/20/2019 1:02:50 AM 6416 (0x1910)
    Performing AD query: '(&(ObjectCategory=mSSMSSite)(|(mSSMSRoamingBoundaries=172.25.137.0)(mSSMSRoamingBoundaries=SHA)))' ccmsetup 9/20/2019 1:02:50 AM 6416 (0x1910)
    Failed to get assigned site from AD. Error 0x80004005 ccmsetup 9/20/2019 1:02:50 AM 6416 (0x1910)
    GetADInstallParams failed with 0x80004005 ccmsetup 9/20/2019 1:02:50 AM 6416 (0x1910)
    Couldn't find an MP source through AD. Error 0x80004005 ccmsetup 9/20/2019 1:02:50 AM 6416 (0x1910)
    No valid source or MP locations ccmsetup 9/20/2019 1:02:50 AM 6416 (0x1910)
    Updating MDM_ConfigSetting.ClientDeploymentErrorCode with value 2147500037 ccmsetup 9/20/2019 1:02:50 AM 6416 (0x1910)
    OS is not Win10RS3+, ENDOK. ccmsetup 9/20/2019 1:02:50 AM 6416 (0x1910)
    Failed to get client version for sending state messages. Error 0x8004100e ccmsetup 9/20/2019 1:02:50 AM 6416 (0x1910)
    [] Params to send '5.0.8790.1008 Deployment "C:\Windows\ccmsetup\ccmsetup.exe"' ccmsetup 9/20/2019 1:02:50 AM 6416 (0x1910)
    A Fallback Status Point has not been specified and no client was installed.  Message with STATEID='322' will not be sent. ccmsetup 9/20/2019 1:02:50 AM 6416 (0x1910)
    Failed to send status 322. Error (87D00215) ccmsetup 9/20/2019 1:02:50 AM 6416 (0x1910)
    Failed to connect to policy namespace. Error 0x8004100e ccmsetup 9/20/2019 1:02:50 AM 6416 (0x1910)
    Failed to revoke client upgrade local policy. Error 0x8004100e ccmsetup 9/20/2019 1:02:50 AM 6416 (0x1910)
    Updating MDM_ConfigSetting.ClientDeploymentErrorCode with value 2147500037 ccmsetup 9/20/2019 1:02:50 AM 6416 (0x1910)
    OS is not Win10RS3+, ENDOK. ccmsetup 9/20/2019 1:02:50 AM 6416 (0x1910)
    CcmSetup failed with error code 0x80004005 ccmsetup 9/20/2019 1:02:50 AM 6416 (0x1910)

    • Edited by Sanju144 Friday, September 20, 2019 12:17 PM
    Friday, September 20, 2019 11:48 AM

All replies

  • Hi,

    Check the configuration of your boundaries and boundary groups, don't forget to specify the MP/DP in the boundary group.

    You can refer to this: https://www.prajwaldesai.com/configuring-discovery-and-boundaries-in-configuration-manager-2012-r2/

    Regards,

    SAAD Youssef

    ______

    Please remember to mark the replies as answer if they help, thank you!

    Friday, September 20, 2019 1:30 PM
  • How exactly are you performing the installation?

    Jason | https://home.configmgrftw.com | @jasonsandys

    Friday, September 20, 2019 2:58 PM
  • Hi,

    1.May we know if you're using client PUSH installation? If yes, please try specifying the site instead of "auto" specifying.  

    2. Please create a boundary and boundary group in SCCM that matches with where your client resides to have a try. Also associate the MP/DP with the boundary group. 

    3. Is there a firewall in the mix blocking communication? Can you ping the primary site server using both NetBios and FQDN names from the client after it fails? Can you also ping the client from the primary site server?

    4. Also try removing all traces of the failed client installation by removing the directories like ccmsetup and ccm and restart setup.

    Hope my answer could help you. Thanks for your time.

    Best regards,
    Simon Ren

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, September 23, 2019 8:14 AM
  • Hi,

    May we know the current status of the question? If there is any other assistance we can provide, please feel free to let us know, we will do our best to help you.

    Thanks and regards,
    Simon 

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, September 24, 2019 1:40 AM
  • Checked the boundary and it is all fine and MP/DPs are specified in Boundary group 
    Friday, September 27, 2019 5:33 AM
  • I'll check the instructions and get back. Thanks 
    Friday, September 27, 2019 5:34 AM
  • Manual installation
    Friday, September 27, 2019 5:55 AM
  • Manual installation

    Try a manual installation with the following command line, then check the ccmsetup.log file.

    • CCMSetup.exe /mp:SMSMP01 SMSSITECODE=S01

    * Change "SMSMP01" with the FQDN of your Management Point.
    * Change "S01" with your SCCM Site Code.

    Friday, September 27, 2019 7:08 AM
  • Always supply SMSMP as well as /mp is not sufficient and does not set the MP.

    Jason | https://home.configmgrftw.com | @jasonsandys

    Friday, September 27, 2019 12:50 PM
  • For us to help you, you need to provide complete information. A two word answer is far from that.

    Are you simply double-clicking on ccmsetup?

    Are you trying to run client.msi?

    Are you running a script?

    Are you manually entering a command-line?

    Troubleshooting is about information and details. Not providing those means we really can't help mush if at all.



    Jason | https://home.configmgrftw.com | @jasonsandys

    Friday, September 27, 2019 12:53 PM
  • What kind of boundaries are you using?

    If IP subnets, change them to IP address ranges.


    Jason | https://home.configmgrftw.com | @jasonsandys

    Friday, September 27, 2019 12:56 PM
  • Hi,

    Just checking in to see if there is any other assistance we can provide. If there are no other questions, would you please help close this case? Thanks for your time.

    Thanks and regards,
    Simon

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, October 4, 2019 7:15 AM