locked
Turn Off Site Wide Client Push RRS feed

  • Question

  • If I had enabled the client push site wide, and then disabled it, will computers that were discovered already and are in the console but didn't yet get the client installed (but were sent a request and were offline most likely) still install it once online? B/C I know it tries every 4 hours for a week.  Please help.
    Tuesday, September 25, 2012 4:47 PM

All replies

  • No they won't once it's disabled.

    Justin | http://patchmypc.net | Please remember to mark as helpful/answer if this helped you

    Tuesday, September 25, 2012 4:54 PM
  • Matt,

    You can look in the Microsoft Configuration Manager\inboxes\ccrretry.box folder and see if there are any pending client retries there. If there are, then I believe even with the client push disabled it will retry.

    Another folder to check would be the Microsoft Configuration Manager\inboxes\ccr.box folder. see if any client request files are in this folder as well.

    I believe with the client push disabled and if these folders contain client requests, you will see warnings appear in your site status.


    Kind Regards, Tom Ziegler http://www.sccmguy.com | Twitter @Tom_Ziegler


    • Edited by Tom Ziegler Tuesday, September 25, 2012 5:23 PM
    Tuesday, September 25, 2012 4:56 PM
  • Client push, whether initiated automatically or manually, generates a CCR for each assigned resource that does not have the client installed. The client configuration manager (CCM) attempts to install the client on systems based on these CCRs regardless of the auto-client install status. If it (the CCM) successfully initiates a client push on the system (by copying ccmsetup to it and start ccmsetup as a service), then the CCR is removed by the CCM. If it fails to do this, the CCR is left in tact. The CCM will retry client installation based on a CCRs existence every hour for 7 days and then finally give up and delete the CCR.

    Auto client push simply auto-generates the CCRs (and manual client push manually generates the CCR). Disabling auto client push does not delete any CCRs in the queue thus disabling it will not stop attempts at pushing the client to resources already identified.

    You can examine the existing CCRs (and delete them) in the folder indicated by Tom.


    Jason | http://blog.configmgrftw.com

    Tuesday, September 25, 2012 5:52 PM
  • What if I turn it off, and then do a manual push using the wizard to a collection? Will it still try to reinstall using the site wide push that I disable b/c there is a pending CCR from it?
    Tuesday, September 25, 2012 8:32 PM
  • No. CCM will never initiate a reinstall (unless you initiated the install manually from the console and told it to do a reinstall). CCM checks for an existing client installation and stops processing if it finds the client already installed. I *think* it will also remove the CCR if it does find the client already installed.


    Jason | http://blog.configmgrftw.com

    Tuesday, September 25, 2012 8:46 PM
  • ok great, so you are saying that if I disable site wide push, if there was a CCR generated for an already discovered resource, that happens to be offline, it will go ahead and try to install the client once it comes online?

    to prevent this, should I just remove that resource from SCCM for now?

    Tuesday, September 25, 2012 9:31 PM
  • Yes if a ccr exist for a client that is currently offline it will attempt to install the client when it comes online (if within the 7 day period).

    To prevent the client from installing, Removing the ccr files will prevent Configuration Manager from attempting to install the client yes.


    Kind Regards, Tom Ziegler http://www.sccmguy.com | Twitter @Tom_Ziegler


    • Edited by Tom Ziegler Tuesday, September 25, 2012 10:21 PM added content
    Tuesday, September 25, 2012 10:12 PM