locked
Cumulative Update 3 and Agent Upgrade RRS feed

  • Question

  • After applying CU3 to SCCM 2012 SP1 there is an agent update that needs deployed to all current client machines.  Does the deployment of this update force a full install of the 170MB agent or does it just apply a small update?

    Also I have a logon script that currently installs the agent on new client PCs. It copies the ccmsetup.exe locally to each PC and runs it with my site code as an argument. If I want new PCs to get the new version of the agent which includes the update from CU3 do I simply just copy over a new ccmsetup.exe that CU3 creates or will the deployment I created for the current PCs be applied the new PCs once they become members of a relevant collection?


    Hibs Ya Bass!

    Tuesday, January 7, 2014 4:19 AM

Answers

  • Hi, You deploy it using the package/program created during installation of the CU3 Upgrade. so there is no need to re-deploy the whole client, there is now updated ccmsetup.exe either so you must deploy the update. You can also deploy the update using SUP and SCUP.

    If you install the client using the logon script you can use the PATCH= command line and add the patch direclty during installation as well.

    Regards,
    Jörgen


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

    Tuesday, January 7, 2014 7:05 AM

All replies

  • Hi, You deploy it using the package/program created during installation of the CU3 Upgrade. so there is no need to re-deploy the whole client, there is now updated ccmsetup.exe either so you must deploy the update. You can also deploy the update using SUP and SCUP.

    If you install the client using the logon script you can use the PATCH= command line and add the patch direclty during installation as well.

    Regards,
    Jörgen


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

    Tuesday, January 7, 2014 7:05 AM
  • Hi, You deploy it using the package/program created during installation of the CU3 Upgrade. so there is no need to re-deploy the whole client, there is now updated ccmsetup.exe either so you must deploy the update. You can also deploy the update using SUP and SCUP.

    If you install the client using the logon script you can use the PATCH= command line and add the patch direclty during installation as well.

    Regards,
    Jörgen


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

    Thanks for that.

    Going forward and there is a further update to the agent, in say CU4, are the patches for the agent cumulative i.e. when using the PATCH= switch I only ever point to a single patch as opposed to multiple patches?


    Hibs Ya Bass!

    Tuesday, January 7, 2014 7:20 AM
  • Cumulative updates are cumulative. So each CU contains all former CUs.

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

    Tuesday, January 7, 2014 8:24 AM
  • Also note that the PATCH property must reference a fully qualified path and file name. And as more less stated by Jörgen, CUs do not update ccmsetup. Some do update scepinstall though and so using auto client is still a good thing for CUs so that SCEP gets updated.

    Jason | http://blog.configmgrftw.com

    Tuesday, January 7, 2014 12:52 PM
  • Also note that the PATCH property must reference a fully qualified path and file name. And as more less stated by Jörgen, CUs do not update ccmsetup. Some do update scepinstall though and so using auto client is still a good thing for CUs so that SCEP gets updated.

    Jason | http://blog.configmgrftw.com

    Jason,

    I'm glad you mentioned SCEP because that was going to be my next question. CU3 includes an update to SCEPinstall.exe so how do I deploy that? You mention "auto client" - what is that?

    Also, it's nearly 30 MB so does that mean all my client machines will be pulling 30 MB down over the network?

    Cheers

    Craig


    Hibs Ya Bass!

    Wednesday, January 8, 2014 2:27 AM
  • Ha, that is an incomplete phrase. I meant auto client upgrade. Peter documented that at http://configmgrblog.com/2012/12/03/how-to-update-configmgr-clients-automatically-in-sp1/ . This will not update the actual ConfigMgr client to CU3 but it will upgrade SCEP to the latest version. I think the latest SCEP version can also be deployed using software updates though.

    Jason | http://blog.configmgrftw.com

    Wednesday, January 8, 2014 4:40 AM
  • Ha, that is an incomplete phrase. I meant auto client upgrade. Peter documented that at http://configmgrblog.com/2012/12/03/how-to-update-configmgr-clients-automatically-in-sp1/ . This will not update the actual ConfigMgr client to CU3 but it will upgrade SCEP to the latest version. I think the latest SCEP version can also be deployed using software updates though.

    Jason | http://blog.configmgrftw.com

    When you say SCEP can be deployed using software updates do you mean deploying it the same way as the agent update by creating a one off deployment to target a collection containing all client machines?

    Hibs Ya Bass!

    Wednesday, January 8, 2014 5:04 AM
  • Sorry, another slight mis-statement. The update to SCEP (http://support.microsoft.com/kb/2907566) to bring it to the latest version is available via the WSUS catalog and thus can be deployed using Software Updates to systems where SCEP is already installed. As long as you have the proper product and category selected (Forefront Endpoint Protection 2010 and updates), you should be able to search for this in your software updates list and thus deploy it. 

    Jason | http://blog.configmgrftw.com

    Wednesday, January 8, 2014 3:59 PM
  • Sorry, another slight mis-statement. The update to SCEP (http://support.microsoft.com/kb/2907566) to bring it to the latest version is available via the WSUS catalog and thus can be deployed using Software Updates to systems where SCEP is already installed. As long as you have the proper product and category selected (Forefront Endpoint Protection 2010 and updates), you should be able to search for this in your software updates list and thus deploy it. 

    Jason | http://blog.configmgrftw.com

    Hmm, now I am a bit confused. I picked up that update in December's patch Tuesday deployment and as you can see below it is compliant on nearly all my client machines. However the KB article says:

    To apply this update, you must have one of the following installed:
    • System Center 2012 R2 Configuration Manager
    • Cumulative Update 3 for System Center 2012 Configuration Manager Service Pack 1
    • Service Pack 2 for System Center Configuration Manager 2007 and Update Rollup 1 for Forefront Endpoint Protection 2010

    I don't have CU3 applied yet but the update has been applied to at least 327 machines. How can this be?

    Also, the machines that I DO want to get the update, namely Server 2012 R2 machines, aren't picking up the update at all.


    Hibs Ya Bass!

    Wednesday, January 8, 2014 8:34 PM
  • First, remember we're truly dealing with two different things here: the SCEP agent and the ConfigMgr client agent.

    The actual hotfix may require CU3 to be installed on the server, but the update to the SCEP agent itself does not. Thus, it can get pushed out using Software Updates and is applicable to any installation of SCEP regardless of ConfigMgr client agent version. (Yes, this is a little confusing, but just keep in mind my first point above.)

    As for your servers, maybe they aren't targeted with the software update group or maybe they haven't hit the deployment deadline?


    Jason | http://blog.configmgrftw.com

    Wednesday, January 8, 2014 8:40 PM
  • First, remember we're truly dealing with two different things here: the SCEP agent and the ConfigMgr client agent.

    The actual hotfix may require CU3 to be installed on the server, but the update to the SCEP agent itself does not. Thus, it can get pushed out using Software Updates and is applicable to any installation of SCEP regardless of ConfigMgr client agent version. (Yes, this is a little confusing, but just keep in mind my first point above.)

    As for your servers, maybe they aren't targeted with the software update group or maybe they haven't hit the deployment deadline?


    Jason | http://blog.configmgrftw.com

    The servers are definitely targeted. When I look at the details of one of the servers in Monitoring/Deployments the only updates for December that are applied to the server are below.

    Maybe the CU3 agent update needs to be applied to Server 2012 R2 machines first before the SCEP update becomes applicable to them?

     

    Hibs Ya Bass!

    Thursday, January 9, 2014 12:55 AM