none
Client Push in SCCM 2012

    Question

  • Hi Giants,

    i have query.

    i am planning to introduce SCCM 2012 in our environment and we decided to go with 1 Primary and 65 DP in different sites.

    i am planning to use Client Push to deploy the clients in Phase wise that is 3 sites at a time.

    my question here is,

    1. If i initiate a Client Push from Primary, will the Clients Download the SCCM Client package from Primary server MP or Local Distribution Point.

    2. I know we have few CCMSetup Switch to mention the Client Source, but how i can use it in Client Push.

    3. we have SMS 2003 currently running, is it wise to deploy SCCM 2012 client from SMS 2003. because i believe SCCM 2012 Client will remove SMS 2003 Client and install SCCM 2012 Client. in this scenario will it still download from SCCM 2012 Primary Site MP or it uses SMS 2003 Package Source.

    .

    Thanks in Advance

    SithaYuvaraj.

    Tuesday, July 10, 2012 5:57 PM

Answers

All replies

  • Hi,

    1. SCCM 2012 will use the Dp assigned to the boundary that the client resides in.

    2. With Client Push working as it does in SCCM 2012 this should not be needed. However I would recommend that you have a look at and think about using a startup script as a compliment to use client push to get the client out there, like for instance this great script from Jason Sandys: http://blogs.catapultsystems.com/jsandys/archive/2010/12/30/updated-configmgr-startup-script.aspx

    3. Actually NO, the SCCM 2012 client installation does not uninstall/upgrade the SMS 2003 client you will have to handle that manually using scripts, a startup script perhaps ;-) It is documentet in the FAQ for ConfigMgr 2012 migration here: http://technet.microsoft.com/library/gg682088.aspx#FAQ_Migration

    regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Tuesday, July 10, 2012 7:11 PM
  • Hi,

    1. SCCM 2012 will use the Dp assigned to the boundary that the client resides in.

    2. With Client Push working as it does in SCCM 2012 this should not be needed. However I would recommend that you have a look at and think about using a startup script as a compliment to use client push to get the client out there, like for instance this great script from Jason Sandys: http://blogs.catapultsystems.com/jsandys/archive/2010/12/30/updated-configmgr-startup-script.aspx

    3. Actually NO, the SCCM 2012 client installation does not uninstall/upgrade the SMS 2003 client you will have to handle that manually using scripts, a startup script perhaps ;-) It is documentet in the FAQ for ConfigMgr 2012 migration here: http://technet.microsoft.com/library/gg682088.aspx#FAQ_Migration

    regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Hi Jorgen,

    1. If SCCM takes the Client Package from Local DP, do i need to create a Client Package and distribute to All DP's or i need to create a SMSClient Share.

    Thanks,

    SithaYuvaraj.

    Wednesday, July 11, 2012 9:46 AM
  • Hi,

    Normally, you're client Package is already created during the SCCM 2012 installation and of course replicate this package on all of your remote DP.

    Regarding you're SMS 2003 client, you could create a package on SMS 2003 Server which going to uninstall the SMS 2003 client (of course discovery should not run from your SMS 2003 server).


    Thursday, July 12, 2012 9:36 AM