locked
Client Push not working RRS feed

  • Question

  • Hi,

    I'm having issues with Client Push on a newly build SCCM 2012 server. The Client push is not working but when I click on a device in the SCCM console and select install, the client deploys successfully. Does the manual installation use the same account as the client push method?

    There is no activity in the server ccm.log (other than for the manual install). I can browse to the devices admin$ share with the client push account. The account is a member of Domain admins which is in the devices local admin group. I can ping the device by name and IP. There is no ccmsetup folder or log on the client machine. I assume there aren't any firewall issues as the manual install works.

    Any help would be great,

    Thanks,

    Andrew

    Wednesday, November 21, 2012 11:23 AM

Answers

  • Seems that I had missed a step in the process.

    I had to: Right-click on My Boundary Group, click on the References tab and tick ‘Use this boundary group for site assignment'

    Thanks for the assistance

    Thursday, November 22, 2012 3:09 PM

All replies

  • Is there anything in the ccm.log file on the server?
    Wednesday, November 21, 2012 11:46 AM
  • nothing in the ccm.log on the server. Just the standard:

    Waking up for site control file directory change notification SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:24 4372 (0x1114)
    The Site Control File has changed, parameters will be reread. SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    Updating Site Parameters SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    MP Ports: 80 SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    IISPreferedPort: 80 SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    MP SSL Ports: 443 SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    IISSSLPreferedPort: 443 SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    Default MP: CRWSCCM01.crew.local SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    Default MP Type: 1 SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    Default MP: [None] SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    Certificate Selection Criteria: SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    Certificate Store: SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    SSL State: 224 SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    Select First Certificate: 1 SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    Certificate Issuers: SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    Checking configuration information for server: CRWSCCM01.CREW.LOCAL. SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    No Fallback Status Point installed on the Site SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    Install on DC: False SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    Retrieving properties from the site control file. SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    Advanced Client Command Line: SMSSITECODE=HO1 SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
      Ignoring unrecognized property "Advanced Client Command Line Default" SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    Security Mode Option - CCR buffering disabled. SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    Default Client Type: -1 SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)
    Sleeping for 1200 seconds... SMS_CLIENT_CONFIG_MANAGER 20/11/2012 15:35:25 4372 (0x1114)

    Wednesday, November 21, 2012 12:30 PM
  • Have you enabled the "Enable automatic site-wide client push installation? Did you create the Boundary Group(s)? Did you setup AD System Discovery?

    Wednesday, November 21, 2012 12:52 PM
  • Yep, that's enabled, the account is in there and I have installation properties of SMSSITECODE=HO1
    Wednesday, November 21, 2012 2:40 PM
  • Are the clients assigned to the site; i.e., in the all device view, does it have a site code listed? If not, that's the issue; ConfigMgr will not auto-push to systems not assigned to the site.

    Jason | http://blog.configmgrftw.com

    Wednesday, November 21, 2012 3:57 PM
  • The devices say:

    Client: NO

    Site code: 'this is blank'

    Activity: 'this is blank'

    I thought that they only got assigned a site code when the client installed? How can I fix this?

    Wednesday, November 21, 2012 5:09 PM
  • Site assignment is all about boundaries and boundary groups. If a client is not assigned to the local site, pushing an agent to it could be very bad.

    Jason | http://blog.configmgrftw.com

    Wednesday, November 21, 2012 8:07 PM
  • Two boundaries were automatically created when doing discovery, the Default-First-Site-Name and '192.168.1.1-192.168.1.254'. This range is the range that the servers are on. The clients use 192.168.0.x so I had to manually create a boundary for them, the 192.168.0.1-192.168.1.254 range. I then assigned all of these to a single Boundary Group.

    Once the client is manually deployed it has a site code.
    Thursday, November 22, 2012 9:41 AM
  • Seems that I had missed a step in the process.

    I had to: Right-click on My Boundary Group, click on the References tab and tick ‘Use this boundary group for site assignment'

    Thanks for the assistance

    Thursday, November 22, 2012 3:09 PM
  • I'm having the same issue when I add new machines to the domain (server 2012 and windows 8 machines), they get discovered but client push isn't installing the client.  I had the References tab setup correctly already and everything else is correct as mentioned earlier.  Any ideas what else I can troubleshoot?

    Saturday, July 13, 2013 12:33 PM
  • What issue are you having? Simply saying I'm having the same issue doesn't help us help you. Client installation has many aspects and nuances so it is doubtful that you're having the exact same issue but there's no way for us to know without more detail. Also, this should be a new thread.

    Have you performed any troubleshooting or reviewed any logs?

    What have you configured?

    Have you reviewed http://support.microsoft.com/kb/925282 ?


    Jason | http://blog.configmgrftw.com

    Saturday, July 13, 2013 2:47 PM