locked
When you perform a client push on a collection of systems and a new system is added to the AD OU where that collection is targeting, shouldn't the newly added system begin receiving the SCCM client? RRS feed

  • Question

  • Here is my process:

    1. Right click collection and select Install Client
    2. In the Install Configuration Manager Client Wizard I select the "Always install the client software" (though I am not certain what this does exactly).
    3. Then I just monitor the client installs

    The problem that I have seen is that sometimes when a new system gets added to the AD OU that I am targeting with a collection query, it does not install the SCCM client. 

    Do I have to keep manually running the Install Configuration Manager Client Wizard each time a new system is added to that AD OU?

    I thought the "Always install the client software" checkbox ensures that the SCCM client will just keep installing on any new system that it finds in the collection, or is this not the case?

    Thanks

    Wednesday, August 5, 2015 10:56 PM

Answers

  • They're the same thing.

    Have you considered using a startup script or one set to run as a scheduled task?


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Thursday, August 6, 2015 2:48 AM
  • No I have not. 

    How would a start up script be more beneficial than the other methods?

    Thanks


    Check Jason's script here http://blog.configmgrftw.com/configmgr-client-startup-script/ it's all explained there.
    Thursday, August 6, 2015 3:11 AM
  • No need to add an account to the local admins when using a startup script. Why using another method? A startup script (targeted to "all" computers) will be executed as soon as a domain joined computer is started. So no need for alternatives imho.

    Torsten Meringer | http://www.mssccmfaq.de

    Thursday, August 6, 2015 5:22 AM

All replies

  • "always install" is to force the given client you ran it on to install.  If you add a new machine to the collection it shouldn't try to install because when you right force the client install to the collection,
    SCCM should read the collection and tell each of them to install the client.  Any new machine won't see the task you just started because it was a manual process.


    http://www.sccm-tools.com http://sms-hints-tricks.blogspot.com

    Wednesday, August 5, 2015 11:13 PM
  • You can turn on Automatic Client Push that will install the client on newly discovered systems.  Just a thought. . .

    Jeff

    Wednesday, August 5, 2015 11:49 PM
  • I see!

    So this is why it is best to use site-wide client push then?

    What about software update based client installation? How does that work exactly?

    For instance, I know that the GPO needs to be configured to point the systems to the SUP (which I have done), but how and when will the systems receive the SCCM client via windows update?

    Thanks


    Wednesday, August 5, 2015 11:53 PM
  • Jeff, what is the difference between Automatic Client Push and Site-Wide Client Push, or is it the same thing and this is just semantics?

    Thanks

    Thursday, August 6, 2015 12:07 AM
  • They're the same thing.

    Have you considered using a startup script or one set to run as a scheduled task?


    Jason | http://blog.configmgrftw.com | @jasonsandys

    Thursday, August 6, 2015 2:48 AM
  • No I have not. 

    How would a start up script be more beneficial than the other methods?

    Also, if I don't have a client push account setup in AD will it use the SCCM Site Server's computer account if it is added to the local admin group on client systems to install the SCCM client?

    Some of the security folks do not like the idea of using separate accounts and adding them to the local admin group, but they seem to be okay with using the SCCM Site Server's computer account. 

    Thanks



    Thursday, August 6, 2015 3:09 AM
  • No I have not. 

    How would a start up script be more beneficial than the other methods?

    Thanks


    Check Jason's script here http://blog.configmgrftw.com/configmgr-client-startup-script/ it's all explained there.
    Thursday, August 6, 2015 3:11 AM
  • Can someone answer this for me, please?

    Also, if I don't have a client push account setup in AD will it use the SCCM Site Server's computer account if it is added to the local admin group on client systems to install the SCCM client?

    Some of the security folks do not like the idea of using separate accounts and adding them to the local admin group, but they seem to be okay with using the SCCM Site Server's computer account. 




    Thanks
    Thursday, August 6, 2015 4:04 AM
  • Jason, if I use your login script I don't need to add any account to the local admin group on client systems?

    Also, could other methods of client installation still be used along with your script like enabling site-wide client push just to ensure 100% client installs?

    Thanks



    Thursday, August 6, 2015 4:28 AM
  • No need to add an account to the local admins when using a startup script. Why using another method? A startup script (targeted to "all" computers) will be executed as soon as a domain joined computer is started. So no need for alternatives imho.

    Torsten Meringer | http://www.mssccmfaq.de

    Thursday, August 6, 2015 5:22 AM
  • AWESOME!!

    Thanks everyone

    Thursday, August 6, 2015 2:37 PM