locked
Clients having issues with auto push deployments RRS feed

  • Question

  • I have a SCCM 2012 SP2 (5.0.8239.1000) server that refuses to install clients after the machine is discovered during the AD Systems discovery.

    The client will show up in the All systems collection with our site code, but it will not deploy.

    When i look at the ccm.log There is no movement at all. It only seems to keep showing a bunch of clients it fails to install to, but none of them are new machines.

    Right clicking and deploying the client to the machine works fine, and i can see in the ccm.log file that it connects and installs, so no issues.

    The network team shows no blocked traffic from the Server to the client. We do not use Windows firewall, and there was no AV client installed on this particular client.

    This auto deployment "used" to work, albeit it wasn't consistent. This also happens at all 3 of our sites (1 Primary, and 2 DPs)

    Is there anything else I may be able to look at to troubleshoot this issue? Besides getting rid of this version of SCCM!

    Friday, January 26, 2018 6:53 PM

All replies

  • What OS are the clients running?

    Are you sure that the ccm.log isn't just hitting its default 2MB limit and rolling over?

    On a side note, you should at least install CU4 for 2012 SP2.


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

    Friday, January 26, 2018 7:35 PM
  • Hi,

    You should have selected "Enable automatic site-wide client push installation", please make sure that the "Servers" and  "Workstations" have also been selected.(e.g. image)



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

    Monday, January 29, 2018 9:51 AM
  • "The network team shows no blocked traffic from the Server to the client. We do not use Windows firewall, and there was no AV client installed on this particular client."

    you still Should see information in the ccm.log.

    Monday, January 29, 2018 9:55 AM
  • The clients are running Windows 7 SP1.

    I have looked at both .log and _log files and I see no action whatsoever.

    I agree that I need to update to the latest CU... there are circumstances outside of my control that do not allow me to upgrade to the latest version (company politics).

    Monday, January 29, 2018 7:18 PM
  • All of these options are checked off already.
    Monday, January 29, 2018 7:18 PM
  • I agree. The only thing i see is a bunch of errors it trying to install on machines that are not on the network anymore. Which seems odd to me that it still tries for these machines, but nothing new.

    But as soon as I click install in the console, I then see data about that machine appear in the ccm.log file.

    I am just not sure that process... once the system is detected by AD System Discovery, and the system shows up in All Systems with the Site code, it should at some point start the client installation...

    Monday, January 29, 2018 7:20 PM
  • > "I have looked at both .log and _log files and I see no action whatsoever."

    That doesn't mean the applicable entries have rolled out of both logs.

    If there is an AD resource, that resource is assigned to the site performing the client push, and auto-push is enabled, I've never seen a case where ccm.log doesn't show the activity.

    Next step is to increase the log file size and then check again.


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

    Monday, January 29, 2018 9:44 PM
  • Hi Jason,

    I increased the log files of the SMS_CLIENT_CONFIG_MANAGER... and stared at it hoping to see this particular machine show up.

    All i can see is a bunch of machines that are retrying to install the client on which fails with errors such as "machine does not exist on the network"

    ---> ERROR: Unable to access target machine for request: "2097168894", machine name: "00C017525615",  access denied or invalid network path. SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:06 AM 3236 (0x0CA4)
    Execute query exec [sp_CP_SetLastErrorCode] 2097168894, 53 SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:06 AM 3236 (0x0CA4)
    Stored request "2097168894", machine name "00C017525615", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:06 AM 3236 (0x0CA4)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097168894, 2 SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:06 AM 3236 (0x0CA4)
    Execute query exec [sp_CP_SetLatest] 2097168894, N'01/30/2018 13:43:06', 20 SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:06 AM 3236 (0x0CA4)
    <======End request: "2097168894", machine name: "00C017525615". SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:06 AM 3236 (0x0CA4)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account Domain\ServiceAccount (00000035) SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:11 AM 5524 (0x1594)
    ---> The device 16-0642.domain does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:11 AM 5524 (0x1594)
    ---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:11 AM 5524 (0x1594)
    ---> Attempting to connect to administrative share '\\16-0642\admin$' using account 'DOMAIN\ServiceAccount' SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:11 AM 5524 (0x1594)
    ---> WNetAddConnection2 failed (LOGON32_LOGON_NEW_CREDENTIALS) using account DOMAIN\ServiceAccount (00000035) SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:33 AM 5524 (0x1594)
    ---> The device 16-0642 does not exist on the network. Giving up SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:33 AM 5524 (0x1594)
    ---> ERROR: Unable to access target machine for request: "16787217", machine name: "16-0642",  access denied or invalid network path. SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:33 AM 5524 (0x1594)
    Execute query exec [sp_CP_SetLastErrorCode] 16787217, 53 SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:33 AM 5524 (0x1594)
    Stored request "16787217", machine name "16-0642", in queue "Retry". SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:33 AM 5524 (0x1594)

    Execute query exec [sp_CP_SetPushRequestMachineStatus] 16787217, 2 SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:33 AM 5524 (0x1594)

    Execute query exec [sp_CP_SetLatest] 16787217, N'01/30/2018 13:43:33', 33 SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:33 AM 5524 (0x1594)
    <======End request: "16787217", machine name: "16-0642". SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:33 AM 5524 (0x1594)
    CCR count in queue "Retry" is 19. SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:34 AM 14184 (0x3768)
    Sleeping for 618 seconds... SMS_CLIENT_CONFIG_MANAGER 1/30/2018 8:43:34 AM 14184 (0x3768)

    It will loop through this, and go through about maybe 20ish systems all failing but the machine that I am looking for, which was added to the domain yesterday, is not showing up in the log files as attempting to have the client install.

    It never seems to show any "NEWLY" discovered machines. But if i go in the console and push the install to this machine, I will then start to see the information that it communicated with the machine and the client is being installed. I did this on 2 other previous machines, which is why i am stumped.

    Is there another log file that i can look at that may shed more light on this?

    Tuesday, January 30, 2018 2:03 PM
  • This is what happens when we go into the console to force the install (this is a machine that was added to the domain last week)

    Waiting for change in directory "d:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:19:49 AM 29544 (0x7368)
    Execute query exec [sp_CP_GetNewPushMachines] N'GDC' SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:02 AM 29544 (0x7368)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097170076, 1 SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:02 AM 29544 (0x7368)
    Execute query exec [sp_CP_GetPushRequestMachine] 2097170076 SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:03 AM 29544 (0x7368)
    Successfully retrieved information for machine 17-0564 from DB SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:03 AM 29544 (0x7368)
    Execute query exec [sp_CP_GetPushRequestMachineIP] 2097170076 SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:03 AM 29544 (0x7368)
    Execute query exec [sp_CP_GetPushRequestMachineResource] 2097170076 SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:03 AM 29544 (0x7368)
    Execute query exec [sp_CP_GetPushMachineName] 2097170076 SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:03 AM 29544 (0x7368)
    Received request: "2097170076" for machine name: "17-0564" on queue: "Incoming". SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:03 AM 29544 (0x7368)
    Stored request "2097170076", machine name "17-0564", in queue "Processing". SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:03 AM 29544 (0x7368)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097170076, 1 SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:03 AM 29544 (0x7368)
    ----- Started a new CCR processing thread. Thread ID is 0x3fec. There are now 1 processing threads SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:05 AM 29544 (0x7368)
    Submitted request successfully SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:05 AM 29544 (0x7368)
    Getting a new request from queue "Incoming" after 100 millisecond delay. SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:05 AM 29544 (0x7368)
    Waiting for change in directory "d:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:05 AM 29544 (0x7368)
    ======>Begin Processing request: "2097170076", machine name: "17-0564" SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:05 AM 16364 (0x3FEC)
    Execute query exec [sp_IsMPAvailable] N'GDC' SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:05 AM 16364 (0x3FEC)
    ---> Trying each entry in the SMS Client Remote Installation account list SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:05 AM 16364 (0x3FEC)
    ---> Attempting to connect to administrative share '\\17-0564\admin$' using account 'Domain\ServiceAccount' SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:05 AM 16364 (0x3FEC)
    ---> Connected to administrative share on machine 17-0564 using account 'Domain\ServiceAccount' SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:05 AM 16364 (0x3FEC)
    ---> Attempting to make IPC connection to share <\\17-0564\IPC$> SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:05 AM 16364 (0x3FEC)
    ---> Searching for SMSClientInstall.* under '\\17-0564\admin$\' SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:05 AM 16364 (0x3FEC)
    ---> System OS version string "6.1.7601" converted to 6.10 SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:05 AM 16364 (0x3FEC)
    ---> Unable to connect to WMI (root\ccm) on remote machine "17-0564", error = 0x8004100e. SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:05 AM 16364 (0x3FEC)
    ---> Creating \ VerifyingCopying existence of destination directory \\17-0564\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:06 AM 16364 (0x3FEC)
    ---> Copying client files to \\17-0564\admin$\ccmsetup. SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:06 AM 16364 (0x3FEC)
    ---> Copying file "d:\Program Files\Microsoft Configuration Manager\bin\I386\MobileClient.tcf" to "MobileClient.tcf" SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:06 AM 16364 (0x3FEC)
    ---> Copying file "d:\Program Files\Microsoft Configuration Manager\bin\I386\ccmsetup.exe" to "ccmsetup.exe" SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:06 AM 16364 (0x3FEC)
    ---> ForceReinstall flag is set to true SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:06 AM 16364 (0x3FEC)
    ---> Created service "ccmsetup" on machine "17-0564". SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:06 AM 16364 (0x3FEC)
    ---> Started service "ccmsetup" on machine "17-0564". SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:06 AM 16364 (0x3FEC)
    ---> Deleting SMS Client Install Lock File '\\17-0564\admin$\SMSClientInstall.GDC' SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:06 AM 16364 (0x3FEC)
    Execute query exec [sp_CP_SetLastErrorCode] 2097170076, 0 SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:06 AM 16364 (0x3FEC)
    ---> Completed request "2097170076", machine name "17-0564". SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:06 AM 16364 (0x3FEC)
    Deleted request "2097170076", machine name "17-0564" SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:06 AM 16364 (0x3FEC)
    Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097170076, 4 SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:06 AM 16364 (0x3FEC)
    Execute query exec [sp_CP_SetLatest] 2097170076, N'01/30/2018 16:30:06', 1 SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:06 AM 16364 (0x3FEC)
    <======End request: "2097170076", machine name: "17-0564". SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:30:06 AM 16364 (0x3FEC)
    Execute query exec [sp_CP_CheckNewAssignedMachine] N'GDC', 1 SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:33:26 AM 29544 (0x7368)
    Waiting for change in directory "d:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout). SMS_CLIENT_CONFIG_MANAGER 1/30/2018 11:33:26 AM 29544 (0x7368)

    I have verified that the client has been installed on this machine.

    Tuesday, January 30, 2018 4:39 PM
  • And you are sure that the resource in the console shows the site code for your primary site?

    Also, if you add the operating system column, what operating system is listed?


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

    Tuesday, January 30, 2018 11:10 PM
  • Hi Jason,

    Yup it shows under All Systems with the Sitecode, and the Operating System shows 6.1.

    I am not sure what else could be causing this... maybe I need to get Microsoft involved at this point.

    I believe it has been an issue since just before Christmas, but was only just recently told about the issue from our Help Desk..

    Very bizarre behaviour.

    Wednesday, January 31, 2018 2:12 PM
  • Operating system shows just "6.1"?

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

    Wednesday, January 31, 2018 7:34 PM
  • Yes... now that you kinda questioned that I went and checked both types of clients to make sure...

    In the client Properties for the machine that is not auto-installing the client, it shows under the Property "Operating System Name and Version" says "6.1"

    On clients that have it installed say "Microsoft Windows NT Workstation 6.1"

    In the All systems under the Operating System Column it shows what is displayed in the "Operating System Name and Version" accordingly.

    The systems are doing AD System Discovery and Network Discovery

    Is it possible that something with the discovery is causing an issue?

    Wednesday, January 31, 2018 8:56 PM