locked
Unable to install Client on Device RRS feed

  • Question

  • When I attempt to push a client out, I get the below log, with the notable entry being:

    ---> Unable to connect to WMI (root\ccm) on remote machine "106-K", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:18 PM 1176 (0x0498)

    I've updated the schema, the account has domain admin access, windows firewall is disabled on the server and client.    No idea why I can't install the client.

    ======>Begin Processing request: "2097152126", machine name: "106-K" SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:17 PM 1176 (0x0498)
    Execute query exec [sp_IsMPAvailable] N'BC1' SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:17 PM 1176 (0x0498)
    ---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:17 PM 1176 (0x0498)
    ---> Attempting to connect to administrative share '\\106-K\admin$' using account 'bcon\sccm.agent' SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:17 PM 1176 (0x0498)
    ---> Connected to administrative share on machine 106-K using account 'bcon\sccm.agent' SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:17 PM 1176 (0x0498)
    ---> Attempting to make IPC connection to share <\\106-K\IPC$> SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:17 PM 1176 (0x0498)
    ---> Searching for SMSClientInstall.* under '\\106-K\admin$\' SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:17 PM 1176 (0x0498)
    ---> System OS version string "6.1.7601" converted to 6.10 SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:18 PM 1176 (0x0498)
    ---> Unable to connect to WMI (root\ccm) on remote machine "106-K", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:18 PM 1176 (0x0498)
    ---> Creating \ VerifyingCopying exsistance of destination directory \\106-K\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:18 PM 1176 (0x0498)
    ---> Copying client files to \\106-K\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:18 PM 1176 (0x0498)
    ---> Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\MobileClient.tcf" to "MobileClient.tcf" SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:18 PM 1176 (0x0498)
    ---> Copying file "C:\Program Files\Microsoft Configuration Manager\bin\I386\ccmsetup.exe" to "ccmsetup.exe" SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:18 PM 1176 (0x0498)
    ---> Updated service "ccmsetup" on machine "106-K". SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:18 PM 1176 (0x0498)
    ---> ERROR: Unable to start service "ccmsetup" on machine "106-K", error = 1068. SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:18 PM 1176 (0x0498)
    ---> Failed to install CCM Client Bootstrap component on client (1068) SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:18 PM 1176 (0x0498)
    ---> Deleting SMS Client Install Lock File '\\106-K\admin$\SMSClientInstall.BC1' SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:18 PM 1176 (0x0498)
    Execute query exec [sp_CP_SetLastErrorCode] 2097152126, 1068 SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:18 PM 1176 (0x0498)
    Stored request "2097152126", machine name "106-K", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:18 PM 1176 (0x0498)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152126, 2 SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:18 PM 1176 (0x0498)
    Execute query exec [sp_CP_SetLatest] 2097152126, N'03/20/2015 20:44:18', 24 SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:18 PM 1176 (0x0498)
    <======End request: "2097152126", machine name: "106-K". SMS_CLIENT_CONFIG_MANAGER 3/20/2015 3:44:18 PM 1176 (0x0498)

    Friday, March 20, 2015 8:47 PM

Answers

  • And it turns out BITS was disabled on the client PC.    Problem solved.
    • Marked as answer by Travis BC Friday, March 20, 2015 9:24 PM
    Friday, March 20, 2015 9:24 PM

All replies

  • I'm seeing now that it does install the ccmsetup service on the PC, but the service is not able to start.   When I attempt to manually start it, I get:

    Windows could not start the ccmsetup service on Local Computer.

    Error 1068: The dependency service or group failed to start.

    Friday, March 20, 2015 9:10 PM
  • And it turns out BITS was disabled on the client PC.    Problem solved.
    • Marked as answer by Travis BC Friday, March 20, 2015 9:24 PM
    Friday, March 20, 2015 9:24 PM