Automatic Client Push

We recently migrated from SCCM 2007 to SCCM 2012 R2.  I did the migration by manually pushing out clients, and now that a majority are migrated, I enabled Automatic Client Push.  However, resources that were already discovered without the client
installed aren't receiving the client.  Checking CCM.log on the primary site server, I don't see SCCM even attempting to push the client.
Any ideas?

Can you post a portion of the ccm.log?
I apparently can't post much of it.  The workstations that are failing are ones I pushed to manually the day prior.  This is from the point of enabling automatic client push, and a bit afterwards:
Waking up for site control file directory change notification  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:33.896+360><thread=17076 (0x42B4)>
The Site Control File has changed, parameters will be reread.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:33.965+360><thread=17076 (0x42B4)>
Updating Site Parameters  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:33.984+360><thread=17076 (0x42B4)>
~MP Ports: 80  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:33.998+360><thread=17076 (0x42B4)>
~IISPreferedPort: 80  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.012+360><thread=17076 (0x42B4)>
~MP SSL Ports: 443  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.025+360><thread=17076 (0x42B4)>
~IISSSLPreferedPort: 443  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.040+360><thread=17076 (0x42B4)>
~Default MP: SCCM.Domain.com  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.053+360><thread=17076 (0x42B4)>
~Default MP Type: 1  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.067+360><thread=17076 (0x42B4)>
~Default MP: [None]  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.081+360><thread=17076 (0x42B4)>
~Certificate Selection Criteria:   $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.094+360><thread=17076 (0x42B4)>
~Certificate Store:   $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.107+360><thread=17076 (0x42B4)>
~SSL State: 224  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.120+360><thread=17076 (0x42B4)>
~Select First Certificate: 1  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.134+360><thread=17076 (0x42B4)>
~Certificate Issuers:   $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.159+360><thread=17076 (0x42B4)>
Checking configuration information for server: SCCM.Domain.COM.~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.174+360><thread=17076 (0x42B4)>
~No Fallback Status Point installed on the Site  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.187+360><thread=17076 (0x42B4)>
~Install on DC: True  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.200+360><thread=17076 (0x42B4)>
~Option for installing using IP address: 0  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.214+360><thread=17076 (0x42B4)>
Retrieving properties from the site control file.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.226+360><thread=17076 (0x42B4)>
~Advanced Client Command Line: SMSSITECODE=STE  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.239+360><thread=17076 (0x42B4)>
  Ignoring unrecognized property "Advanced Client Command Line Default"  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.253+360><thread=17076 (0x42B4)>
~Security Mode Option - CCR buffering disabled.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.266+360><thread=17076 (0x42B4)>
~Default Client Type: -1  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.279+360><thread=17076 (0x42B4)>
Sleeping for 981 seconds...  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 18:57:34.300+360><thread=17076 (0x42B4)>
CCM Shutting down (12)~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:11:12.799+360><thread=10212 (0x27E4)>
No request returned from queue  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:11:12.836+360><thread=10212 (0x27E4)>
CCM Shutting down... (4)~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:11:12.850+360><thread=17076 (0x42B4)>
CCM Main thread is exiting...~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:11:12.908+360><thread=17076 (0x42B4)>
SMS_EXECUTIVE started SMS_CLIENT_CONFIG_MANAGER as thread ID 2664 (0xA68).  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.269+360><thread=16000 (0x3E80)>
************** Client Config Manager main thread starting **************  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.294+360><thread=2664 (0xA68)>
This site: "STE".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.308+360><thread=2664 (0xA68)>
This site type: "1".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.324+360><thread=2664 (0xA68)>
This machine: "SCCM.Domain.com".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.338+360><thread=2664 (0xA68)>
The Site Control File has changed, parameters will be reread.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.498+360><thread=2664 (0xA68)>
Updating Site Parameters  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.570+360><thread=2664 (0xA68)>
~MP Ports: 80  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.615+360><thread=2664 (0xA68)>
~IISPreferedPort: 80  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.630+360><thread=2664 (0xA68)>
~MP SSL Ports: 443  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.644+360><thread=2664 (0xA68)>
~IISSSLPreferedPort: 443  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.658+360><thread=2664 (0xA68)>
~Default MP: SCCM.Domain.com  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.680+360><thread=2664 (0xA68)>
~Default MP Type: 1  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.693+360><thread=2664 (0xA68)>
~Default MP: [None]  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.705+360><thread=2664 (0xA68)>
~Certificate Selection Criteria:   $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.718+360><thread=2664 (0xA68)>
~Certificate Store:   $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.732+360><thread=2664 (0xA68)>
~SSL State: 224  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.745+360><thread=2664 (0xA68)>
~Select First Certificate: 1  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.758+360><thread=2664 (0xA68)>
~Certificate Issuers:   $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.774+360><thread=2664 (0xA68)>
Checking configuration information for server: SCCM.Domain.COM.~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.788+360><thread=2664 (0xA68)>
~No Fallback Status Point installed on the Site  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.801+360><thread=2664 (0xA68)>
~Install on DC: True  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.819+360><thread=2664 (0xA68)>
~Option for installing using IP address: 0  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.845+360><thread=2664 (0xA68)>
Retrieving properties from the site control file.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.864+360><thread=2664 (0xA68)>
~Advanced Client Command Line: SMSSITECODE=STE  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.878+360><thread=2664 (0xA68)>
  Ignoring unrecognized property "Advanced Client Command Line Default"  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.893+360><thread=2664 (0xA68)>
~Security Mode Option - CCR buffering disabled.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.914+360><thread=2664 (0xA68)>
~Default Client Type: -1  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.927+360><thread=2664 (0xA68)>
Confirming all required files are available on the site server~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.942+360><thread=2664 (0xA68)>
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.965+360><thread=2664 (0xA68)>
  Site Server Name             "\\SCCM.Domain.com"    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:56.980+360><thread=2664 (0xA68)>
  Site Code                    "STE"    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.020+360><thread=2664 (0xA68)>
  CCM Account 1                "Domain\clientdeploy"    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.054+360><thread=2664 (0xA68)>
  CCM Account 2                "Domain2\clientdeploy"    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.067+360><thread=2664 (0xA68)>
  CCM Account 3                "<end of list>"    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.081+360><thread=2664 (0xA68)>
  Max CCR Processing Threads    10     $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.095+360><thread=2664 (0xA68)>
  CCR Processing Thread Timeout 600000 ms  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.108+360><thread=2664 (0xA68)>
  Sitewide Travel Mode Switch   USE CLIENT SETTING  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.131+360><thread=2664 (0xA68)>
  Days Between Account Cleanups 30  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.143+360><thread=2664 (0xA68)>
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.156+360><thread=2664 (0xA68)>
Parameters for queue: "Incoming"  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.168+360><thread=2664 (0xA68)>
  Inbox Path                   "E:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box"    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.181+360><thread=2664
(0xA68)>
  Read Queue Every             DIR CHANGE NOTIFICATION    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.193+360><thread=2664 (0xA68)>
  Retry CCR For                168 Hours    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.206+360><thread=2664 (0xA68)>
  Report Error After           ERROR REPORTING OFF    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.219+360><thread=2664 (0xA68)>
  Warn when Queue Exceeds      100  CCRs    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.246+360><thread=2664 (0xA68)>
  Delay Between CCRs           100 Millisec    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.259+360><thread=2664 (0xA68)>
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.271+360><thread=2664 (0xA68)>
Parameters for queue: "Retry"  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.284+360><thread=2664 (0xA68)>
  Inbox Path                   "E:\Program Files\Microsoft Configuration Manager\inboxes\ccrretry.box"    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.297+360><thread=2664
(0xA68)>
  Read Queue Every             60 Minutes    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.310+360><thread=2664 (0xA68)>
  Retry CCR For                168 Hours    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.323+360><thread=2664 (0xA68)>
  Report Error After           24 Hours    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.336+360><thread=2664 (0xA68)>
  Warn when Queue Exceeds      150  CCRs    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.349+360><thread=2664 (0xA68)>
  Delay Between CCRs           100 Millisec    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.361+360><thread=2664 (0xA68)>
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.374+360><thread=2664 (0xA68)>
Parameters for queue: "Processing"  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.387+360><thread=2664 (0xA68)>
  Inbox Path                   "E:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box\InProc"    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.389+360><thread=2664
(0xA68)>
  Read Queue Every             DIR CHANGE NOTIFICATION    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.415+360><thread=2664 (0xA68)>
  Retry CCR For                CCR DOESN'T EXPIRE    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.428+360><thread=2664 (0xA68)>
  Report Error After           ERROR REPORTING OFF    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.440+360><thread=2664 (0xA68)>
  Warn when Queue Exceeds      150  CCRs    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.453+360><thread=2664 (0xA68)>
  Delay Between CCRs           0 Millisec    $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.466+360><thread=2664 (0xA68)>
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.478+360><thread=2664 (0xA68)>
Moving CCRs from processing queue to incoming queue~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.491+360><thread=2664 (0xA68)>
Started Incoming Queue Thread, ThreadId = 2488  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.505+360><thread=2664 (0xA68)>
Started Retry Queue Thread, ThreadId = 1548  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.518+360><thread=2664 (0xA68)>
Sleeping for 300 seconds...  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.531+360><thread=2664 (0xA68)>
THREAD_ProcessQ starting, Input Queue ID is 0.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.551+360><thread=9352 (0x2488)>
  Queue Name is "Incoming".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.632+360><thread=9352 (0x2488)>
  Queue Directory is "E:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.697+360><thread=9352 (0x2488)>
Sleeping for 300 seconds before processing requests on queue Incoming...  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.711+360><thread=9352 (0x2488)>
THREAD_ProcessQ starting, Input Queue ID is 1.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.531+360><thread=5448 (0x1548)>
  Queue Name is "Retry".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.773+360><thread=5448 (0x1548)>
  Queue Directory is "E:\Program Files\Microsoft Configuration Manager\inboxes\ccrretry.box".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.785+360><thread=5448 (0x1548)>
Sleeping for 480 seconds before processing requests on queue Retry...  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:13:57.804+360><thread=5448 (0x1548)>
~Waking up for site control file directory change notification  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.148+360><thread=2664 (0xA68)>
The Site Control File has not changed since the last parameter update.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.170+360><thread=2664 (0xA68)>
Updating Site Parameters  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.183+360><thread=2664 (0xA68)>
~MP Ports: 80  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.200+360><thread=2664 (0xA68)>
~IISPreferedPort: 80  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.247+360><thread=2664 (0xA68)>
~MP SSL Ports: 443  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.260+360><thread=2664 (0xA68)>
~IISSSLPreferedPort: 443  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.279+360><thread=2664 (0xA68)>
~Default MP: SCCM.Domain.com  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.298+360><thread=2664 (0xA68)>
~Default MP Type: 1  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.311+360><thread=2664 (0xA68)>
~Default MP: [None]  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.324+360><thread=2664 (0xA68)>
~Certificate Selection Criteria:   $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.337+360><thread=2664 (0xA68)>
~Certificate Store:   $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.351+360><thread=2664 (0xA68)>
~SSL State: 224  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.364+360><thread=2664 (0xA68)>
~Select First Certificate: 1  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.379+360><thread=2664 (0xA68)>
~Certificate Issuers:   $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.392+360><thread=2664 (0xA68)>
Checking configuration information for server: SCCM.Domain.COM.~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.411+360><thread=2664 (0xA68)>
~No Fallback Status Point installed on the Site  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.494+360><thread=2664 (0xA68)>
~Install on DC: True  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.520+360><thread=2664 (0xA68)>
~Option for installing using IP address: 0  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.535+360><thread=2664 (0xA68)>
Sleeping for 282 seconds...  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:14:15.557+360><thread=2664 (0xA68)>
CCR count in queue "Incoming" is 0.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:18:57.577+360><thread=2664 (0xA68)>
CCR count in queue "Processing" is 0.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:18:57.590+360><thread=2664 (0xA68)>
Sleeping for 300 seconds...  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:18:57.603+360><thread=2664 (0xA68)>
Getting a new request from queue "Incoming" after 100 millisecond delay.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:18:57.733+360><thread=9352 (0x2488)>
Waiting for change in directory "E:\Program Files\Microsoft Configuration Manager\inboxes\ccr.box" for queue "Incoming", (30 minute backup timeout).  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:18:57.746+360><thread=9352
(0x2488)>
Getting a new request from queue "Retry" after 100 millisecond delay.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:57.827+360><thread=5448 (0x1548)>
Execute query exec [sp_CP_GetPushRequestMachine] 2097152351~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:57.944+360><thread=5448 (0x1548)>
Successfully retrieved information for machine workstation2 from DB  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:57.957+360><thread=5448 (0x1548)>
Execute query exec [sp_CP_GetPushRequestMachineIP] 2097152351~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:57.969+360><thread=5448 (0x1548)>
Execute query exec [sp_CP_GetPushRequestMachineResource] 2097152351~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:57.983+360><thread=5448 (0x1548)>
Execute query exec [sp_CP_GetPushMachineName] 2097152351~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:57.996+360><thread=5448 (0x1548)>
Received request: "2097152351" for machine name: "workstation2" on queue: "Retry".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:58.008+360><thread=5448 (0x1548)>
Stored request "2097152351", machine name "workstation2", in queue "Processing".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:58.021+360><thread=5448 (0x1548)>
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152351, 1~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:21:58.036+360><thread=5448 (0x1548)>
----- Started a new CCR processing thread. Thread ID is 0x335c. There are now 1 processing threads  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.061+360><thread=5448 (0x1548)>
Submitted request successfully  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.074+360><thread=5448 (0x1548)>
Getting a new request from queue "Retry" after 100 millisecond delay.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.087+360><thread=5448 (0x1548)>
Found CCR "2097152396.ccr" in queue "Retry".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.099+360><thread=5448 (0x1548)>
======>Begin Processing request: "2097152351", machine name: "workstation2"  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.074+360><thread=13148 (0x335C)>
Execute query exec [sp_IsMPAvailable] N'STE'~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.129+360><thread=13148 (0x335C)>
---> Trying each entry in the SMS Client Remote Installation account list~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.142+360><thread=13148 (0x335C)>
---> Attempting to connect to administrative share '\\workstation2\admin$' using account 'Domain\sccmclientdeploy'~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.155+360><thread=13148 (0x335C)>
Execute query exec [sp_CP_GetPushRequestMachine] 2097152396~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.211+360><thread=5448 (0x1548)>
Successfully retrieved information for machine workstation1 from DB  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.230+360><thread=5448 (0x1548)>
Execute query exec [sp_CP_GetPushRequestMachineIP] 2097152396~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.243+360><thread=5448 (0x1548)>
Execute query exec [sp_CP_GetPushRequestMachineResource] 2097152396~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.256+360><thread=5448 (0x1548)>
Execute query exec [sp_CP_GetPushMachineName] 2097152396~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.269+360><thread=5448 (0x1548)>
Received request: "2097152396" for machine name: "workstation1" on queue: "Retry".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.283+360><thread=5448 (0x1548)>
Stored request "2097152396", machine name "workstation1", in queue "Processing".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.296+360><thread=5448 (0x1548)>
Execute query exec [sp_CP_SetPushRequestMachineStatus] 2097152396, 1~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.312+360><thread=5448 (0x1548)>
---> Connected to administrative share on machine workstation2 using account 'Domain\sccmclientdeploy'~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.213+360><thread=13148 (0x335C)>
---> Attempting to make IPC connection to share <\\workstation2\IPC$> ~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.351+360><thread=13148 (0x335C)>
---> Searching for SMSClientInstall.* under '\\workstation2\admin$\'~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.368+360><thread=13148 (0x335C)>
---> Unable to connect to WMI on remote machine "workstation2", error = 0x80041002.  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.457+360><thread=13148 (0x335C)>
---> Deleting SMS Client Install Lock File '\\workstation2\admin$\SMSClientInstall.STE'~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.470+360><thread=13148 (0x335C)>
Execute query exec [sp_CP_SetLastErrorCode] 2097152351, -2147217406~  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.491+360><thread=13148 (0x335C)>
Stored request "2097152351", machine name "workstation2", in queue "Retry".  $$<SMS_CLIENT_CONFIG_MANAGER><01-08-2015 19:22:00.505+360><thread=13148 (0x335C)>

Similar Messages

  • Automatic Client Push not working - Site System Servers

    Having an issue getting automatic site-wise client push to work when only
    having "Configuration Manager site system servers" selected.  This was turned on after discovery was enabled and fully executed.
    SCCM 2012 R2 CU1, Single Primary Site Server, 2 Management Points (one on primary and second is standalone), with 5 DP's (currently), SQL is standalone.
    The site systems are within the IP range boundaries and show as assigned (i.e. site code showing in console of object).  The boundaries are in a boundary group with site assignment selected, and a DP added.  When I view the object properties I
    see its returning the correct IP that does fall withing the IP range boundary.
    Nothing in the ccm.log indicating its ever trying to install the client and the ccr and ccrretry folders are empty.  I can do a manual client push without issue to a site server object or a discovered desktop/laptop object.
    Is there something I may be missing here?  And does anyone know the interval in which SCCM should be creating ccr records for discovered objects that don't have a client?

    Thanks or the quick replies everyone.  To answer Idan's questions, no errors in log or component status and SQL is not clustered.
    John, I hope this isn't the case.  If it were wouldn't that effectively mean you would not be able to enabled discovery until you are ready to turn on auto client push?  And if you did that you would have no way to control the client roll out.
     Maybe I am missing something in that equation.  I'll test that theory regardless but if that ends up being the case that is alarming!  :-)
    Jason, thanks for the tip on the potential bug.  Was really more so hoping to validate automatic client push rather than actually needing it for my site system servers.  So if it is the issue you reference above hopefully its just contained to
    the site system servers.  Would be nice to be able to select automatic client push to just a collection of devices prior to turning it on for site wide deployment.  
    I guess I could always just turn off discovery temporarily and delete all but some test clients, enable client push for workstations, then once validated, turn it back off and re-enable discovery.  (wouldn't turn push back on until most clients are
    deployed on the roll out schedule)

  • Automatic client push installation not working

    I created one secondary server and replication with CAS is active. Boundary also configured and enabled automatic client push installation. 
    Daily i am checking some machines, but agents are not getting installing automatically . But manual client installation is working fine without any issue. Anyone can help on this to find outwhy automatic clients push installation is not running on client
    machines

    Which site code is showing, for your secondary or for your primary?
    If secondary, then as Joyce pointed out, you need to check ccm.log on the secondary site server needs to be checked because that's where the client will be pushed from.
    Jason | http://blog.configmgrftw.com | @jasonsandys

  • Client Push Installation Properties

    I'm trying to setup the automatic client push.  On the accounts tab if I enter user and password and hit verify it wants a network share.  Is it a specific location it wants?  Thanks.

    Hi,
    In which we search far and wide to bring you the best of the Microsoft blogs.
    Managing Software Updates in Configuration Manager 2012
    http://blogs.technet.com/b/server-cloud/archive/2012/02/20/managing-software-updates-in-configuration-manager-2012.aspx
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Client Push Installation

    Does the site wide automatic client push just try one time to install the client? If it fails, does it retry?

    Agree with Michael. No, it won't retry automatic if the deploy agent failed until to rerun it from pending management.
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"
    Mai Ali | My blog: Technical | Twitter:
    Mai Ali

  • Enable Automatic site-wide client push installation

    Hi,
    We are configuring sccm 2012 next to sccm 2007. We want to push SCCM 2007 clients automatically to pc's in a certain OU. Can this be done via "Enable Automatic site-wide client push installation".
    So will it deploy to only the discovered devices in this OU we configured to discover or really install site wide (probably not but need to be sure)?
    J.
    Jan Hoedt

    Automatic client push will initiate a push to all devices that are discovered (where client = 0) and that are assigned to the site (-> boundaries).
    Torsten Meringer | http://www.mssccmfaq.de

  • SCCM Client push or manual installation does not complete

    Hi All,
    I have deployed SCCM 2012 R2 in my lab environment. It has been deployed successfully. I have a issue in which the clients are not getting installed both manually and by pushing the agents via the console. 
    My servers are as follows:
    SCCMSVR.labtest.com  - Is the SCCM server and Fail back status point.
    Server.labtest.com - Is the Domain controller, SQL server
    SCCMTEST.labtest.com - A testing machine to push the client and to deploy patches in it.
    Site code is LAB
    I ran the setup using the following command.
    I have shared the ccmsetup in a share so the command is as follows:
    \\sccmsvr\Client\ccmsetup.exe /MP:SCCMSVR /Logon SMSSITECODE=LAB FSP=SCCMSVR
    But when i check the task manager the process of ccmsetup.exe but it does not change to CCMEXEC.exe
    I waited for an hour but still the same issue. (This was done in the DC Server.labtest.com)
    Screen shot of the DC  Machine:
    When i do a client push installation in a testing machine (SCCMTEST.labtest.com)  i still the same issue. I pushed the client still the same issue
    In the task manager the process of ccmsetup.exe but it does not change to CCMEXEC.exe.
    Screen shot of the second machine:
    Also checked the control panel. Dint find the config manager options there on both machines.
    Also turned off firewall on all 3 machines  but still the same issue.
    Analysed the event logs on all the servers. The client machines did not have any relevant events.
    The SCCM server had this event. Not sure if this is causing the issue.
    Event id 2344
    On 9/28/2014 3:26:48 PM, component SMS_DISTRIBUTION_MANAGER on computer SCCMSVR.LABTEST.COM reported:  Failed to create virtual directory on the defined share or volume on distribution point "["Display=\\SCCMSVR.LABTEST.COM\"]MSWNET:["SMS_SITE=LAB"]\\SCCMSVR.LABTEST.COM\".
    Possible cause: Distribution Manager requires that IIS base components be installed on the local Configuration Manager Site Server in order to create the virtual directory.  Distribution Manager also requires that IIS Web Services be installed on the Distribution
    Point Server that needs to support Background Intelligent Transfer Service (BITS).
    Solution: Verify that IIS base components are installed on the local Configuration Manager Site Server, and IIS Web Services are installed on the Distribution Point Server.
    Can any one please help.
    Gautam.75801

    Hi Kashif,
    Thank you for your valuable help. As you mentioned the IIS 6 WMI compatibility Feature was not installed. Once i installed and rebooted the SCCM server and pushed
     both the agents manually and by Pushing it via console and it succeed. How ever i got some errors on both the systems The trace log tool during the installation but it succeed.
    What i would like to know is that is it common to get errors like the below while pushing a agent automatically or manually ?
    1. MSI: Action 1:25:44: CcmRegisterComponentsRollback. In the event of a failed installation, this action rolls back the changes from CcmRegisterComponents.
    (Got this multiple times)
    2. MSI: Warning 25702. Failed to uninstall PrepDrvr.Sys for Software Metering Agent.
    3. Failed to load mdmregistration.dll. Continue deployment.
    4. Failed to load mdmregistration.dll with error 0x8007007e
    5. File 'C:\Windows\ccmsetup\WindowsFirewallConfigurationProvider.msi' does not exist. Discovery failed.
    6. File 'C:\Windows\system32\msrdc.dll' does not exist. Discovery failed.
    7. Enumerated all 1 local DP locations but none of them is good. Fallback to MP.
    8. Failed to check url http://SCCMSVR.LABTEST.COM/SMS_DP_SMSPKG$/LAB00002. Error 0x80004005
    9. Failed to correctly receive a WEBDAV HTTP request.. (StatusCode at WinHttpQueryHeaders: 401)
    10. As per the screen shot.
    Gautam.75801

  • SCCM Client Push Installation Wizard does not install the client. CCMSetup folder - not created

    Hello,
    I have tried running the Client Push wizard for a single computer or a pilot collection of 8 computers, the result is always
    the same - no SCCM client is installed on any computer.
    The computers are running 32-bit Windows XP SP2.
    The Windows firewall is disabled.
    The client push installation account is setup and have domain admin and local admin privileges. Client Push automatic method
    is not enabled.
    The domain is AD WIndows 2000.
    The SCCM server is running Windows 2003 R2 SP2 64bit Standard.
    The AD schema has been extended.
    MP, and SLP are installed and published. (MP is published in DNS as well.)
    FSP is installed.
    MP, SLP and FSP are running on the same server.
    SQL 2005 server is running locally.
    System management container is created and all rights and permissions delegated.
    With the Push installation account I can access C$ share on the client computer from the SCCM server.
    RPC, Remote registry, WMI services are running on the client machines.
    All prerequisites are installed from the client folder on SCCM server- latest BITS 2.5, Windows installer 3.1 and MSXML6.
    All computers are in the same IP subnet which is listed in the boundaries.
    Yet, the client is not being installed.
    No CCMSetup folder is created on the client machines in Windows\System32 folder, so it is really difficult to troubleshoot
    what the is the issue. I do not see anything helpful in the ccm.log on the server.
    I have tried running the CCMSetup.exe manually on one of the workstations and that was successful and reported back to the
    SCCM server / console.
    What else I should check / try? I really want to push agents via the wizard.
    Thank you,
    Peter

    Hi Wally,
    I have changed 2 things:
    1. Enabed automatic push installation (so I am not usign the wizard any more)
    2. Changed the IP subnet to IP ranges in the site boundairies.
    After runnignt the discovery, I was able to see some activities in the ccm.log. A ccmsetup folder is now created but the agent is still not instaleld. Here is the ccmsetup.log
    ==================================
    <![LOG[==========[ ccmsetup started in process 3140 ]==========]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:8853">
    <![LOG[Version: 4.0.5931.0000]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:1913">
    <![LOG[Command line parameters for ccmsetup have been specified.  No registry lookup for command line parameters is required.]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:3937">
    <![LOG[Command line: "C:\WINDOWS\system32\ccmsetup\ccmsetup.exe" /runservice /config:MobileClient.tcf]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:3946">
    <![LOG[CCMHTTPPORT:    80]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7851">
    <![LOG[CCMHTTPSPORT:    443]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7866">
    <![LOG[CCMHTTPSSTATE:    0]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7884">
    <![LOG[CCMHTTPSCERTNAME:    ]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7912">
    <![LOG[FSP:    HFXDBSSOM.CORP.EASTLINK.CA]LOG]!><time="09:45:07.045+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7927">
    <![LOG[CCMFIRSTCERT:    0]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:7969">
    <![LOG[Config file:      C:\WINDOWS\system32\ccmsetup\MobileClient.tcf]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4341">
    <![LOG[Retry time:       10 minute(s)]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4342">
    <![LOG[MSI log file:     ]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4343">
    <![LOG[MSI properties:    INSTALL="ALL" SMSSITECODE="PHX" CCMHTTPPORT="80" CCMHTTPSPORT="443" CCMHTTPSSTATE="0" FSP="HFXDBSSOM.CORP.EASTLINK.CA" CCMFIRSTCERT="0"]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4344">
    <![LOG[Source List:]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4352">
    <![LOG[                  \\HFXDBSSOM.corp.eastlink.ca\SMSClient]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4359">
    <![LOG[                  \\HFXDBSSOM\SMSClient]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4368">
    <![LOG[MPs:]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4371">
    <![LOG[                  HFXDBSSOM.corp.eastlink.ca]LOG]!><time="09:45:07.061+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:4386">
    <![LOG[Updated security on object C:\WINDOWS\system32\ccmsetup\.]LOG]!><time="09:45:07.076+240" date="12-06-2007" component="ccmsetup" context="" type="0" thread="3108" file="ccmsetup.cpp:8692">
    <![LOG[Sending Fallback Status Point message, STATEID='100'.]LOG]!><time="09:45:07.076+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="3108" file="ccmsetup.cpp:9169">
    <![LOG[State message with TopicType 800 and TopicId {A450B407-619B-4777-B77E-C3352753B58A} has been sent to the FSP]LOG]!><time="09:45:07.326+240" date="12-06-2007" component="FSPStateMessage" context="" type="1" thread="3108" file="fsputillib.cpp:730">
    <![LOG[Running as user "SYSTEM"]LOG]!><time="09:45:07.326+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:2534">
    <![LOG[Detected 24292 MB free disk space on system drive.]LOG]!><time="09:45:07.326+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:465">
    <![LOG[DetectWindowsEmbeddedFBWF() Detecting OS Version]LOG]!><time="09:45:07.342+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:511">
    <![LOG[Client OS is not Windows XP Embedded]LOG]!><time="09:45:07.342+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:548">
    <![LOG[Successfully ran BITS check.]LOG]!><time="09:45:08.745+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:6948">
    <![LOG[Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 401)]LOG]!><time="09:45:08.745+240" date="12-06-2007" component="ccmsetup" context="" type="3" thread="2600" file="ccmsetup.cpp:5813">
    <![LOG[Sending Fallback Status Point message, STATEID='308'.]LOG]!><time="09:45:08.760+240" date="12-06-2007" component="ccmsetup" context="" type="1" thread="2600" file="ccmsetup.cpp:9169">
    <![LOG[State message with TopicType 800 and TopicId {3BFABF82-FB74-43FB-8A4A-6DFDEAEAC25C} has been sent to the FSP]LOG]!><time="09:45:08.776+240" date="12-06-2007" component="FSPStateMessage" context="" type="1" thread="2600" file="fsputillib.cpp:730">
    ==============================================================
    There are two red errors I am concerned about:
    "Failed to successfully complete HTTP request. (StatusCode at WinHttpQueryHeaders: 401)
    and
    "Failed to download 'WindwosXP-KB923845-x86-ENU.exe' from http://HFXDBSSOM.corp.eastlink.ca/CCM_Client/i386/BITS25 with error code 0x80004005).
    What should I do to resolve these errors?
    Thanks,
    Peter

  • Best practise for installing patches for SCCM Client 2012 (Both x86 and x64)) - OSD and Client Push Installation

    Hi All,
    What is best practice for automatic installing of SCCM 2012 client Patches
    (using Patch switch) during installation of SCCM 2012 clients? The challenge is that now there are two versions of clients and updates (x86 and x64).
    I need information for:
    OSD
    Client Push Installation
    Thank you in advance.
    Regards,

    Not everything that can be or is supported or not supported is documented (or ever can be):
    http://technet.microsoft.com/en-us/magazine/jj643252.aspx
    Your expectation here needs to be adjusted. No one recommended contacting support. William just mentioned that *if* you have an issue and needed to contact support, they may decline to help you because you've done something explicitly unsupported.
    For clientpatch, here's the specific documentation noting it as unsupported:
    http://blogs.technet.com/b/configmgrteam/archive/2009/04/08/automatically-applying-hotfixes-to-the-configuration-manager-2007-client-during-installation.aspx
    Additionally, I've also been in contact with the sustained engineering folks responsible for the CUs and they've reinforced the statement.
    What can happen? Who knows? Microsoft does not test against unsupported configurations and features -- that's the definition of unsupported. It's not tested so no one really knows. They did find a couple of explicit issues (outlined in that post above) so
    know that at least those exist and probably more since it is, as mentioned, abandoned code.
    Why does it matter what can happen though? If the folks who write and support the code tell you shouldn't do it, you are simply asking for problems by doing it. Ultimately, you're asking a question that has no defined answer (except "bad"/unsupported things)
    that really doesn't matter if you follow the explicit guidance. If you don't, as William points out, that's a risk for you take and an answer for you to discover.
    Jason | http://blog.configmgrftw.com

  • Client Push CU4

    When you use the automatic site wide push or the client push wizard is it pushing the client from the SMS_Sitecode\Client directory? This is also the package source path for the "Configuration Manager Client Package" package. Reason I ask is
    if this is correct than the ccmsetup and other files in this directory would be either RTM, SP1, or R2. We have SP1 so the version it would install would be 5.0.7804.1000. When I right click on ccmsetup and look at the details tab it says the file version
    is 5.0.7804.1500 which is CU4. I did install the CU4 hotfix so maybe it is reading this from the msp? What does happen is when we do the client push it installs the original SP1 version (5.0.7804.1000). Is this what is supposed to happen?

    More info:
    Description of Cumulative Update 4 for System Center 2012 Configuration Manager Service Pack 1
    http://support.microsoft.com/kb/2922875/en-us
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • How to change my client push installation version

    I have one primary site server.  I have updated it to 5.00.7958.1401 and this is the version shown if i check "about system center configuration manager".
    When i push the client to machines by right clicking and choosing "install client"...SCCM installs client version 5.00.7958.1000.
    How can I change it so my client push installs the CU3 version 1401?
    Thanks

    If you were to mess with the files in the client folder of the site server's installation path, you would place your self in an unsupported state, though this is simple...
    how about using the PATCH parameter for ccmsetup.exe? You could configure it in the Client Push Installation / Installation Properties tab...
    http://thecmadmin.com/2013/08/01/installing-cumulative-update-2-cu2-for-cm12-sp1-during-initial-client-install/
    other reference:
    http://blogs.technet.com/b/deploymentguys/archive/2012/10/11/automatically-populate-the-patch-property-for-the-configmgr-client-installation-updated-for-configmgr-2012.aspx

  • Deploying client language pack while client push

    Hi All,
    How do i deploy specific  language pack with client push installation? 
    Note: I already enabled site for that language and i can see language files are exists in "Client\i386\Language Pack\".
    Thanks.

    During the client installation the client will install the languages that are available at that moment. When the languages is available later, the client has to be reinstalled. After the installation the client will automatically switch to the OS language.
    To detect the installed language, see this key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCMSetup\InstalledLangs
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude
    Thanks Peter for information.
    Do i need to use special parameter/switch in client install properties while client push installation to install language pack?
    Thanks again
    Sam

  • Sccm client push installation problem

    in my company 22000 users and install sccm 2012(1 primary site in main dc  and 4 site system server in branch  )
    i enable automatic site-wide client push installation . only sccm client installed in 11000 computers during 7 month and  increment installation it very slowly 2-10 per month 
    how i install  svvm client in another computers automaticly
    please help me

    Yes. You can also manually create boundaries. Each client must fall under a boundary (eg IP Subnet, IP Range, AD site). You need to check that all are covered. Boundaries have to be added to boundary groups which are configured for site assignment.
    http://www.gerryhampsoncm.blogspot.ie/2013/02/sccm-2012-sp1-step-by-step-guide-part-6.html
    Gerry Hampson | Blog:
    www.gerryhampsoncm.blogspot.ie | LinkedIn:
    Gerry Hampson | Twitter:
    @gerryhampson

  • Locked SCCM Client Package waiting for prestaged content, Cant use Client Push

    Hi there,
    I am having an issue with client push. When initiated the client is unable to find the client install package on the DP. The CCMSETUP log file on the client  reads "MP xxxxx.xxx.com didnt return DP locations for client package with the expected
    version". This could be caused by a boundry issue but the boundry information is set up correctly, and published into AD.
    The SCCM Client on the site server is not getting replicated properly to the DP's that we have setup and I think that this is causing the issue. The reason why its not gettiog to the DP is due to this error: "Distribution Manager is waiting for Package SG100001
    content to be prestaged on the distribution point" when we look at the content status of the SCCM client Package.
    We are unable to change the prestaged distribution point settings "automatic" as the package is the locked as its the SCCM client installation package and its waiting for us to prestage it on the DP. I have tried prestaging it, but it didnt
    work
    Any ideas as I have been stuck for two days on this now...
    Thanks in advanced.
    George

    Torsten you were right, The solution was as follows for anyone else having the same issue.
    As soon as you create a DP it appears that the client installation package automatically tries to distribute to the DP. If you created the DP as "Enabled for Prestage" while doing the setup then the SCCM client package will just wait for you to
    copy it manually. To reslove this I had to remove the "Enabled for Prestage Content" from the DP then go into the SCCM client Package, content location tab, select the DP and redistribute the package to the DP.
    Checking the Distribution Manager and PkgXferMgr.log assisted me in monitoring the content transfer to the new location.
    Thanks for your assistance.
    George
    George, I too concur that this fixed the issue.
    I had the same problem with my SCCM 2012 R2 CU4, where i updated the distribution point for the Configuration Manager Client Package. Thanks a million!

  • Installing Internet Clients Using Client Push

    I've read throught the MS documentation on how to install internet based clients (http://technet.microsoft.com/en-us/library/gg712298.aspx#BKMK_Manual) and it indicates
    that they can be installed using client push. So, if I just add the CCMHOSTNAME property in the client push settings I can then use automatic site wide installation? This is assuming the clients already have a certificate installed. I'm confused because it
    shows in this article that you must include other properties and even ccmsetup properties such as /usepkicert. You can only use the client msi properties in the client push settings. Would this work with just CCMHOSTNAME? Also, would I have to add SMSSITECODE
    since clients won't automatically be assigned a site based on there boundaries?

    You can even leave that property out, as long as you're clients are on the intranet during the client installation. During the first policy retrieval the client will get the information about the Internet-facing site system.
    My Blog: http://www.petervanderwoude.nl/
    Follow me on twitter: pvanderwoude

Maybe you are looking for

  • HT201317 photo stream is not showing on icloud

    phot stream is not showing on icloud.com on my pc

  • Inspire 5500 - Speakers Cut Out?

    Hello... I'm using the excellent Inspire 5500 speakers, but occasionally one of the speakers, usually front center, just cuts out. If you pull the power and plug it back in (a simple off/on doesn't work) it'll come back. But sometimes when I turn the

  • Does SChannel library support DTLS(Datagram Transport Layer Security) protocol?

    Please let me know whether SChannel library supports DTLS(Datagram Transport Layer Security) protocol.

  • Backup phone with an iPhone plan

    Does anyone know or have a definitive answer on the following? I have an 8gb iPhone (which I love) and have a unbranded Moto KRZR as a backup phone/phone to use when I don't want to take my iPhone (golf,beach etc). Anyway, I know the iPhone SIM is sw

  • How could i store this

    I am doing a university assignment for a fictional car company. Anyway, the scenario says there are 3 categories of viechles, with a number of cars in each. small car: 3 renault clio's family saloon: 3 vauxhall vectras light van: 2 Renault traffic's.