From 1f0ac063fbb979bce1017c0fe14f53bc226e4e20 Mon Sep 17 00:00:00 2001 From: Rei Ikei <47890550+reiikei@users.noreply.github.com> Date: Wed, 18 Dec 2024 09:05:40 +0900 Subject: [PATCH 1/4] Update mcc-ent-edu-overview.md Confirmed with Andy that MCC is supported in other Autopilot scenarios. --- windows/deployment/do/mcc-ent-edu-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/do/mcc-ent-edu-overview.md b/windows/deployment/do/mcc-ent-edu-overview.md index 125aed12f4b..71d131633e4 100644 --- a/windows/deployment/do/mcc-ent-edu-overview.md +++ b/windows/deployment/do/mcc-ent-edu-overview.md @@ -31,7 +31,7 @@ Microsoft Connected Cache deployed directly to Windows relies on [Windows Subsys Microsoft Connected Cache for Enterprise and Education (preview) is intended to support the following content delivery scenarios: -- Pre-provisioning of devices using Windows Autopilot +- Windows Autopilot deployment scenarios - Co-managed clients that get monthly updates and Win32 apps from Microsoft Intune - Cloud-only managed devices, such as Intune-enrolled devices without the Configuration Manager client, that get monthly updates and Win32 apps from Microsoft Intune From 1748ae768fd09513e9a05aceaa836eaa8e16a161 Mon Sep 17 00:00:00 2001 From: Rei Ikei <47890550+reiikei@users.noreply.github.com> Date: Wed, 18 Dec 2024 15:23:43 +0900 Subject: [PATCH 2/4] Update mcc-ent-edu-overview.md --- windows/deployment/do/mcc-ent-edu-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/do/mcc-ent-edu-overview.md b/windows/deployment/do/mcc-ent-edu-overview.md index 71d131633e4..3354775fb43 100644 --- a/windows/deployment/do/mcc-ent-edu-overview.md +++ b/windows/deployment/do/mcc-ent-edu-overview.md @@ -29,7 +29,7 @@ Microsoft Connected Cache deployed directly to Windows relies on [Windows Subsys ## Supported scenarios and configurations -Microsoft Connected Cache for Enterprise and Education (preview) is intended to support the following content delivery scenarios: +Microsoft Connected Cache for Enterprise and Education (preview) is intended to support all Windows cloud downloads that use Delivery Optimization. Including, but not limited to the following content delivery scenarios: - Windows Autopilot deployment scenarios - Co-managed clients that get monthly updates and Win32 apps from Microsoft Intune From 18aa289b719deecf6d8cf7735e89561fa6ed9f0a Mon Sep 17 00:00:00 2001 From: Meghan Stewart <33289333+mestew@users.noreply.github.com> Date: Mon, 6 Jan 2025 11:17:34 -0800 Subject: [PATCH 3/4] Update windows/deployment/do/mcc-ent-edu-overview.md edit --- windows/deployment/do/mcc-ent-edu-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/do/mcc-ent-edu-overview.md b/windows/deployment/do/mcc-ent-edu-overview.md index 3354775fb43..a09f4f9a76c 100644 --- a/windows/deployment/do/mcc-ent-edu-overview.md +++ b/windows/deployment/do/mcc-ent-edu-overview.md @@ -29,7 +29,7 @@ Microsoft Connected Cache deployed directly to Windows relies on [Windows Subsys ## Supported scenarios and configurations -Microsoft Connected Cache for Enterprise and Education (preview) is intended to support all Windows cloud downloads that use Delivery Optimization. Including, but not limited to the following content delivery scenarios: +Microsoft Connected Cache for Enterprise and Education (preview) is intended to support all Windows cloud downloads that use Delivery Optimization including, but not limited to, the following content delivery scenarios: - Windows Autopilot deployment scenarios - Co-managed clients that get monthly updates and Win32 apps from Microsoft Intune From baf77a52d3588b6c0f31ab8442296d76f40e0ba8 Mon Sep 17 00:00:00 2001 From: Ryan Williams <103447364+Ryan-K-Williams@users.noreply.github.com> Date: Mon, 6 Jan 2025 13:15:01 -0800 Subject: [PATCH 4/4] Update windows-autopatch-manage-driver-and-firmware-updates.md As part of unification we changed the autopatch deferral period from 0-14 days to 0-30 days. --- .../windows-autopatch-manage-driver-and-firmware-updates.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/windows-autopatch/manage/windows-autopatch-manage-driver-and-firmware-updates.md b/windows/deployment/windows-autopatch/manage/windows-autopatch-manage-driver-and-firmware-updates.md index ddab13c4408..e9684918197 100644 --- a/windows/deployment/windows-autopatch/manage/windows-autopatch-manage-driver-and-firmware-updates.md +++ b/windows/deployment/windows-autopatch/manage/windows-autopatch-manage-driver-and-firmware-updates.md @@ -68,7 +68,7 @@ For deployment rings set to **Automatic**, you can choose the deferral period fo The deferral period allows you to delay the installation of driver and firmware updates on the devices in the specified deployment ring in case you want to test the update on a smaller group of devices first or avoid potential disruptions during a busy period. -The deferral period can be set from 0 to 14 days, and it can be different for each deployment ring. +The deferral period can be set from 0 to 30 days, and it can be different for each deployment ring. > [!NOTE] > The deferral period only applies to automatically approved driver and firmware updates. An admin must specify the date to start offering a driver with any manual approval.