locked
Client push not working after client discovery RRS feed

  • Question

  • I'm using AD System Discovery to discovery client machines and assign them to a site.  I have configured the client push to be automatic to workstations.  The problem is, the machine gets discovered and assigned to a site however no client push happens.  Deploying client to a Windows 7 Pro x64 SP1 VM.

    If I right click the client machine and install client, it works just fine.  I do have boundaries, and boundary groups setup for IP subnet.  There is only a single SCCM site in my test environment, 3 boundaries, and 2 boundary groups.  I have a distribution point configured for the boundary I'm trying to install the client push to.

    I attempted to view the ccm.log, and there were no reports of the computer name in the log except when I right click - install client.  Any ideas?

    Tuesday, February 12, 2013 4:32 PM

Answers

All replies

  • Hi,

    First, I advice you don't use IP subnet for boundaries to avoid some issues (you read the Jason's blog http://blog.configmgrftw.com/?p=343). Change your boundaries to IP ranges then look what happen.


    Bechir Gharbi | My blog: @myITforum.com | Twitter: @Bechir_Gharbi | Linkedin: Bechir Gharbi | Time zone: GMT + 1

    • Marked as answer by aacajo Wednesday, February 13, 2013 2:26 PM
    Tuesday, February 12, 2013 5:40 PM
  • After Discovery, are your clients assigned to your site; i.e., do they should your site code in the site code column?

    Jason | http://blog.configmgrftw.com

    Tuesday, February 12, 2013 8:03 PM
  • Yes IP subnet really IS evil...  Changing to ranges fixed the problem.  Appreciate the help.

    Jason:  They did not have a site code in the "Site Code" column, but if I looked at the properties of the machine it had the property "Agent Site" set correctly in discovery data.

    Wednesday, February 13, 2013 2:28 PM