From 4823a73b61632465107ee96f91363b026c044819 Mon Sep 17 00:00:00 2001 From: PhilKang0704 Date: Tue, 19 Nov 2024 01:56:26 +0800 Subject: [PATCH 1/2] fix broken links --- .../solutions/end-to-end-guides/macos-endpoints-get-started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/memdocs/solutions/end-to-end-guides/macos-endpoints-get-started.md b/memdocs/solutions/end-to-end-guides/macos-endpoints-get-started.md index 3c64045cf8c..061232f7df4 100644 --- a/memdocs/solutions/end-to-end-guides/macos-endpoints-get-started.md +++ b/memdocs/solutions/end-to-end-guides/macos-endpoints-get-started.md @@ -565,7 +565,7 @@ In [Phase 1 - Set up your environment](#phase-1---set-up-your-environment), you If you're deploying the VPP version of OneDrive, then enter `com.microsoft.OneDrive-Mac.FinderSync`. - During Microsoft OneDrive configuration, end users are prompted to allow sync icons by enabling the Finder Sync extension. There's a sample script that can configure the finder extension for the user. For more information on the script, go to the [GitHub - Microsoft Intune Shell samples](https://github.com/microsoft/shell-intune-samples/blob/master/macOS/Config/EnableOneDriveFinderSync/EnableOneDriveFinderSync.sh). + During Microsoft OneDrive configuration, end users are prompted to allow sync icons by enabling the Finder Sync extension. There's a sample script that can configure the finder extension for the user. For more information on the script, go to the [GitHub - Microsoft Intune Shell samples](https://github.com/microsoft/shell-intune-samples/blob/master/macOS/Config/Enable%20OneDrive%20Finder%20Sync/EnableOneDriveFinderSync.sh). ### Device Configuration From 47169c633f852d476a365d8f9cfa6418881839db Mon Sep 17 00:00:00 2001 From: PhilKang0704 Date: Tue, 19 Nov 2024 02:01:53 +0800 Subject: [PATCH 2/2] fix broken links --- .../core/plan-design/configs/support-for-windows-adk.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/memdocs/configmgr/core/plan-design/configs/support-for-windows-adk.md b/memdocs/configmgr/core/plan-design/configs/support-for-windows-adk.md index 18f5e1cf56b..a3a288ee196 100644 --- a/memdocs/configmgr/core/plan-design/configs/support-for-windows-adk.md +++ b/memdocs/configmgr/core/plan-design/configs/support-for-windows-adk.md @@ -58,7 +58,7 @@ The following table lists the versions of the Windows ADK that you can use with Instead use the **ADK 10.1.26100.1 (May 2024)** (10.1.26100.1) or newer where these issues are resolved. -- For information on applying the [BlackLotus UEFI bootkit vulnerability](https://prod.support.services.microsoft.com/topic/kb5025885-how-to-manage-the-windows-boot-manager-revocations-for-secure-boot-changes-associated-with-cve-2023-24932-41a975df-beb2-40c1-99a3-b3ff139f832d) security updates to boot images from the ADKs before the **ADK 10.1.26100.1 (May 2024)** (10.1.26100.1), see [Customize Windows PE boot images](/windows/deployment/customize-boot-image). Boot images from the **ADK 10.1.26100.1 (May 2024)** (10.1.26100.1) and newer already have the BlackLotus UEFI bootkit vulnerability security update applied to them. For this reason, it's recommended to use boot images from the **ADK 10.1.26100.1 (May 2024)** (10.1.26100.1) or newer. +- For information on applying the [BlackLotus UEFI bootkit vulnerability](https://support.microsoft.com/topic/kb5025885-how-to-manage-the-windows-boot-manager-revocations-for-secure-boot-changes-associated-with-cve-2023-24932-41a975df-beb2-40c1-99a3-b3ff139f832d) security updates to boot images from the ADKs before the **ADK 10.1.26100.1 (May 2024)** (10.1.26100.1), see [Customize Windows PE boot images](/windows/deployment/customize-boot-image). Boot images from the **ADK 10.1.26100.1 (May 2024)** (10.1.26100.1) and newer already have the BlackLotus UEFI bootkit vulnerability security update applied to them. For this reason, it's recommended to use boot images from the **ADK 10.1.26100.1 (May 2024)** (10.1.26100.1) or newer. - Windows Server builds have the same Windows ADK requirement as the associated Windows client version. For example, Windows Server 2016 is the same build version as Windows 10 LTSB 2016.