locked
How do you install 2012 R2 client updates? RRS feed

  • Question

  • Have just upgraded our site server to 2012 R2 with no problems but am mystified about how to deploy the updated configuration manager client package

    There is a package called 'configuration manager Client package' with zero programs in it.  Is this meant to populate in an update cycle?

    Or am I meant to create a new package with files copied from C:\Program Files\Microsoft Configuration Manager\Client.

    If so what command line arguments do I need to use, if any

    The consensus seems to be not to use automatic upgrade: 'Automatic client upgrades are useful when you want to upgrade a small number of client computers that might have been missed by your main client installation method.'

    Thanks

    David


    • Edited by David b111 Friday, October 25, 2013 2:57 PM
    Friday, October 25, 2013 2:57 PM

Answers

  • The note right below that statement in the doc more or less does:

    "For System Center 2012 Configuration Manager SP1 and System Center 2012 R2 Configuration Manager only:      

    The performance improvements in Configuration Manager SP1 let you use automatic client upgrades as the main method to upgrade clients. However, the performance of this method might be affected by the infrastructure of your hierarchy, such as the number of clients that you have"


    Jason | http://blog.configmgrftw.com

    • Marked as answer by David b111 Monday, October 28, 2013 9:23 AM
    Friday, October 25, 2013 9:04 PM

All replies

  • The consensus seems to be not to use automatic upgrade: 'Automatic client upgrades are useful when you want to upgrade a small number of client computers that might have been missed by your main client installation method.'
    Not sure where you pulled this from but it's not the consensus. Auto-client upgrade is a great choice. Microsoft upgraded all of their internal clients to SP1 using it (and I'm sure they used it for R2 also although I have not explicitly heard that).

    Jason | http://blog.configmgrftw.com

    Friday, October 25, 2013 6:01 PM
  • I agree with Jason's reply. That method is so easy.

    In regards to the configuration manage client package, the content is required when using client push. This has to be distributed to the DPs (normally done automatically).

    I had some installations fail because the content was not on the remote DPs (I configured my DPs for Prestaging and in that case, the following checkbox needs to be enabled: hierarchy settings > automatic client upgrade > automatically distribute client installation package to DPs that are enabled for prestaged content.

    I would suggest using the auto-client upgrade feature. If you need more control over the upgrade (grouping/scheduling), you may have to use a script-based method (GPO, SCCM package, SUP-based, etc).

    Friday, October 25, 2013 6:23 PM
  • Thanks for the replies - wish Technet gave the same sort of useful advice! (ie if they did all their internal clients this way then why not say so?)

    You can find the quote in here: http://technet.microsoft.com/en-us/library/gg712298.aspx 

    I'll try creating a package with no arguments for ccmsetup.exe and/or if that fails will consider the auto client method

    Friday, October 25, 2013 8:59 PM
  • The note right below that statement in the doc more or less does:

    "For System Center 2012 Configuration Manager SP1 and System Center 2012 R2 Configuration Manager only:      

    The performance improvements in Configuration Manager SP1 let you use automatic client upgrades as the main method to upgrade clients. However, the performance of this method might be affected by the infrastructure of your hierarchy, such as the number of clients that you have"


    Jason | http://blog.configmgrftw.com

    • Marked as answer by David b111 Monday, October 28, 2013 9:23 AM
    Friday, October 25, 2013 9:04 PM