locked
Client Install Push failing RRS feed

  • Question

  • I don't really understand where the commandline arguments are coming from when I perform a Install Client push from SCCM Console to a single device. In the screenshot below, on the left is the failed install. I only checkmarked "Always install the client software" &  "Install the client software from a specified site" and choose the only site we have.

    The succesful manual log is on the right. It basically copies all the necessary files to the local end user device and then runs a command

    CCMSetup.exe /MP:SCCM.NCELEC.Local FSP=SCCM.NCELEC.Local SMSSITECODE=998

    I feel as though the Install Client push is picking up some Mobile setting we ar not even using at this time? Any suggestions would be helpful at this point thanks.


    Thank You, Joe

    Monday, September 24, 2012 7:55 PM

Answers

  • What's in the Installation Properties tab of the Client Push Installation Properties dialog? You get to it in the Administration workspace -> Overview -> Site Config -> Sites -> Site and then choosing Client Installation settings from the ribbon bar (or right-click context menu)?

    Jason | http://blog.configmgrftw.com

    • Marked as answer by joe_1974 Wednesday, September 26, 2012 3:20 PM
    Monday, September 24, 2012 8:28 PM

All replies

  • try changing your switch in the client push /MP needs to be lower case /mp. Upper case arguments apply to client.msi and will be passed on to client.msi where lowercase argurments can be applied in the ccmsetup.exe. The mobileclient.tcf file is normal when you perform a client push this file contains the client install settings. http://technet.microsoft.com/en-us/library/cc181242.aspx


    Justin | http://patchmypc.net | Please remember to mark as helpful/answer if this helped you



    Monday, September 24, 2012 8:03 PM
  • What's in the Installation Properties tab of the Client Push Installation Properties dialog? You get to it in the Administration workspace -> Overview -> Site Config -> Sites -> Site and then choosing Client Installation settings from the ribbon bar (or right-click context menu)?

    Jason | http://blog.configmgrftw.com

    • Marked as answer by joe_1974 Wednesday, September 26, 2012 3:20 PM
    Monday, September 24, 2012 8:28 PM
  • Justin,

    The manual install with the uppercase works fine for me. I am having issues with the push from the console. I have the machine in a boundary.

    Are you saying the console push reads my bat file with the uppercase /MP switch?


    Thank You, Joe

    Monday, September 24, 2012 8:57 PM
  • What's in the Installation Properties tab of the Client Push Installation Properties dialog? You get to it in the Administration workspace -> Overview -> Site Config -> Sites -> Site and then choosing Client Installation settings from the ribbon bar (or right-click context menu)?

    Jason | http://blog.configmgrftw.com

    Jason,

    Thanks. It has the uppercase there. I wil update that and try the push again. Thanks!


    Thank You, Joe

    Monday, September 24, 2012 9:38 PM
  • I change the mp to lowercase then click apply and it gets changed back to uppercase so I don't think that is it.

    Thank You, Joe

    Monday, September 24, 2012 9:42 PM
  • So, you put /mp in that Installation Properties text box?

    Why?

    /mp is a parameter for ccmsetup that tells ccmsetup where to download the files it needs from using BITS. It does *not* set the MP.

    Only valid properties for client.msi can be placed in that Install Properties text box. If you would like to force the MP, use SMSMP.

    The full list of valid properties is at http://technet.microsoft.com/en-us/library/gg699356.aspx

    (anything with a slash, is a parameter for ccmsetup, anything in all caps and without the preceding slash is an MSI property).


    Jason | http://blog.configmgrftw.com

    Tuesday, September 25, 2012 12:51 AM
  • Thanks Jason, not sure if that was the issue or if our server just needed rebooting. But I can remote push agent now.

    I removed the " /MP:SCCM.NCELEC.Local" from the Client Push Installation settings<o:p></o:p>

    Applied Windows updates on the SCCM server and rebooted; then performed the push successfully.

    <o:p> </o:p>


    Thank You, Joe

    Wednesday, September 26, 2012 3:21 PM