locked
Client Push Not being attempted RRS feed

  • Question

  • After installing and setting boundaries, discovery and pushing the client I had a about 380 machines that were not clients (out of 3000). Push is still enabled and as we've added machines it appears that the push install isn't making an attempt to insatll. I look through the CCM logs and there's nothing. No attempt to contact the PC, no invalid path....nothing. I try to run the install client from the action menu, same thing. I verified that push is enabled, rights are not an issue, the machines are alive, no firewall and are being discovered. Anywhere else I can look to try and figure out what's going on? This worked for a while and then stopped.

    Wednesday, August 31, 2011 5:05 PM

Answers

  • Is there also no activity in ccm.log when initiating a manual push and having the option "include only client in this site's boundaries" unchecked?


    Torsten Meringer | http://www.mssccmfaq.de
    • Marked as answer by Sabrina Shen Tuesday, September 6, 2011 9:09 AM
    Wednesday, August 31, 2011 6:50 PM
  • Once the agent is installed, clients will reflect the site code of the primary site because they can't be assigned to a secondary. Without the agent installed, they will show as assigned to the secondary site.

    Yes, you should enable client push at the secondary to auto-push to systems assigned to the secondaries.

    Gory details: http://myitforum.com/cs2/blogs/jgilbert/archive/2007/02/22/sms-2003-client-push-installation-method-explained.aspx.


    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
    • Marked as answer by Sabrina Shen Tuesday, September 6, 2011 9:09 AM
    Wednesday, August 31, 2011 8:04 PM

All replies

  • I think, you should take 1 or 2 clients and try to understand the issue. Look at ccmsetup.log for details...

    Also, you can try to reinitiate the client push for one or two systems. At the same monitor the ccm.log

    Below are the excellent guids to start with your teobleshooting

    http://blogs.technet.com/b/sudheesn/archive/2010/05/31/troubleshooting-sccm-part-i-client-push-installation.aspx

    http://support.microsoft.com/kb/925282


    Anoop C Nair - Twitter @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    SCCM Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    Wednesday, August 31, 2011 5:13 PM
  • Yes, that's what I am doing. The CCMsetup never gets created becasue as far as I can tell its not even trying to start the install. I think something is wrong on the site server side.
    Wednesday, August 31, 2011 5:16 PM
  • Ok, The client push was working and it's stopped working now. Did you check for any changes in the configuration or any issue in configuration? Any thing in event logs?

    I would suggest you to remove the client push and add this back. Any difference in the configuration, connectivity or infrastructure of these clients(380).


    Anoop C Nair - Twitter @anoopmannur

    MY BLOG:  http://anoopmannur.wordpress.com

    SCCM Professionals

    This posting is provided AS-IS with no warranties/guarantees and confers no rights.

    Wednesday, August 31, 2011 5:28 PM
  • Is there also no activity in ccm.log when initiating a manual push and having the option "include only client in this site's boundaries" unchecked?


    Torsten Meringer | http://www.mssccmfaq.de
    • Marked as answer by Sabrina Shen Tuesday, September 6, 2011 9:09 AM
    Wednesday, August 31, 2011 6:50 PM
  • AhHA, unchecking initated the manual push. 1 mystery solved. Now, why isn't the automatic push working.
    Wednesday, August 31, 2011 6:55 PM
  • Same reason. Auto client push will only push to systems assigned to the site doing the push.

    No assignment = No push.

    So you need to verify your boundaries. What kind are you using (note that anything except IP Address Range boundaries have potential incorrect behaviors)?


    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
    Wednesday, August 31, 2011 6:59 PM
  • I using 1 primary and a couple of secondary sites. For Boundries I'm using AD Sites. I have verified all my subnets are in Sites and Services. Should the push be enabled on the secondary sites as well? the 2300 installed correctly without that. I can see that SCCM is assigning the missing PC's to one of my sites during discovery. After install they all switch to the primary site.

    Wednesday, August 31, 2011 7:06 PM
  • Once the agent is installed, clients will reflect the site code of the primary site because they can't be assigned to a secondary. Without the agent installed, they will show as assigned to the secondary site.

    Yes, you should enable client push at the secondary to auto-push to systems assigned to the secondaries.

    Gory details: http://myitforum.com/cs2/blogs/jgilbert/archive/2007/02/22/sms-2003-client-push-installation-method-explained.aspx.


    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
    • Marked as answer by Sabrina Shen Tuesday, September 6, 2011 9:09 AM
    Wednesday, August 31, 2011 8:04 PM