From b7021b15bc49eb7a6125d458d7a829c7a9ba10c2 Mon Sep 17 00:00:00 2001 From: GrafAlk <124048092+grafalk@users.noreply.github.com> Date: Wed, 3 Jun 2026 16:30:23 +0300 Subject: [PATCH] Update configure-precache-content.md Are you sure that in part need don't use 'Download content locally when needed by the running task sequence' option ? For a task sequence that installs an OS image, don't use the deployment option to **Download content locally when needed by the running task sequence**. When the task sequence wipes the disk before it applies the OS image, it removes the client cache. Since the content is gone, the task sequence fails. In my opinion must be : For a task sequence that installs an OS image, don't use the deployment option to **Download all content locally before starting task sequence**. Because in this case client download all content, then disk will be wipe and TS failed. In short need to replace "Download content locally when needed by the running task sequence" on "Download all content locally before starting task sequence" Am I right ? :) --- intune/configmgr/osd/deploy-use/configure-precache-content.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/intune/configmgr/osd/deploy-use/configure-precache-content.md b/intune/configmgr/osd/deploy-use/configure-precache-content.md index 92f595f6b36..77dc31c3ebd 100644 --- a/intune/configmgr/osd/deploy-use/configure-precache-content.md +++ b/intune/configmgr/osd/deploy-use/configure-precache-content.md @@ -103,7 +103,7 @@ For example, the following **Upgrade OS** step uses the English version: - On the **Distribution Points** tab, configure the **Deployment options** settings. If the content isn't pre-cached before a user starts the installation, the client uses these settings. > [!IMPORTANT] - > For a task sequence that installs an OS image, don't use the deployment option to **Download content locally when needed by the running task sequence**. When the task sequence wipes the disk before it applies the OS image, it removes the client cache. Since the content is gone, the task sequence fails. These deployment options are dynamic based on other options you select for the deployment. For more information, see [Deploy a task sequence](deploy-a-task-sequence.md#bkmk_deploy-options). + > For a task sequence that installs an OS image, don't use the deployment option to **Download all content locally before starting task sequence**. When the task sequence wipes the disk before it applies the OS image, it removes the client cache. Since the content is gone, the task sequence fails. These deployment options are dynamic based on other options you select for the deployment. For more information, see [Deploy a task sequence](deploy-a-task-sequence.md#bkmk_deploy-options). ## User experience