locked
Client failed to install RRS feed

  • Question

  • Can the sccm client installation be failed because of the versions in site server and AD are different? I thought info in AD schema would update itself as the site server upgraded to the newer version (from SP1 to R2). Do I need to manually update the AD schema (system management cn?). If so, is there a documentation steps to do it?

    Thank you,

    Pete G.

    Thursday, October 15, 2015 2:12 PM

Answers

  • If you get the the control panel applet, the issue is not installation as that's already done; the issue is communication.

    You need to review the client logs to start to troubleshoot. Start with locaitonservices.log, clientlocation.log, and clientidmanagerstartup.log.

    Also, keep in mind that's it normally takes around 3-5 minutes (sometimes longer depending upon a host of variables) after the client is successfully installed for it to complete its initial communication and show all of the actions as being available.


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

    Thursday, October 15, 2015 3:46 PM

All replies

  • The client install will not be impacted by the version of the site server being different - it should still install and the service should start. If the versions are too far mismatched there may be issues but so long as it is the same major version they should be able to talk to the server. Is the SMSSetup log showing an error message? 

    • Edited by agreer Thursday, October 15, 2015 2:54 PM
    Thursday, October 15, 2015 2:45 PM
  • The version of installer ccmsetup.exe from the site server is 7958.1401. When installed on the user machine, it shows 7958.1000 and don't have all the files, no xml file, only two actions (machine policy, user policy) and taking long - won't finish up the installation.

    Thank you,

    Pete G.

    Thursday, October 15, 2015 3:12 PM
  • If you get the the control panel applet, the issue is not installation as that's already done; the issue is communication.

    You need to review the client logs to start to troubleshoot. Start with locaitonservices.log, clientlocation.log, and clientidmanagerstartup.log.

    Also, keep in mind that's it normally takes around 3-5 minutes (sometimes longer depending upon a host of variables) after the client is successfully installed for it to complete its initial communication and show all of the actions as being available.


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

    Thursday, October 15, 2015 3:46 PM