none
in-place upgrade task sequence RRS feed

  • Question

  • we have a task sequence that will install some software and then do an in-place upgrade of Windows 10, from 1709 to 1809.   The TS will install 4 Packages.  Each package is downloaded to c:\_SMSTaskSequence\Packages.  Each package installs without error.   Then the 5th package is not a package but an Application.  It gets downloaded to C:\Windows\CCMCACHE

    Why? Why does the application get downloaded to a different location?  We were under the impression that a TS does not use c:\Windows\ccmcache for content.

    mqh7

    Monday, June 24, 2019 4:05 PM

All replies

  • Hi 

    Based on my experience, we can configure where to download the content in the Download Package Content step of in-place upgrade task sequence: task Sequence working directory, Configuration Manager client cache, custom path. They will all work well.

    1. Task Sequence working directory: The task sequence will download the content to the C:\_SMSTaskSequence\Packages directory.
    2. Configuration Manager client cache: The task sequence will download the content to the C:\_SMSTaskSequence\Packages directory. After that it will stage the downloaded content to the client cache directory C:\Windows\CCMCACHE. 
    3. Custom path: The task sequence will download the content to the C:\_SMSTaskSequence\Packages directory. After that it will stage the downloaded content to the custom path. 

    For more details, please refer to:
    Download package content during a task sequence

    Hope it helps. Thanks for your time.

    Best regards,
    Simon Ren

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

    Tuesday, June 25, 2019 8:31 AM
  • the download package content step does not appear to work for Applications.  Only Driver packages, boot images, OS and packages.

    so my question remains.  Why would an Application get placed in the ccmcache folder while packages go to _smstasksequence?

    thanks. 


    mqh7

    Tuesday, June 25, 2019 5:44 PM
  • I guess it is just by design. What is the actual problem here?

    MCSE Mobility 2018. Expert on SCCM, Windows 10, ALOVPN, MBAM.

    Tuesday, June 25, 2019 9:36 PM
  • you can clear SCCM Client casch with is powershell commandes :

    $resman = new-object -com "UIResource.UIResourceMgr"
    $cacheInfo = $resman.GetCacheInfo()
    $cacheinfo.GetCacheElements()  | foreach {$cacheInfo.DeleteCacheElement($_.CacheElementID)}

    • Proposed as answer by slimyaakoubi Friday, November 8, 2019 12:22 PM
    Wednesday, November 6, 2019 8:30 PM