locked
Automatic Site Wide Client Push Not Working RRS feed

  • Question

  • I can install the client fine and successfully if I right click in the console and "Install Client". However, using the "Enable automatic site-wide client push installation" doesn't work. Nothing is written in the CCM.log on the server. I have boundaries setup in boundary groups. What could be the problem?
    Monday, September 24, 2012 12:47 PM

All replies

  • In the boundary group you have setup for the site do you have site assignment configured.
    Monday, September 24, 2012 12:55 PM
  • I do have that setup yes

    This is a migration from 2007 to the new version, any issues there?

    Monday, September 24, 2012 12:57 PM
  • Nothing in the ccm.log typically indicates that the resources are not assigned to the site.

    Jason | http://blog.configmgrftw.com

    Monday, September 24, 2012 1:43 PM
  • Is there further troubleshooting I can do? Why does it work when I initiate client install using right click on a resource or collection? Does it have anything to do with the 2007 client already being installed and the site wide push can't uninstall it as it can if you use the wizard?
    Monday, September 24, 2012 1:48 PM
  • Do you see a site code for your discovered objects?

    On your boundary group(s) property -> reference tab - select use this boundary for site assignement.

    Monday, September 24, 2012 2:02 PM
  • I do see my site code there in my boundary groups
    Monday, September 24, 2012 2:03 PM
  • No, that wouldn't prevent activity in ccm.log.

    During the manually client push wizard, you can check a box that says push to a system regardless of site assignment.

    Is this a single primary site or are there other sites?

    Do the resources without the client installed show an assigned site code in the console?


    Jason | http://blog.configmgrftw.com

    Monday, September 24, 2012 2:11 PM
  • This is a single primary site, migrated from 2007.  No, the resources without the client do not have an assigned site code, only the ones that I've already used client push wizard to successfully install the client.
    Monday, September 24, 2012 2:17 PM
  • Then it looks like they are not falling within your site assignment boundary group(s).

    Jason | http://blog.configmgrftw.com

    Monday, September 24, 2012 2:22 PM
  • oh they are within the boundary groups, I have one boundary group with alot of IP address range boundaries that were created with Active Directory Forest Discovery. The workstations are within these IP address ranges. Could it be a bug, here another user is having the same issue...

    http://www.myitforum.com/forums/Enable-automatic-sitewide-client-push-instalation-is-not-working-for-me-in-SCCM-2012-RTM-m234637.aspx

    Monday, September 24, 2012 2:31 PM
  • Have you rerun system discovery? Resources without a client are assigned to sites by system discovery.

    Jason | http://blog.configmgrftw.com

    Monday, September 24, 2012 2:45 PM
  • ok reran Active Directory System Discovery, site code column still blank for the resources that don't have the client installed...
    Monday, September 24, 2012 3:02 PM
  • I think auto client push will only happen on the initial discovery.


    John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

    • Proposed as answer by ArtSaw Saturday, July 13, 2019 8:12 AM
    Tuesday, September 25, 2012 12:53 AM
  • Then, unless it's a bug (which is possible -- I haven't heard or seen anything related but only CSS can truly confirm that) the systems not assigned are not within your boundaries in the site assignment boundary group. You can individually open the properties dialog for each resource to check the IP address discovered for each and compare it to your boundaries in you site assignment boundary group(s).

    Jason | http://blog.configmgrftw.com

    Tuesday, September 25, 2012 12:58 AM
  • None of the resources have an IP address after being discovered, could that be the issue? Why wouldn't the discovery get the IP address?
    Tuesday, September 25, 2012 12:40 PM
  • Yes, that sounds like it could be the source of the issue.

    First thing I would do is delete all of the resources without a client installed and re-run a full AD System Discovery. One of the steps in AD System Discovery is to verify DNS name resolution of all systems discovered before a DDR is created. It's possible that this changed in 2012 with the new constraints that were adding on password age and last login time. The documentation (at http://technet.microsoft.com/en-us/library/gg712308.aspx#BKMK_ADSystemDisc ) still seems to indicate that this is the case though.

    If that still creates resources without IPs either the behavior has changed or there is a bug with discovery.


    Jason | http://blog.configmgrftw.com

    Tuesday, September 25, 2012 1:34 PM