locked
Build Package To Upgrade SCCM Client To Version 1610 RRS feed

  • Question

  • Post SCCM 1610 upgrade question:

    In our environment we have many distributed workstation support groups, so due to political reasons we are not able to "auto update SCCM clients". Instead we have to create a package that each workstation admin group can deploy when they are ready. To build a package to upgrade the existing clients to SCCM 1610, which source content should be used?

    • \\<Site Server Name>\SMS_<Site Code>\Client\
    • \\<Site Server Name>\SMS_<Site Code>\ClientUpgrade\

    -Tony


    Thursday, February 16, 2017 7:56 PM

Answers

All replies

  • The first one.

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

    • Proposed as answer by Frank Dong Friday, February 17, 2017 8:35 AM
    • Marked as answer by Tony Chirillo Friday, February 17, 2017 12:15 PM
    • Unmarked as answer by Tony Chirillo Friday, February 17, 2017 12:15 PM
    • Marked as answer by Tony Chirillo Friday, February 17, 2017 12:19 PM
    Friday, February 17, 2017 7:35 AM
  • By the way, there are ways to upgrade existing clients. You can review below document to choose a most suitable method:

    https://docs.microsoft.com/en-us/sccm/core/clients/manage/upgrade/upgrade-clients.


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, February 17, 2017 8:38 AM
  • Torsten Thanks!

    Quick question for you, if the first one is supposed to be used - what is the purpose of the ClientUpgrade folder? 

    I came across this blog that shows it being used: https://www.scconfigmgr.com/2013/02/18/upgrade-clients-to-sp1-with-the-client-upgrade-package/

    Granted this is for a few versions back...

    -Tony

    Friday, February 17, 2017 12:19 PM