From 8260848c7227ebf7a31aa84064b928bc9bb3d51c Mon Sep 17 00:00:00 2001 From: Paolo Matarazzo <74918781+paolomatarazzo@users.noreply.github.com> Date: Fri, 4 Apr 2025 08:03:46 -0400 Subject: [PATCH] acrolinx --- windows/configuration/taskbar/pinned-apps.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/windows/configuration/taskbar/pinned-apps.md b/windows/configuration/taskbar/pinned-apps.md index 19fdec25c2..80e5ae4798 100644 --- a/windows/configuration/taskbar/pinned-apps.md +++ b/windows/configuration/taskbar/pinned-apps.md @@ -116,19 +116,19 @@ To use this option, add `PinGeneration="1"` to the pins you want to allow users Here are some details to better understand and use `PinGeneration`: -- When `PinGeneration` isn't defined, users can unpin that element, but the pin will be repinned during the next policy update cycle -- When `PinGeneration` is defined, users can unpin that element, and the pin won't be repinned during the next policy update cycle +- When `PinGeneration` isn't defined, users can unpin that element, but the pin is repinned during the next policy update cycle +- When `PinGeneration` is defined, users can unpin that element, and the pin isn't repinned during the next policy update cycle - When the `PinGeneration` value changes, for example from `1` to `2`, the element is pinned again, even if the user unpinned it previously - Every `PinGeneration` number is specific to an app. You can define a value of `1` for one app, and a value of `2` for another app -- Start `PinGeneration` with a value of `1` and increment the number each time you want to repin the app. This way, if the user unpins the app, it won't be repinned until you change the number again +- Start `PinGeneration` with a value of `1` and increment the number each time you want to repin the app. This way, if the user unpins the app, it's not repinned until you change the number again - For simple management, always increment the `PinGeneration` number and don't reuse numbers -- If you remove the `PinGeneration` attribute, the app will be repinned during the next policy update cycle even if the user unpinned it previously. This is the default behavior +- If you remove the `PinGeneration` attribute, the app is repinned during the next policy update cycle even if the user unpinned it previously. This is the default behavior > [!CAUTION] -> The `PinGeneration` option is only available on devices with [KBXYZ][KB-1] or later. When assigning this policy, target devices that are patched, otherwise the taskbar pins don't apply. +> The `PinGeneration` option is only available on devices with [KBXYZ][KB-1] or later. Only assign this policy to devices that are patched, otherwise the taskbar pins don't apply. > ->- If you use Microsoft Intune, you can use [filters](/intune/intune-service/fundamentals/filters) to target only devices with the required patch ->- If you use GPO, you can use [WMI filters](/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/cc732796(v=ws.11)) to target only devices with the required patch +>- With Microsoft Intune you can use [filters](/intune/intune-service/fundamentals/filters) to target only devices with the required patch +>- With GPO you can use [WMI filters](/previous-versions/windows/it-pro/windows-server-2008-r2-and-2008/cc732796(v=ws.11)) to target only devices with the required patch ::: zone-end @@ -216,7 +216,7 @@ To replace all default pins and add your own pins, add `PinListPlacement="Replac **Before and after:** -:::image type="content" source="images/pin-add-pingeneration-11.png" alt-text="Screenshot of the Windows 11 taskbar, before and after adding pins with the M365 companion apps." border="false" lightbox="images/pin-add-pingeneration-11.png"::: +:::image type="content" source="images/pin-add-pingeneration-11.png" alt-text="Screenshot of the Windows 11 taskbar, before and after adding pins with the Microsoft 365 companion apps." border="false" lightbox="images/pin-add-pingeneration-11.png"::: ::: zone-end