deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-05-12 21:37:22 +00:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

updates

Browse Source
This commit is contained in:
Paolo Matarazzo 2025-04-04 08:11:23 -04:00
parent 8260848c72
commit a8314fd9df
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
windows/configuration/taskbar/pinned-apps.md
View File

@ -114,16 +114,19 @@ On devices with [KBXYZ][KB-1] or later, you can allow specific pinned apps to be
To use this option, add `PinGeneration="1"` to the pins you want to allow users to unpin. The value of `PinGeneration` can be any number, and it's used to identify the pin version. If the value changes, the app is pinned again during the next policy update cycle. This allows IT admins to repin an app, if needed. To use this option, add `PinGeneration="1"` to the pins you want to allow users to unpin. The value of `PinGeneration` can be any number, and it's used to identify the pin version. If the value changes, the app is pinned again during the next policy update cycle. This allows IT admins to repin an app, if needed.
Here are some details to better understand and use `PinGeneration`: Here's the logic used by `PinGeneration`:
- When `PinGeneration` isn't defined, users can unpin that element, but the pin is 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 `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 - 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 - 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'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 is 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
Some tips for using `PinGeneration`:
- Define `PinGeneration` with a starting 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
> [!CAUTION] > [!CAUTION]
> 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. > 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.
> >