mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 02:13:43 +00:00
Restructuring of configuration docset
This commit is contained in:
Paolo Matarazzo
@ -0,0 +1,83 @@
|
||||
---
|
||||
title: Changes to Group Policy settings for Windows 10 Start menu
|
||||
description: Learn about changes to Group Policy settings for the Windows 10 Start menu. Also, learn about the new Windows 10 Start experience.
|
||||
ms.topic: whats-new
|
||||
appliesto:
|
||||
- ✅ <a href=/windows/release-health/supported-versions-windows-client target=_blank>Windows 10</a>
|
||||
ms.date: 08/18/2023
|
||||
---
|
||||
|
||||
# Changes to Group Policy settings for Windows 10 Start
|
||||
|
||||
|
||||
Windows 10 has a brand new Start experience. As a result, there are changes to the Group Policy settings that you can use to manage Start. Some policy settings are new or changed, and some old Start policy settings still apply. Other Start policy settings no longer apply and are deprecated.
|
||||
|
||||
## Start policy settings supported for Windows 10 Pro, Windows 10 Enterprise, and Windows 10 Education
|
||||
|
||||
|
||||
These policy settings are available in **Administrative Templates\\Start Menu and Taskbar** under **User Configuration**.
|
||||
|
||||
|Policy|Notes|
|
||||
|--- |--- |
|
||||
|Clear history of recently opened documents on exit|Documents that the user opens are tracked during the session. When the user signs off, the history of opened documents is deleted.|
|
||||
|Don't allow pinning items in Jump Lists|Jump Lists are lists of recently opened items, such as files, folders, or websites, organized by the program that you use to open them. This policy prevents users from pinning items to any Jump List.|
|
||||
|Don't display or track items in Jump Lists from remote locations|When this policy is applied, only items local on the computer are shown in Jump Lists.|
|
||||
|Don't keep history of recently opened documents|Documents that the user opens aren't tracked during the session.|
|
||||
|Prevent changes to Taskbar and Start Menu Settings|In Windows 10, this policy disables all of the settings in **Settings** > **Personalization** > **Start** and the options in dialog available via right-click Taskbar > **Properties**|
|
||||
|Prevent users from customizing their Start Screen|Use this policy with a [customized Start layout](windows-10-start-layout-options-and-policies.md) to prevent users from changing it|
|
||||
|Prevent users from uninstalling applications from Start|In Windows 10, this policy removes the uninstall button in the context menu. It doesn't prevent users from uninstalling the app through other entry points (for example, PowerShell)|
|
||||
|Remove All Programs list from the Start menu|In Windows 10, this policy removes the **All apps** button.|
|
||||
|Remove and prevent access to the Shut Down, Restart, Sleep, and Hibernate commands|This policy removes the Shut Down, Restart, Sleep, and Hibernate commands from the Start Menu, Start Menu power button, CTRL+ALT+DEL screen, and Alt+F4 Shut Down Windows menu.|
|
||||
|Remove common program groups from Start Menu|As in earlier versions of Windows, this policy removes apps specified in the All Users profile from Start|
|
||||
|Remove frequent programs list from the Start Menu|In Windows 10, this policy removes the top left **Most used** group of apps.|
|
||||
|Remove Logoff on the Start Menu|**Logoff** has been changed to **Sign Out** in the user interface, however the functionality is the same.|
|
||||
|Remove pinned programs list from the Start Menu|In Windows 10, this policy removes the bottom left group of apps (by default, only File Explorer and Settings are pinned).|
|
||||
|Show "Run as different user" command on Start|This policy enables the **Run as different user** option in the right-click menu for apps.|
|
||||
|Start Layout|This policy applies a specific Start layout, and it also prevents users from changing the layout. This policy can be configured in **User Configuration** or **Computer Configuration**.|
|
||||
|Force Start to be either full screen size or menu size|This policy applies a specific size for Start.|
|
||||
|
||||
## Deprecated Group Policy settings for Start
|
||||
|
||||
The Start policy settings listed in the following table don't work on Windows 10. Most of them were deprecated in Windows 8 however a few more were deprecated in Windows 10. Deprecation in this case means that the policy setting won't work on Windows 10. The "Supported on" text for a policy setting won't list Windows 10. The policy settings are still in the Group Policy Management Console and can be used on the operating systems that they apply to.
|
||||
|
||||
| Policy | When deprecated |
|
||||
|----------------------------------------------------------------------------------|-----------------|
|
||||
| Go to the desktop instead of Start when signing in | Windows 10 |
|
||||
| List desktop apps first in the Apps view | Windows 10 |
|
||||
| Pin Apps to Start when installed (User or Computer) | Windows 10 |
|
||||
| Remove Default Programs link from the Start menu. | Windows 10 |
|
||||
| Remove Documents icon from Start Menu | Windows 10 |
|
||||
| Remove programs on Settings menu | Windows 10 |
|
||||
| Remove Run menu from Start Menu | Windows 10 |
|
||||
| Remove the "Undock PC" button from the Start Menu | Windows 10 |
|
||||
| Search just apps from the Apps view | Windows 10 |
|
||||
| Show Start on the display the user is using when they press the Windows logo key | Windows 10 |
|
||||
| Show the Apps view automatically when the user goes to Start | Windows 10 |
|
||||
| Add the Run command to the Start Menu | Windows 8 |
|
||||
| Change Start Menu power button | Windows 8 |
|
||||
| Gray unavailable Windows Installer programs Start Menu shortcuts | Windows 8 |
|
||||
| Remove Downloads link from Start Menu | Windows 8 |
|
||||
| Remove Favorites menu from Start Menu | Windows 8 |
|
||||
| Remove Games link from Start Menu | Windows 8 |
|
||||
| Remove Help menu from Start Menu | Windows 8 |
|
||||
| Remove Homegroup link from Start Menu | Windows 8 |
|
||||
| Remove Music icon from Start Menu | Windows 8 |
|
||||
| Remove Network icon from Start Menu | Windows 8 |
|
||||
| Remove Pictures icon from Start Menu | Windows 8 |
|
||||
| Remove Recent Items menu from Start Menu | Windows 8 |
|
||||
| Remove Recorded TV link from Start Menu | Windows 8 |
|
||||
| Remove user folder link from Start Menu | Windows 8 |
|
||||
| Remove Videos link from Start Menu | Windows 8 |
|
||||
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Manage Windows 10 Start and taskbar layout](windows-10-start-layout-options-and-policies.md)
|
||||
- [Configure Windows 10 taskbar](configure-windows-10-taskbar.md)
|
||||
- [Customize and export Start layout](customize-and-export-start-layout.md)
|
||||
- [Add image for secondary tiles](start-secondary-tiles.md)
|
||||
- [Start layout XML for desktop editions of Windows 10 (reference)](start-layout-xml-desktop.md)
|
||||
- [Customize Windows 10 Start and taskbar with Group Policy](customize-windows-10-start-screens-by-using-group-policy.md)
|
||||
- [Customize Windows 10 Start and taskbar with provisioning packages](customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md)
|
||||
- [Customize Windows 10 Start and taskbar with mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md)
|
||||
180
windows/configuration/start/customize-and-export-start-layout.md
Normal file
180
windows/configuration/start/customize-and-export-start-layout.md
Normal file
@ -0,0 +1,180 @@
|
||||
---
|
||||
title: Customize and export Start layout
|
||||
description: The easiest method for creating a customized Start layout is to set up the Start screen and export the layout.
|
||||
ms.topic: how-to
|
||||
|
||||
ms.date: 08/18/2023
|
||||
ms.collection:
|
||||
- tier1
|
||||
---
|
||||
|
||||
# Customize and export Start layout
|
||||
|
||||
**Applies to**:
|
||||
|
||||
- Windows 10
|
||||
|
||||
>**Looking for consumer information?** See [Customize the Start menu](https://go.microsoft.com/fwlink/p/?LinkId=623630)
|
||||
|
||||
The easiest method for creating a customized Start layout to apply to other Windows 10 devices is to set up the Start screen on a test computer and then export the layout.
|
||||
|
||||
After you export the layout, decide whether you want to apply a *full* Start layout or a *partial* Start layout.
|
||||
|
||||
When a full Start layout is applied, the users can't pin, unpin, or uninstall apps from Start. Users can view and open all apps in the **All Apps** view, but they can't pin any apps to Start.
|
||||
|
||||
When [a partial Start layout](#configure-a-partial-start-layout) is applied, the contents of the specified tile groups can't be changed, but users can move those groups, and can also create and customize their own groups.
|
||||
|
||||
> [!NOTE]
|
||||
> Partial Start layout is only supported on Windows 10, version 1511 and later.
|
||||
|
||||
You can deploy the resulting .xml file to devices using one of the following methods:
|
||||
|
||||
- [Group Policy](customize-windows-10-start-screens-by-using-group-policy.md)
|
||||
|
||||
- [Windows Configuration Designer provisioning package](customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md)
|
||||
|
||||
- [Mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md)
|
||||
|
||||
### Customize the Start screen on your test computer
|
||||
|
||||
To prepare a Start layout for export, you simply customize the Start layout on a test computer.
|
||||
|
||||
**To prepare a test computer**
|
||||
|
||||
1. Set up a test computer on which to customize the Start layout. Your test computer should have the operating system that is installed on the users' computers (Windows 10 Pro, Enterprise, or Education). Install all apps and services that the Start layout should display.
|
||||
|
||||
1. Create a new user account that you'll use to customize the Start layout.
|
||||
|
||||
**To customize Start**
|
||||
|
||||
1. Sign in to your test computer with the user account that you created.
|
||||
|
||||
1. Customize the Start layout as you want users to see it by using the following techniques:
|
||||
|
||||
- **Pin apps to Start**. From Start, type the name of the app. When the app appears in the search results, right-click the app, and then select **Pin to Start**.
|
||||
|
||||
To view all apps, select **All apps** in the bottom-left corner of Start. Right-click any app, and pin or unpin it from Start.
|
||||
|
||||
- **Unpin apps** that you don't want to display. To unpin an app, right-click the app, and then select **Unpin from Start**.
|
||||
|
||||
- **Drag tiles** on Start to reorder or group apps.
|
||||
|
||||
- **Resize tiles**. To resize tiles, right-click the tile and then select **Resize.**
|
||||
|
||||
- **Create your own app groups**. Drag the apps to an empty area. To name a group, select above the group of tiles and then type the name in the **Name group** field that appears above the group.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> In Windows 10, version 1703, if the Start layout includes tiles for apps that are not installed on the device that the layout is later applied to, the tiles for those apps will be blank. The blank tiles will persist until the next time the user signs in, at which time the blank tiles are removed. Some system events may cause the blank tiles to be removed before the next sign-in.
|
||||
>
|
||||
> In earlier versions of Windows 10, no tile would be pinned.
|
||||
|
||||
### Export the Start layout
|
||||
|
||||
When you have the Start layout that you want your users to see, use the [Export-StartLayout](/powershell/module/startlayout/export-startlayout) cmdlet in Windows PowerShell to export the Start layout to an .xml file. Start layout is located by default at C:\Users\username\AppData\Local\Microsoft\Windows\Shell\
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you include secondary Microsoft Edge tiles (tiles that link to specific websites in Microsoft Edge), see [Add custom images to Microsoft Edge secondary tiles](start-secondary-tiles.md) for instructions.
|
||||
|
||||
**To export the Start layout to an .xml file**
|
||||
|
||||
1. While signed in with the same account that you used to customize Start, right-click Start, and select **Windows PowerShell**.
|
||||
|
||||
1. On a device running Windows 10, version 1607, 1703, or 1803, at the Windows PowerShell command prompt, enter the following command:
|
||||
|
||||
`Export-StartLayout -path <path><file name>.xml`
|
||||
|
||||
On a device running Windows 10, version 1809 or higher, run the **Export-StartLayout** with the switch **-UseDesktopApplicationID**. For example:
|
||||
|
||||
```PowerShell
|
||||
Export-StartLayout -UseDesktopApplicationID -Path layout.xml
|
||||
```
|
||||
|
||||
In the previous command, `-path` is a required parameter that specifies the path and file name for the export file. You can specify a local path or a UNC path (for example, \\\\FileServer01\\StartLayouts\\StartLayoutMarketing.xml).
|
||||
|
||||
Use a file name of your choice—for example, StartLayoutMarketing.xml. Include the .xml file name extension. The [Export-StartLayout](/powershell/module/startlayout/export-startlayout) cmdlet doesn't append the file name extension, and the policy settings require the extension.
|
||||
|
||||
Example of a layout file produced by `Export-StartLayout`:
|
||||
|
||||
```xml
|
||||
<LayoutModificationTemplate Version="1" xmlns="https://schemas.microsoft.com/Start/2014/LayoutModification">
|
||||
<DefaultLayoutOverride>
|
||||
<StartLayoutCollection>
|
||||
<defaultlayout:StartLayout GroupCellWidth="6" xmlns:defaultlayout="https://schemas.microsoft.com/Start/2014/FullDefaultLayout">
|
||||
<start:Group Name="Life at a glance" xmlns:start="https://schemas.microsoft.com/Start/2014/StartLayout">
|
||||
<start:Tile Size="2x2" Column="0" Row="0" AppUserModelID="Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge" />
|
||||
<start:Tile Size="2x2" Column="4" Row="0" AppUserModelID="Microsoft.Windows.Cortana_cw5n1h2txyewy!CortanaUI" />
|
||||
<start:Tile Size="2x2" Column="2" Row="0" AppUserModelID="Microsoft.BingWeather_8wekyb3d8bbwe!App" />
|
||||
</start:Group>
|
||||
|
||||
</defaultlayout:StartLayout>
|
||||
</StartLayoutCollection>
|
||||
</DefaultLayoutOverride>
|
||||
</LayoutModificationTemplate>
|
||||
```
|
||||
|
||||
1. (Optional) Edit the .xml file to add [a taskbar configuration](configure-windows-10-taskbar.md) or to [modify the exported layout](start-layout-xml-desktop.md). When you make changes to the exported layout, be aware that [the order of the elements in the .xml file is critical.](start-layout-xml-desktop.md#required-order)
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If the Start layout that you export contains tiles for desktop (Win32) apps or .url links, **Export-StartLayout** will use **DesktopApplicationLinkPath** in the resulting file. Use a text or XML editor to change **DesktopApplicationLinkPath** to **DesktopApplicationID**. See [Specify Start tiles](start-layout-xml-desktop.md#specify-start-tiles) for details on using the app ID in place of the link path.
|
||||
|
||||
> [!NOTE]
|
||||
> All clients that the start layout applies to must have the apps and other shortcuts present on the local system in the same location as the source for the Start layout.
|
||||
>
|
||||
> For scripts and application tile pins to work correctly, follow these rules:
|
||||
>
|
||||
>* Executable files and scripts should be listed in \Program Files or wherever the installer of the app places them.
|
||||
>
|
||||
>* Shortcuts that will pinned to Start should be placed in \ProgramData\Microsoft\Windows\Start Menu\Programs.
|
||||
|
||||
>
|
||||
>* If you place executable files or scripts in the \ProgramData\Microsoft\Windows\Start Menu\Programs folder, they will not pin to Start.
|
||||
>
|
||||
>* Start on Windows 10 does not support subfolders. We only support one folder. For example, \ProgramData\Microsoft\Windows\Start Menu\Programs\Folder. If you go any deeper than one folder, Start will compress the contents of all the subfolder to the top level.
|
||||
>
|
||||
>* Three additional shortcuts are pinned to the start menu after the export. These are shortcuts to %ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs, %APPDATA%\Microsoft\Windows\Start Menu\Programs, and %APPDATA%\Microsoft\Windows\Start Menu\Programs\System Tools\.
|
||||
|
||||
### Configure a partial Start layout
|
||||
|
||||
A partial Start layout enables you to add one or more customized tile groups to users' Start screens or menus, while still allowing users to make changes to other parts of the Start layout. All groups that you add are *locked*, meaning users can't change the contents of those tile groups, however users can change the location of those groups. Locked groups are identified with an icon, as shown in the following image.
|
||||
|
||||
|
||||
|
||||
When a partial Start layout is applied for the first time, the new groups are added to the users' existing Start layouts. If an app tile is in both an existing group and in a new locked group, the duplicate app tile is removed from the existing (unlocked) group.
|
||||
|
||||
When a partial Start layout is applied to a device that already has a StartLayout.xml applied, groups that were added previously are removed and the groups in the new layout are added.
|
||||
|
||||
If the Start layout is applied by Group Policy or MDM, and the policy is removed, the groups remain on the devices but become unlocked.
|
||||
|
||||
**To configure a partial Start screen layout**
|
||||
|
||||
1. [Customize the Start layout](#customize-the-start-screen-on-your-test-computer).
|
||||
|
||||
1. [Export the Start layout](#export-the-start-layout).
|
||||
1. Open the layout .xml file. There is a `<DefaultLayoutOverride>` element. Add `LayoutCustomizationRestrictionType="OnlySpecifiedGroups"` to the **DefaultLayoutOverride** element as follows:
|
||||
|
||||
```xml
|
||||
<DefaultLayoutOverride LayoutCustomizationRestrictionType="OnlySpecifiedGroups">
|
||||
```
|
||||
|
||||
1. Save the file and apply using any of the deployment methods.
|
||||
|
||||
> [!NOTE]
|
||||
> Office 2019 tiles might be removed from the Start menu when you upgrade Office 2019. This only occurs if Office 2019 app tiles are in a custom group in the Start menu and only contains the Office 2019 app tiles. To avoid this problem, place another app tile in the Office 2019 group prior to the upgrade. For example, add Notepad.exe or calc.exe to the group. This issue occurs because Office 2019 removes and reinstalls the apps when they are upgraded. Start removes empty groups when it detects that all apps for that group have been removed.
|
||||
|
||||
## Related articles
|
||||
|
||||
[Manage Windows 10 Start and taskbar layout](windows-10-start-layout-options-and-policies.md)
|
||||
|
||||
[Configure Windows 10 taskbar](configure-windows-10-taskbar.md)
|
||||
|
||||
[Add image for secondary tiles](start-secondary-tiles.md)
|
||||
|
||||
[Start layout XML for desktop editions of Windows 10 (reference)](start-layout-xml-desktop.md)
|
||||
|
||||
[Customize Windows 10 Start and taskbar with Group Policy](customize-windows-10-start-screens-by-using-group-policy.md)
|
||||
|
||||
[Customize Windows 10 Start and taskbar with provisioning packages](customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md)
|
||||
|
||||
[Customize Windows 10 Start and taskbar with mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md)
|
||||
|
||||
[Changes to Start policies in Windows 10](changes-to-start-policies-in-windows-10.md)
|
||||
@ -0,0 +1,189 @@
|
||||
---
|
||||
title: Add or remove pinned apps on the Start menu in Windows 11
|
||||
description: Export Start layout to LayoutModification.json with pinned apps, and add or remove pinned apps. Use the JSON text in an MDM policy to deploy a custom Start menu layout to Windows 11 devices.
|
||||
ms.reviewer: ericpapa
|
||||
ms.date: 01/10/2023
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Customize the Start menu layout on Windows 11
|
||||
|
||||
**Applies to**:
|
||||
|
||||
- Windows 11
|
||||
|
||||
> **Looking for OEM information?** See [Customize the Taskbar](/windows-hardware/customize/desktop/customize-the-windows-11-taskbar) and [Customize the Start layout](/windows-hardware/customize/desktop/customize-the-windows-11-start-menu).
|
||||
|
||||
Your organization can deploy a customized Start layout to your Windows 11 devices. Customizing the Start layout is common when you have similar devices used by many users, or you want to pin specific apps.
|
||||
|
||||
For example, you can override the default set of apps with your own a set of pinned apps, and in the order you choose. As an administrator, use this feature to pin apps, remove default pinned apps, order the apps, and more.
|
||||
|
||||
To add apps you want pinned to the Start menu, you use a JSON file. In previous Windows versions, IT administrators used an XML file to customize the Start menu. The XML file isn't available on Windows 11 and later ***unless*** [you're an OEM](/windows-hardware/customize/desktop/customize-the-windows-11-start-menu).
|
||||
|
||||
This article shows you how to export an existing Start menu layout, and use the JSON in a Microsoft Intune policy.
|
||||
|
||||
## Before you begin
|
||||
|
||||
- When you customize the Start layout, you overwrite the entire full layout. A partial Start layout isn't available. Users can pin and unpin apps, and uninstall apps from Start. When a user signs in or Explorer restarts, Windows reapplies the MDM policy. This action restores the specified layout and doesn't retain any user changes.
|
||||
|
||||
To prevent users from making any changes to the Start menu layout, see the [NoChangeStartMenu](/windows/client-management/mdm/policy-csp-admx-startmenu#admx-startmenu-nochangestartmenu) policy.
|
||||
|
||||
- It's recommended to use a mobile device management (MDM) provider. MDM providers help manage your devices, and help manage apps on your devices. You can use Microsoft Intune. Intune is a family of products that include Microsoft Intune, which is a cloud service, and Configuration Manager, which is on-premises.
|
||||
|
||||
In this article, we mention these services. If you're not managing your devices using an MDM provider, the following resources may help you get started:
|
||||
|
||||
- [Endpoint Management at Microsoft](/mem/endpoint-manager-overview)
|
||||
- [What is Microsoft Intune](/mem/intune/fundamentals/what-is-intune) and [Microsoft Intune planning guide](/mem/intune/fundamentals/intune-planning-guide)
|
||||
- [What is Configuration Manager?](/mem/configmgr/core/understand/introduction)
|
||||
|
||||
## Start menu features and areas
|
||||
|
||||
In Windows 11, the Start menu is redesigned with a simplified set of apps that are arranged in a grid of pages. There aren't folders, groups, or different-sized app icons:
|
||||
|
||||
:::image type="content" source="./images/customize-start-menu-layout-windows-11/start-menu-layout.png" alt-text="Sample start menu layout on Windows 11 devices that shows pinned apps, access to all apps, and shows recommended files.":::
|
||||
|
||||
Start has the following areas:
|
||||
|
||||
- **Pinned**: Shows pinned apps, or a subset of all of the apps installed on the device. You can create a list of pinned apps you want on the devices using the **ConfigureStartPins** policy. **ConfigureStartPins** overrides the entire layout, which also removes apps that are pinned by default.
|
||||
|
||||
This article shows you [how to use the **ConfigureStartPins** policy](#get-the-pinnedlist-json).
|
||||
|
||||
- **All apps**: Users select this option to see an alphabetical list of all the apps on the device. This section can't be customized using the JSON file.
|
||||
|
||||
The [Start/HideFrequentlyUsedApps CSP](/windows/client-management/mdm/policy-csp-start#start-hidefrequentlyusedapps) exposes settings that configure the "Most used" section, which is at the top of the all apps list.
|
||||
|
||||
In **Intune**, you can configure this Start menu layout feature, and more. For more information on the Start menu settings you can configure in an Intune policy, see [Windows 10/11 device settings to allow or restrict features](/mem/intune/configuration/device-restrictions-windows-10#start).
|
||||
|
||||
In **Group Policy**, there are policies that include settings that control the Start menu layout. Some policies may not work as expected. Be sure to test your policies before broadly deploying them across your devices:
|
||||
|
||||
- `Computer Configuration\Administrative Templates\Start Menu and Taskbar`
|
||||
- `User Configuration\Administrative Templates\Start Menu and Taskbar`
|
||||
|
||||
- **Recommended**: Shows recently opened files and recently installed apps. This section can only be customized in Windows 11 SE using the following policy.
|
||||
|
||||
- `Computer Configuration\Administrative Templates\Start Menu and Taskbar\Remove Recommended section from Start Menu`
|
||||
|
||||
## Create the JSON file
|
||||
|
||||
On an existing Windows 11 device, set up your own Start layout with the pinned apps you want users to see. Then, use the [Windows PowerShell Export-StartLayout](/powershell/module/startlayout/export-startlayout) cmdlet to export the existing layout to a `LayoutModification.json` file.
|
||||
|
||||
The JSON file controls the Start menu layout, and lists all the apps that are pinned. You can update the JSON file to:
|
||||
|
||||
- Change the order of existing apps. The apps in the JSON file are shown on Start in the same order.
|
||||
- Add more apps by entering the app ID. For more information, see [Get the pinnedList JSON](#get-the-pinnedlist-json) (in this article).
|
||||
|
||||
If you're familiar with creating JSON files, you can create your own `LayoutModification.json` file. But, it's easier and faster to export the layout from an existing device.
|
||||
|
||||
### Export an existing Start layout
|
||||
|
||||
1. Create a folder to save the `.json` file. For example, create the `C:\Layouts` folder.
|
||||
2. On a Windows 11 device, open the Windows PowerShell app.
|
||||
3. Run the following cmdlet. Name the file `LayoutModification.json`.
|
||||
|
||||
```powershell
|
||||
Export-StartLayout -Path "C:\Layouts\LayoutModification.json"
|
||||
|
||||
```
|
||||
|
||||
### Get the pinnedList JSON
|
||||
|
||||
1. Open the `LayoutModification.json` file in a JSON editor, such as Visual Studio Code or Notepad. For more information, see [edit JSON with Visual Studio Code](https://code.visualstudio.com/docs/languages/json).
|
||||
2. In the file, you see the `pinnedList` section. This section includes all of the pinned apps. Copy the `pinnedList` content in the JSON file. You'll use it in the next section.
|
||||
|
||||
In the following example, you see that Microsoft Edge, Microsoft Word, the Microsoft Store app, and Notepad are pinned:
|
||||
|
||||
```json
|
||||
{
|
||||
|
||||
"pinnedList": [
|
||||
|
||||
{ "desktopAppId": "MSEdge" },
|
||||
|
||||
{ "desktopAppId": "Microsoft.Office.WINWORD.EXE.15" },
|
||||
|
||||
{ "packagedAppId": "Microsoft.WindowsStore_8wekyb3d8bbwe!App" },
|
||||
|
||||
{ "packagedAppId": "Microsoft.WindowsNotepad_8wekyb3d8bbwe!App" }
|
||||
|
||||
]
|
||||
|
||||
}
|
||||
|
||||
```
|
||||
|
||||
3. Starting with Windows 11, the **ConfigureStartPins** policy is available. This policy uses the `LayoutModification.json` file to add apps to the Pinned section. In your JSON file, you can add more apps to this section using the following keys:
|
||||
|
||||
---
|
||||
| Key | Description |
|
||||
| --- | --- |
|
||||
| packagedAppID | Use this option for Universal Windows Platform apps. To pin a UWP app, use the app's AUMID.|
|
||||
| desktopAppID | Use this option for unpackaged Win32 apps. To pin a Win32 app, use the app's AUMID. If the app doesn't have an AUMID, then enter the `desktopAppLink` instead. |
|
||||
| desktopAppLink | Use this option for unpackaged Win32 apps that don't have an associated AUMID. To pin this type of app, use the path to the `.lnk` shortcut that points to the app. |
|
||||
|
||||
## Use MDM to create and deploy a pinned list policy
|
||||
|
||||
Now that you have the JSON syntax, you're ready to deploy your customized Start layout to devices in your organization.
|
||||
|
||||
MDM providers can deploy policies to devices managed by the organization, including organization-owned devices, and personal or bring your own device (BYOD). Using an MDM provider, such as Microsoft Intune, you can deploy a policy that configures the pinned list.
|
||||
|
||||
This section shows you how to create a pinned list policy in Intune. There isn't a Group Policy to create a pinned list.
|
||||
|
||||
### Create a pinned list using an Intune policy
|
||||
|
||||
To deploy this policy, the devices must be enrolled, and managed by your organization. For more information, see [What is device enrollment?](/mem/intune/enrollment/device-enrollment).
|
||||
|
||||
1. Sign in to the [Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
2. Select **Devices** > **Configuration profiles** > **Create profile**.
|
||||
3. Enter the following properties:
|
||||
|
||||
- **Platform**: Select **Windows 10 and later**.
|
||||
- **Profile**: Select **Templates** > **Custom**.
|
||||
|
||||
4. Select **Create**.
|
||||
5. In **Basics**, enter the following properties:
|
||||
|
||||
- **Name**: Enter a descriptive name for the profile. Name your profiles so you can easily identify them later. For example, a good profile name is **Win11: Custom Start layout**.
|
||||
- **Description**: Enter a description for the profile. This setting is optional, and recommended.
|
||||
|
||||
6. Select **Next**.
|
||||
7. In **Configuration settings** > **OMA-URI**, select **Add**. Add the following properties:
|
||||
|
||||
- **Name**: Enter something like **Configure Start pins**.
|
||||
- **Description**: Enter a description for the row. This setting is optional, and recommended.
|
||||
- **OMA-URI**: Enter `./Vendor/MSFT/Policy/Config/Start/ConfigureStartPins`.
|
||||
- **Data type**: Select **String**.
|
||||
- **Value**: Paste the JSON you created or updated in the previous section. For example, enter the following text:
|
||||
|
||||
```json
|
||||
{
|
||||
|
||||
"pinnedList": [
|
||||
|
||||
{ "desktopAppId": "MSEdge" },
|
||||
|
||||
{ "desktopAppId": "Microsoft.Office.WINWORD.EXE.15" },
|
||||
|
||||
{ "packagedAppId": "Microsoft.WindowsStore_8wekyb3d8bbwe!App" },
|
||||
|
||||
{ "packagedAppId": "Microsoft.WindowsNotepad_8wekyb3d8bbwe!App" }
|
||||
|
||||
]
|
||||
|
||||
}
|
||||
|
||||
```
|
||||
|
||||
Your settings look similar to the following settings:
|
||||
|
||||
:::image type="content" source="./images/customize-start-menu-layout-windows-11/endpoint-manager-admin-center-custom-oma-uri-start-layout.png" alt-text="Custom OMA-URI settings to customize Start menu layout using pinnedList":::
|
||||
|
||||
8. Select **Save** > **Next** to save your changes.
|
||||
9. Configure the rest of the policy settings. For more specific information, see [Create a profile with custom settings](/mem/intune/configuration/custom-settings-configure).
|
||||
|
||||
The Windows OS exposes many CSPs that apply to the Start menu. For a list, see [Supported CSP policies for Windows 11 Start menu](supported-csp-start-menu-layout-windows.md).
|
||||
|
||||
### Deploy the policy using Intune
|
||||
|
||||
When the policy is created, you can deploy it now, or deploy it later. Since this policy is a customized Start layout, the policy can be deployed anytime, including before users sign in the first time.
|
||||
|
||||
For more information and guidance on assigning policies to devices in your organization, see [Assign user and device profiles](/mem/intune/configuration/device-profile-assign).
|
||||
@ -0,0 +1,126 @@
|
||||
---
|
||||
title: Customize Windows 10 Start and taskbar with group policy
|
||||
description: In Windows 10, you can use a Group Policy Object (GPO) to deploy a customized Start layout to users in a domain.
|
||||
ms.date: 12/31/2017
|
||||
---
|
||||
|
||||
# Customize Windows 10 Start and taskbar with Group Policy
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
>**Looking for consumer information?** See [Customize the Start menu](https://go.microsoft.com/fwlink/p/?LinkId=623630)
|
||||
|
||||
In Windows 10 Pro, Enterprise, and Education, you can use a Group Policy Object (GPO) to deploy a customized Start and taskbar layout to users in a domain. No reimaging is required, and the layout can be updated simply by overwriting the .xml file that contains the layout. This enables you to customize Start and taskbar layouts for different departments or organizations, with minimal management overhead.
|
||||
|
||||
This topic describes how to update Group Policy settings to display a customized Start and taskbar layout when the users sign in. By creating a domain-based GPO with these settings, you can deploy a customized Start and taskbar layout to users in a domain.
|
||||
|
||||
>[!WARNING]
|
||||
>When a full Start layout is applied with this method, the users cannot pin, unpin, or uninstall apps from Start. Users can view and open all apps in the **All Apps** view, but they cannot pin any apps to Start. When a partial Start layout is applied, the contents of the specified tile groups cannot be changed, but users can move those groups, and can also create and customize their own groups. When you apply a taskbar layout, users will still be able to pin and unpin apps, and change the order of pinned apps.
|
||||
|
||||
|
||||
|
||||
**Before you begin**: [Customize and export Start layout](customize-and-export-start-layout.md)
|
||||
|
||||
## Operating system requirements
|
||||
|
||||
|
||||
In Windows 10, version 1607, Start and taskbar layout control using Group Policy is supported in Windows 10 Enterprise and Windows 10 Education. In Windows 10, version 1703, Start and taskbar layout control using Group Policy is also supported in Windows 10 Pro.
|
||||
|
||||
The GPO can be configured from any computer on which the necessary ADMX and ADML files (StartMenu.admx and StartMenu.adml) for Windows 10 are installed. In Group Policy, ADMX files are used to define Registry-based policy settings in the Administrative Templates category. To find out how to create a central store for Administrative Templates files, see [article 929841, written for Windows Vista and still applicable](/troubleshoot/windows-server/group-policy/create-central-store-domain-controller) in the Microsoft Knowledge Base.
|
||||
|
||||
## <a href="" id="bkmk-howstartscreencontrolworks"></a>How Start layout control works
|
||||
|
||||
|
||||
Three features enable Start and taskbar layout control:
|
||||
|
||||
- The [Export-StartLayout](/powershell/module/startlayout/export-startlayout) cmdlet in Windows PowerShell exports a description of the current Start layout in .xml file format.
|
||||
|
||||
>[!NOTE]
|
||||
>To import the layout of Start to a mounted Windows image, use the [Import-StartLayout](/powershell/module/startlayout/import-startlayout) cmdlet.
|
||||
|
||||
- [You can modify the Start .xml file](configure-windows-10-taskbar.md) to include `<CustomTaskbarLayoutCollection>` or create an .xml file just for the taskbar configuration.
|
||||
|
||||
- In Group Policy, you use the **Start Layout** settings for the **Start Menu and Taskbar** administrative template to set a Start and taskbar layout from an .xml file when the policy is applied. The Group Policy object doesn't support an empty tile layout, so the default tile layout for Windows is loaded in that case.
|
||||
|
||||
>[!NOTE]
|
||||
>To learn how customize Start to include your line-of-business apps when you deploy Windows 10, see [Customize the Windows 10 Start layout]( https://go.microsoft.com/fwlink/p/?LinkId=620863).
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-domaingpodeployment"></a>Use Group Policy to apply a customized Start layout in a domain
|
||||
|
||||
|
||||
To apply the Start and taskbar layout to users in a domain, use the Group Policy Management Console (GPMC) to configure a domain-based Group Policy Object (GPO) that sets **Start Layout** policy settings in the **Start Menu and Taskbar** administrative template for users in a domain.
|
||||
|
||||
The GPO applies the Start and taskbar layout at the next user sign-in. Each time the user signs in, the timestamp of the .xml file with the Start and taskbar layout is checked and if a newer version of the file is available, the settings in the latest version of the file are applied.
|
||||
|
||||
The GPO can be configured from any computer on which the necessary ADMX and ADML files (StartMenu.admx and StartMenu.adml) for Windows 10 are installed.
|
||||
|
||||
The .xml file with the Start and taskbar layout must be located on shared network storage that is available to the users' computers when they sign in and the users must have Read-only access to the file. If the file is not available when the first user signs in, Start and the taskbar are not customized during the session, but the user will be prevented from making changes to Start. On subsequent sign-ins, if the file is available at sign-in, the layout it contains will be applied to the user's Start and taskbar.
|
||||
|
||||
For information about deploying GPOs in a domain, see [Working with Group Policy Objects](/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc731212(v=ws.11)).
|
||||
|
||||
## <a href="" id="bkmk-localgpimport"></a>Use Group Policy to apply a customized Start layout on the local computer
|
||||
|
||||
|
||||
You can use the Local Group Policy Editor to provide a customized Start and taskbar layout for any user who signs in on the local computer. To display the customized Start and taskbar layout for any user who signs in, configure **Start Layout** policy settings for the **Start Menu and Taskbar** administrative template. You can use the **Start Menu and Taskbar** administrative template in **User Configuration** or **Computer Configuration**.
|
||||
|
||||
>[!NOTE]
|
||||
>This procedure applies the policy settings on the local computer only. For information about deploying the Start and taskbar layout to users in a domain, see [Use Group Policy to deploy a customized Start layout in a domain](#bkmk-domaingpodeployment).
|
||||
>
|
||||
>This procedure creates a Local Group Policy that applies to all users on the computer. To configure Local Group Policy that applies to a specific user or group on the computer, see [Step-by-Step Guide to Managing Multiple Local Group Policy Objects](/previous-versions/windows/it-pro/windows-vista/cc766291(v=ws.10)). The guide was written for Windows Vista and the procedures still apply to Windows 10.
|
||||
|
||||
|
||||
This procedure adds the customized Start and taskbar layout to the user configuration, which overrides any Start layout settings in the local computer configuration when a user signs in on the computer.
|
||||
|
||||
**To configure Start Layout policy settings in Local Group Policy Editor**
|
||||
|
||||
1. On the test computer, press the Windows key, type **gpedit**, and then select **Edit group policy (Control panel)**.
|
||||
|
||||
2. Go to **User Configuration** or **Computer Configuration** > **Administrative Templates** >**Start Menu and Taskbar**.
|
||||
|
||||
|
||||
|
||||
3. Right-click **Start Layout** in the right pane, and click **Edit**.
|
||||
|
||||
This opens the **Start Layout** policy settings.
|
||||
|
||||
|
||||
|
||||
4. Enter the following settings, and then click **OK**:
|
||||
|
||||
1. Select **Enabled**.
|
||||
|
||||
2. Under **Options**, specify the path to the .xml file that contains the Start and taskbar layout. For example, type **C:\\Users\\Test01\\StartScreenMarketing.xml**.
|
||||
|
||||
3. Optionally, enter a comment to identify the Start and taskbar layout.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you disable Start Layout policy settings that have been in effect and then re-enable the policy, users will not be able to make changes to Start, however the layout in the .xml file will not be reapplied unless the file has been updated. In Windows PowerShell, you can update the timestamp on a file by running the following command:
|
||||
>
|
||||
|
||||
> `(ls <path>).LastWriteTime = Get-Date`
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-updatestartscreenlayout"></a>Update a customized Start layout
|
||||
|
||||
|
||||
After you use Group Policy to apply a customized Start and taskbar layout on a computer or in a domain, you can update the layout simply by replacing the .xml file that is specified in the Start Layout policy settings with a file with a newer timestamp.
|
||||
|
||||
## Related topics
|
||||
|
||||
|
||||
- [Manage Windows 10 Start and taskbar layout](windows-10-start-layout-options-and-policies.md)
|
||||
- [Configure Windows 10 taskbar](configure-windows-10-taskbar.md)
|
||||
- [Customize and export Start layout](customize-and-export-start-layout.md)
|
||||
- [Add image for secondary tiles](start-secondary-tiles.md)
|
||||
- [Start layout XML for desktop editions of Windows 10 (reference)](start-layout-xml-desktop.md)
|
||||
- [Customize Windows 10 Start and taskbar with provisioning packages](customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md)
|
||||
- [Customize Windows 10 Start and taskbar with mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md)
|
||||
- [Changes to Start policies in Windows 10](changes-to-start-policies-in-windows-10.md)
|
||||
|
||||
|
||||
@ -0,0 +1,91 @@
|
||||
---
|
||||
title: Change the Windows 10 Start and taskbar using mobile device management | Microsoft Docs
|
||||
description: In Windows 10, you can use a mobile device management (MDM) policy to deploy a customized Start and taskbar layout to users. For example, use Microsoft Intune to configure the start menu layout and taskbar, and deploy the policy to your devices.
|
||||
ms.topic: article
|
||||
|
||||
ms.date: 08/05/2021
|
||||
---
|
||||
|
||||
# Customize Windows 10 Start and taskbar with mobile device management (MDM)
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
|
||||
>**Looking for consumer information?** [Customize the Start menu](https://go.microsoft.com/fwlink/p/?LinkId=623630)
|
||||
|
||||
In Windows 10 Pro, Windows 10 Enterprise, and Windows 10 Education, you can use a mobile device management (MDM) policy to deploy a customized Start and taskbar layout to users. No reimaging is required. The layout can be updated simply by overwriting the `.xml` file that contains the layout. This feature enables you to customize Start layouts for different departments or organizations, with minimal management overhead.
|
||||
|
||||
>[!NOTE]
|
||||
>Support for applying a customized taskbar using MDM is added in Windows 10, version 1703.
|
||||
|
||||
**Before you begin**: [Customize and export Start layout](customize-and-export-start-layout.md) for desktop editions (also works for taskbar customization).
|
||||
|
||||
>[!WARNING]
|
||||
>When a full Start layout is applied with this method, the users cannot pin, unpin, or uninstall apps from Start. Users can view and open all apps in the **All Apps** view, but they cannot pin any apps to Start. When a partial Start layout is applied, the contents of the specified tile groups cannot be changed, but users can move those groups, and can also create and customize their own groups.
|
||||
|
||||
|
||||
|
||||
## <a href="" id="bkmk-howstartscreencontrolworks"></a>How Start layout control works
|
||||
|
||||
|
||||
Two features enable Start layout control:
|
||||
|
||||
- The **Export-StartLayout** cmdlet in Windows PowerShell exports a description of the current Start layout in .xml file format.
|
||||
|
||||
>[!NOTE]
|
||||
>To import the layout of Start to a mounted Windows image, use the [Import-StartLayout](/powershell/module/startlayout/import-startlayout) cmdlet.
|
||||
|
||||
|
||||
|
||||
- In Microsoft Intune, you select the Start layout XML file and add it to a device configuration profile.
|
||||
|
||||
>[!NOTE]
|
||||
>Please do not include XML Prologs like \<?xml version="1.0" encoding="utf-8"?\> in the Start layout XML file. The settings may not be reflected correctly.
|
||||
|
||||
## <a href="" id="bkmk-domaingpodeployment"></a>Create a policy for your customized Start layout
|
||||
|
||||
The following example uses Microsoft Intune to configure an MDM policy that applies a customized Start layout:
|
||||
|
||||
1. Sign in to the [Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
|
||||
2. Select **Devices** > **Configuration profiles** > **Create profile**.
|
||||
|
||||
3. Enter the following properties:
|
||||
|
||||
- **Platform**: Select **Windows 10 and later**.
|
||||
- **Profile type**: Select **Templates** > **Device restrictions** > **Create**.
|
||||
|
||||
4. In **Basics**, enter the following properties:
|
||||
|
||||
- **Name**: Enter a descriptive name for the profile. Name your profiles so you can easily identify it later. For example, a good profile name is **Customize Start menu and taskbar**.
|
||||
- **Description**: Enter a description for the profile. This setting is optional, but recommended.
|
||||
|
||||
5. Select **Next**.
|
||||
|
||||
6. In **Configuration settings**, select **Start**:
|
||||
|
||||
- If you're using an XML file, select **Start menu layout**. Browse to and select your Start layout XML file.
|
||||
- If you don't have an XML file, configure the others settings. For more information on these settings, see [Start settings in Microsoft Intune](/mem/intune/configuration/device-restrictions-windows-10#start).
|
||||
|
||||
7. Select **Next**.
|
||||
8. In **Scope tags**, select **Next**. For more information about scope tags, see [Use RBAC and scope tags for distributed IT](/mem/intune/fundamentals/scope-tags).
|
||||
9. In **Assignments**, select the user or groups that will receive your profile. Select **Next**. For more information on assigning profiles, see [Assign user and device profiles](/mem/intune/configuration/device-profile-assign).
|
||||
10. In **Review + create**, review your settings. When you select **Create**, your changes are saved, and the profile is assigned. The policy is also shown in the profiles list.
|
||||
|
||||
> [!NOTE]
|
||||
> For third party partner MDM solutions, you may need to use an OMA-URI setting for Start layout, based on the [Policy configuration service provider (CSP)](/windows/client-management/mdm/policy-configuration-service-provider). The OMA-URI setting is `./User/Vendor/MSFT/Policy/Config/Start/StartLayout`.
|
||||
|
||||
|
||||
## Next steps
|
||||
|
||||
- [Manage Windows 10 Start and taskbar layout](windows-10-start-layout-options-and-policies.md)
|
||||
- [Configure Windows 10 taskbar](configure-windows-10-taskbar.md)
|
||||
- [Customize and export Start layout](customize-and-export-start-layout.md)
|
||||
- [Add image for secondary tiles](start-secondary-tiles.md)
|
||||
- [Start layout XML for desktop editions of Windows 10 (reference)](start-layout-xml-desktop.md)
|
||||
- [Customize Windows 10 Start and taskbar with Group Policy](customize-windows-10-start-screens-by-using-group-policy.md)
|
||||
- [Customize Windows 10 Start and taskbar with provisioning packages](customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md)
|
||||
- [Changes to Start policies in Windows 10](changes-to-start-policies-in-windows-10.md)
|
||||
@ -0,0 +1,134 @@
|
||||
---
|
||||
title: Customize Windows 10 Start and taskbar with provisioning packages
|
||||
description: In Windows 10, you can use a provisioning package to deploy a customized Start layout to users.
|
||||
ms.topic: article
|
||||
|
||||
ms.date: 12/31/2017
|
||||
---
|
||||
|
||||
# Customize Windows 10 Start and taskbar with provisioning packages
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
> **Looking for consumer information?** [Customize the Start menu](https://go.microsoft.com/fwlink/p/?LinkId=623630)
|
||||
|
||||
> [!NOTE]
|
||||
> Currently, using provisioning packages to customize the Start menu layout is supported on Windows 10. It's not supported on Windows 11.
|
||||
|
||||
In Windows 10 Pro, Windows 10 Enterprise, and Windows 10 Education, version 1703, you can use a provisioning package that you create with Windows Configuration Designer to deploy a customized Start and taskbar layout to users. No reimaging is required, and the Start and taskbar layout can be updated simply by overwriting the .xml file that contains the layout. The provisioning package can be applied to a running device. This enables you to customize Start and taskbar layouts for different departments or organizations, with minimal management overhead.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> If you use a provisioning package to configure the taskbar, your configuration will be reapplied each time the explorer.exe process restarts. If your configuration pins an app and the user unpins that app, the user's change will be overwritten the next time the configuration is applied. To apply a taskbar configuration and allow users to make changes that will persist, apply your configuration by using Group Policy.
|
||||
|
||||
**Before you begin**: [Customize and export Start layout](customize-and-export-start-layout.md) for desktop editions.
|
||||
|
||||
## <a href="" id="bkmk-howstartscreencontrolworks"></a>How Start layout control works
|
||||
|
||||
|
||||
Three features enable Start and taskbar layout control:
|
||||
|
||||
- The **Export-StartLayout** cmdlet in Windows PowerShell exports a description of the current Start layout in .xml file format.
|
||||
|
||||
> [!NOTE]
|
||||
> To import the layout of Start to a mounted Windows image, use the [Import-StartLayout](/powershell/module/startlayout/import-startlayout) cmdlet.
|
||||
|
||||
- [You can modify the Start .xml file](configure-windows-10-taskbar.md) to include `<CustomTaskbarLayoutCollection>` or create an .xml file just for the taskbar configuration.
|
||||
|
||||
- In Windows Configuration Designer, you use the **Policies/Start/StartLayout** setting to provide the contents of the .xml file that defines the Start and taskbar layout.
|
||||
|
||||
<span id="escape"/>
|
||||
|
||||
## <a href="" id="escape"></a>Prepare the Start layout XML file
|
||||
|
||||
The **Export-StartLayout** cmdlet produces an XML file. Because Windows Configuration Designer produces a customizations.xml file that contains the configuration settings, adding the Start layout section to the customizations.xml file directly would result in an XML file embedded in an XML file. Before you add the Start layout section to the customizations.xml file, you must replace the markup characters in your layout.xml with escape characters.
|
||||
|
||||
|
||||
1. Copy the contents of layout.xml into an online tool that escapes characters.
|
||||
|
||||
3. During the procedure to create a provisioning package, you will copy the text with the escape characters and paste it in the customizations.xml file for your project.
|
||||
|
||||
## <a href="" id="bkmk-domaingpodeployment"></a>Create a provisioning package that contains a customized Start layout
|
||||
|
||||
|
||||
Use the Windows Configuration Designer tool to create a provisioning package. [Learn how to install Windows Configuration Designer.](provisioning-packages/provisioning-install-icd.md)
|
||||
|
||||
> [!IMPORTANT]
|
||||
> When you build a provisioning package, you may include sensitive information in the project files and in the provisioning package (.ppkg) file. Although you have the option to encrypt the .ppkg file, project files are not encrypted. You should store the project files in a secure location and delete the project files when they are no longer needed.
|
||||
|
||||
1. Open Windows Configuration Designer (by default, %systemdrive%\\Program Files (x86)\\Windows Kits\\10\\Assessment and Deployment Kit\\Imaging and Configuration Designer\\x86\\ICD.exe).
|
||||
|
||||
2. Choose **Advanced provisioning**.
|
||||
|
||||
3. Name your project, and click **Next**.
|
||||
|
||||
4. Choose **All Windows desktop editions** and click **Next**.
|
||||
|
||||
5. On **New project**, click **Finish**. The workspace for your package opens.
|
||||
|
||||
6. Expand **Runtime settings** > **Policies** > **Start**, and click **StartLayout**.
|
||||
|
||||
> [!TIP]
|
||||
> If **Start** is not listed, check the type of settings you selected in step 4. You must create the project using settings for **All Windows desktop editions**.
|
||||
|
||||
7. Enter **layout.xml**. This value creates a placeholder in the customizations.xml file that you will replace with the contents of the layout.xml file in a later step.
|
||||
|
||||
7. Save your project and close Windows Configuration Designer.
|
||||
|
||||
7. In File Explorer, open the project's directory. (The default location is C:\Users\\*user name*\Documents\Windows Imaging and Configuration Designer (WICD)\\*project name*)
|
||||
|
||||
7. Open the customizations.xml file in a text editor. The **<Customizations>** section will look like this:
|
||||
|
||||
|
||||
|
||||
7. Replace **layout.xml** with the text from the layout.xml file, [with markup characters replaced with escape characters](#escape).
|
||||
|
||||
8. Save and close the customizations.xml file.
|
||||
|
||||
8. Open Windows Configuration Designer and open your project.
|
||||
|
||||
8. On the **File** menu, select **Save.**
|
||||
|
||||
9. On the **Export** menu, select **Provisioning package**.
|
||||
|
||||
10. Change **Owner** to **IT Admin**, which will set the precedence of this provisioning package higher than provisioning packages applied to this device from other sources, and then select **Next.**
|
||||
|
||||
11. Optional. In the **Provisioning package security** window, you can choose to encrypt the package and enable package signing.
|
||||
|
||||
- **Enable package encryption** - If you select this option, an auto-generated password will be shown on the screen.
|
||||
|
||||
- **Enable package signing** - If you select this option, you must select a valid certificate to use for signing the package. You can specify the certificate by clicking **Browse** and choosing the certificate you want to use to sign the package.
|
||||
|
||||
12. Click **Next** to specify the output location where you want the provisioning package to go when it's built. By default, Windows Imaging and Configuration Designer (ICD) uses the project folder as the output location.
|
||||
|
||||
Optionally, you can click **Browse** to change the default output location.
|
||||
|
||||
13. Click **Next**.
|
||||
|
||||
14. Click **Build** to start building the package. The provisioning package doesn't take long to build. The project information is displayed in the build page and the progress bar indicates the build status.
|
||||
|
||||
If you need to cancel the build, click **Cancel**. This cancels the current build process, closes the wizard, and takes you back to the **Customizations Page**.
|
||||
|
||||
15. If your build fails, an error message will show up that includes a link to the project folder. You can scan the logs to determine what caused the error. Once you fix the issue, try building the package again.
|
||||
|
||||
If your build is successful, the name of the provisioning package, output directory, and project directory will be shown.
|
||||
|
||||
- If you choose, you can build the provisioning package again and pick a different path for the output package. To do this, click **Back** to change the output package name and path, and then click **Next** to start another build.
|
||||
- If you are done, click **Finish** to close the wizard and go back to the **Customizations Page**.
|
||||
|
||||
16. Copy the provisioning package to the target device.
|
||||
|
||||
17. Double-click the ppkg file and allow it to install.
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Manage Windows 10 Start and taskbar layout](windows-10-start-layout-options-and-policies.md)
|
||||
- [Configure Windows 10 taskbar](configure-windows-10-taskbar.md)
|
||||
- [Customize and export Start layout](customize-and-export-start-layout.md)
|
||||
- [Add image for secondary tiles](start-secondary-tiles.md)
|
||||
- [Start layout XML for desktop editions of Windows 10 (reference)](start-layout-xml-desktop.md)
|
||||
- [Customize Windows 10 Start and taskbar with Group Policy](customize-windows-10-start-screens-by-using-group-policy.md)
|
||||
- [Customize Windows 10 Start and taskbar with mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md)
|
||||
- [Changes to Start policies in Windows 10](changes-to-start-policies-in-windows-10.md)
|
||||
Binary file not shown.
|
After Width: | Height: | Size: 41 KiB |
BIN
windows/configuration/start/images/start-layout-group-policy.png
Normal file
BIN
windows/configuration/start/images/start-layout-group-policy.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 169 KiB |
BIN
windows/configuration/start/images/start-menu-layout.png
Normal file
BIN
windows/configuration/start/images/start-menu-layout.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 121 KiB |
554
windows/configuration/start/start-layout-xml-desktop.md
Normal file
554
windows/configuration/start/start-layout-xml-desktop.md
Normal file
@ -0,0 +1,554 @@
|
||||
---
|
||||
title: Start layout XML for desktop editions of Windows 10
|
||||
description: This article describes the options for customizing Start layout in LayoutModification.xml for Windows 10 desktop editions.
|
||||
ms.topic: article
|
||||
ms.date: 10/02/2018
|
||||
|
||||
---
|
||||
|
||||
# Start layout XML for desktop editions of Windows 10 (reference)
|
||||
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
>**Looking for consumer information?** See [Customize the Start menu](https://go.microsoft.com/fwlink/p/?LinkId=623630)
|
||||
|
||||
On Windows 10 for desktop editions, the customized Start works by:
|
||||
|
||||
- Windows 10 checks the chosen base default layout, such as the desktop edition and whether Cortana is supported for the country/region.
|
||||
|
||||
- Windows 10 reads the LayoutModification.xml file and allows groups to be appended to Start. The groups have the following constraints:
|
||||
- Two groups that are six columns wide, or equivalent to the width of three medium tiles.
|
||||
- Two medium-sized tile rows in height. Windows 10 ignores any tiles that are pinned beyond the second row.
|
||||
|
||||
- No limit to the number of apps that can be pinned. There's a theoretical limit of 24 tiles per group (four small tiles per medium square x 3 columns x 2 rows).
|
||||
|
||||
|
||||
|
||||
>[!NOTE]
|
||||
>To use the layout modification XML to configure Start with roaming user profiles, see [Deploying Roaming User Profiles](/windows-server/storage/folder-redirection/deploy-roaming-user-profiles#step-7-optionally-specify-a-start-layout-for-windows-10-pcs).
|
||||
|
||||
|
||||
|
||||
## LayoutModification XML
|
||||
|
||||
IT admins can provision the Start layout using a LayoutModification.xml file. This file supports several mechanisms to modify or replace the default Start layout and its tiles. The easiest method for creating a LayoutModification.xml file is by using the Export-StartLayout cmdlet; see [Customize and export Start layout](customize-and-export-start-layout.md) for instructions.
|
||||
|
||||
### Required order
|
||||
|
||||
The XML schema for `LayoutModification.xml` requires the following order for tags directly under the LayoutModificationTemplate node:
|
||||
|
||||
1. LayoutOptions
|
||||
1. DefaultLayoutOverride
|
||||
1. RequiredStartGroupsCollection
|
||||
1. AppendDownloadOfficeTile –OR– AppendOfficeSuite (only one Office option can be used at a time)
|
||||
1. AppendOfficeSuiteChoice
|
||||
1. TopMFUApps
|
||||
1. CustomTaskbarLayoutCollection
|
||||
1. InkWorkspaceTopApps
|
||||
1. StartLayoutCollection
|
||||
|
||||
Comments are not supported in the `LayoutModification.xml` file.
|
||||
|
||||
|
||||
### Supported elements and attributes
|
||||
|
||||
>[!NOTE]
|
||||
>To make sure the Start layout XML parser processes your file correctly, follow these guidelines when working with your LayoutModification.xml file:
|
||||
>- Do not leave spaces or white lines in between each element.
|
||||
>- Do not add comments inside the StartLayout node or any of its children elements.
|
||||
>- Do not add multiple rows of comments.
|
||||
|
||||
The following table lists the supported elements and attributes for the LayoutModification.xml file.
|
||||
> [!NOTE]
|
||||
> RequiredStartGroupsCollection and AppendGroup syntax only apply when the Import-StartLayout method is used for building and deploying Windows images.
|
||||
|
||||
| Element | Attributes | Description |
|
||||
| --- | --- | --- |
|
||||
| LayoutModificationTemplate | xmlns</br>xmlns:defaultlayout</br>xmlns:start</br>Version | Use to describe the changes to the default Start layout |
|
||||
| [LayoutOptions](#layoutoptions)</br></br>Parent:</br>LayoutModificationTemplate | StartTileGroupsColumnCount</br>FullScreenStart | Use to specify:</br>- Whether to use full screen Start on the desktop</br>- The number of tile columns in the Start menu |
|
||||
| RequiredStartGroupsCollection</br></br>Parent:</br>LayoutModificationTemplate | n/a | Use to contain collection of RequiredStartGroups |
|
||||
| [RequiredStartGroups](#requiredstartgroups)</br></br>Parent:</br>RequiredStartGroupsCollection | Region | Use to contain the AppendGroup tags, which represent groups that can be appended to the default Start layout |
|
||||
| [AppendGroup](#appendgroup)</br></br>Parent:</br>RequiredStartGroups | Name | Use to specify the tiles that need to be appended to the default Start layout |
|
||||
| [start:Tile](#specify-start-tiles)</br></br>Parent:</br>AppendGroup | AppUserModelID</br>Size</br>Row</br>Column | Use to specify any of the following:</br>- A Universal Windows app</br>- A Windows 8 or Windows 8.1 app</br></br>Note that AppUserModelID is case-sensitive. |
|
||||
| start:Folder<br><br>Parent:<br>start:Group | Name (in Windows 10, version 1809 and later only)<br>Size<br>Row<br>Column<br>LocalizedNameResourcetag | Use to specify a folder of icons; can include [Tile](#start-tile), [SecondaryTile](#start-secondarytile), and [DesktopApplicationTile](#start-desktopapplicationtile). |
|
||||
| start:DesktopApplicationTile</br></br>Parent:</br>AppendGroup | DesktopApplicationID</br>DesktopApplicationLinkPath</br>Size</br>Row</br>Column | Use to specify any of the following:</br>- A Windows desktop application with a known AppUserModelID</br>- An application in a known folder with a link in a legacy Start Menu folder</br>- A Windows desktop application link in a legacy Start Menu folder</br>- A Web link tile with an associated `.url` file that is in a legacy Start Menu folder |
|
||||
| start:SecondaryTile</br></br>Parent:</br>AppendGroup | AppUserModelID</br>TileID</br>Arguments</br>DisplayName</br>Square150x150LogoUri</br>ShowNameOnSquare150x150Logo</br>ShowNameOnWide310x150Logo</br>Wide310x150LogoUri</br>BackgroundColor</br>ForegroundText</br>IsSuggestedApp</br>Size</br>Row</br>Column | Use to pin a Web link through a Microsoft Edge secondary tile. Note that AppUserModelID is case-sensitive. |
|
||||
| TopMFUApps</br></br>Parent:</br>LayoutModificationTemplate | n/a | Use to add up to three default apps to the frequently used apps section in the system area.</br></br>**Note**: Only applies to versions of Windows 10 earlier than version 1709. In Windows 10, version 1709, you can no longer pin apps to the Most Frequently Used apps list in Start. |
|
||||
| Tile</br></br>Parent:</br>TopMFUApps | AppUserModelID | Use with the TopMFUApps tags to specify an app with a known AppUserModelID. </br></br>**Note**: Only applies to versions of Windows 10 earlier than version 1709. In Windows 10, version 1709, you can no longer pin apps to the Most Frequently Used apps list in Start. |
|
||||
| DesktopApplicationTile</br></br>Parent:</br>TopMFUApps | LinkFilePath | Use with the TopMFUApps tags to specify an app without a known AppUserModelID.</br></br>**Note**: Only applies to versions of Windows 10 earlier than version 1709. In Windows 10, version 1709, you can no longer pin apps to the Most Frequently Used apps list in Start. |
|
||||
| AppendOfficeSuite</br></br>Parent:</br>LayoutModificationTemplate | n/a | Use to add the in-box installed Office suite to Start. For more information, see [Customize the Office suite of tiles](/windows-hardware/customize/desktop/customize-start-layout#customize-the-office-suite-of-tiles).</br></br>Don't use this tag with AppendDownloadOfficeTile. |
|
||||
| AppendDownloadOfficeTile</br></br>Parent:</br>LayoutModificationTemplate | n/a | Use to add a specific **Download Office** tile to a specific location in Start</br></br>Do not use this tag with AppendOfficeSuite |
|
||||
|
||||
### LayoutOptions
|
||||
|
||||
New devices running Windows 10 for desktop editions will default to a Start menu with two columns of tiles unless boot to tablet mode is enabled. Devices with screens that are under 10" have boot to tablet mode enabled by default. For these devices, users see the full screen Start on the desktop. You can adjust the following features:
|
||||
|
||||
- Boot to tablet mode can be set on or off.
|
||||
|
||||
- Set full screen Start on desktop to on or off.
|
||||
|
||||
To do this, add the LayoutOptions element in your LayoutModification.xml file and set the FullScreenStart attribute to true or false.
|
||||
|
||||
- Specify the number of columns in the Start menu to 1 or 2.
|
||||
|
||||
To do this, add the LayoutOptions element in your LayoutModification.xml file and set the StartTileGroupsColumnCount attribute to 1 or 2.
|
||||
|
||||
The following example shows how to use the LayoutOptions element to specify full screen Start on the desktop and to use one column in the Start menu:
|
||||
|
||||
```XML
|
||||
<LayoutModificationTemplate
|
||||
xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification"
|
||||
xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout"
|
||||
xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout"
|
||||
Version="1">
|
||||
<LayoutOptions
|
||||
StartTileGroupsColumnCount="1"
|
||||
FullScreenStart="true"
|
||||
/>
|
||||
</LayoutModificationTemplate>
|
||||
```
|
||||
|
||||
For devices being upgraded to Windows 10 for desktop editions:
|
||||
|
||||
- Devices being upgraded from Windows 7 will default to a Start menu with one column.
|
||||
- Devices being upgraded from Windows 8.1 or Windows 8.1 Upgrade will default to a Start menu with two columns.
|
||||
|
||||
### RequiredStartGroups
|
||||
|
||||
The **RequiredStartGroups** tag contains **AppendGroup** tags that represent groups that you can append to the default Start layout.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>For Windows 10 for desktop editions, you can add a maximum of two (2) **AppendGroup** tags per **RequiredStartGroups** tag.
|
||||
|
||||
You can also assign regions to the append groups in the **RequiredStartGroups** tag's using the optional **Region** attribute or you can use the multivariant capabilities in Windows provisioning. If you're using the **Region** attribute, you must use a two-letter country code to specify the country/region that the append group(s) apply to. To specify more than one country/region, use a pipe ("|") delimiter as shown in the following example:
|
||||
|
||||
```XML
|
||||
<RequiredStartGroups
|
||||
Region="DE|ES|FR|GB|IT|US">
|
||||
```
|
||||
|
||||
If the country/region setting for the Windows device matches a **RequiredStartGroups**, then the tiles laid out within the **RequiredStartGroups** is applied to Start.
|
||||
|
||||
If you specify a region-agnostic **RequiredStartGroups** (or one without the optional Region attribute), then the region-agnostic **RequiredStartGroups** is applied to Start.
|
||||
|
||||
### AppendGroup
|
||||
|
||||
**AppendGroup** tags specify a group of tiles that will be appended to Start. There is a maximum of two **AppendGroup** tags allowed per **RequiredStartGroups** tag.
|
||||
|
||||
For Windows 10 for desktop editions, AppendGroup tags contain start:Tile, start:DesktopApplicationTile, or start:SecondaryTile tags.
|
||||
|
||||
You can specify any number of tiles in an **AppendGroup**, but you can't specify a tile with a **Row** attribute greater than 4. The Start layout doesn't support overlapping tiles.
|
||||
|
||||
### Specify Start tiles
|
||||
|
||||
To pin tiles to Start, partners must use the right tile depending on what you want to pin.
|
||||
|
||||
#### Tile size and coordinates
|
||||
|
||||
All tile types require a size (**Size**) and coordinates (**Row** and **Column**) attributes regardless of the tile type that you use when prepinning items to Start.
|
||||
|
||||
The following table describes the attributes that you must use to specify the size and location for the tile.
|
||||
|
||||
| Attribute | Description |
|
||||
| --- | --- |
|
||||
| Size | Determines how large the tile will be.</br></br>- 1x1 - small tile</br>- 2x2 - medium tile</br>- 4x2 - wide tile</br>- 4x4 - large tile |
|
||||
| Row | Specifies the row where the tile will appear. |
|
||||
| Column | Specifies the column where the tile will appear. |
|
||||
|
||||
For example, a tile with Size="2x2", Row="2", and Column="2" results in a tile located at (2,2) where (0,0) is the top-left corner of a group.
|
||||
|
||||
<span id="start-tile" />
|
||||
#### start:Tile
|
||||
|
||||
You can use the **start:Tile** tag to pin any of the following apps to Start:
|
||||
|
||||
- A Universal Windows app
|
||||
- A Windows 8 app or Windows 8.1 app
|
||||
|
||||
To specify any one of these apps, you must set the **AppUserModelID** attribute to the application user model ID that's associated with the corresponding app.
|
||||
|
||||
>[!IMPORTANT]
|
||||
>**AppUserModelID** (AUMID) is case-sensitive.
|
||||
|
||||
The following example shows how to pin the Microsoft Edge Universal Windows app:
|
||||
|
||||
```XML
|
||||
<start:Tile
|
||||
AppUserModelID="Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge"
|
||||
Size="2x2"
|
||||
Row="0"
|
||||
Column="0"/>
|
||||
```
|
||||
|
||||
<span id="start-desktopapplicationtile" />
|
||||
#### start:DesktopApplicationTile
|
||||
|
||||
You can use the **start:DesktopApplicationTile** tag to pin a Windows desktop application to Start. There are two ways you can specify a Windows desktop application:
|
||||
|
||||
- Use a path to a shortcut link (.lnk file) to a Windows desktop application.
|
||||
|
||||
>[!NOTE]
|
||||
>In Start layouts for Windows 10, version 1703, you should use **DesktopApplicationID** rather than **DesktopApplicationLinkPath** if you are using Group Policy or MDM to apply the start layout and the application was installed after the user's first sign-in.
|
||||
|
||||
To pin a Windows desktop application through this method, you must first add the .lnk file in the specified location when the device first boots.
|
||||
|
||||
The following example shows how to pin the Command Prompt:
|
||||
|
||||
```XML
|
||||
<start:DesktopApplicationTile
|
||||
DesktopApplicationLinkPath="%appdata%\Microsoft\Windows\Start Menu\Programs\System Tools\Command Prompt.lnk"
|
||||
Size="2x2"
|
||||
Row="0"
|
||||
Column="4"/>
|
||||
```
|
||||
|
||||
|
||||
You must set the **DesktopApplicationLinkPath** attribute to the .lnk file that points to the Windows desktop application. The path also supports environment variables.
|
||||
|
||||
If you are pointing to a third-party Windows desktop application and the layout is being applied before the first boot, you must put the .lnk file in a legacy Start Menu directory before first boot; for example, "%APPDATA%\Microsoft\Windows\Start Menu\Programs\" or the all users profile "%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\".
|
||||
|
||||
- Use the application's application user model ID, if this is known. If the Windows desktop application doesn't have one, use the shortcut link option.
|
||||
|
||||
|
||||
You can use the [Get-StartApps cmdlet](/powershell/module/startlayout/get-startapps) on a PC that has the application pinned to Start to obtain the app ID.
|
||||
|
||||
To pin a Windows desktop application through this method, you must set the **DesktopApplicationID** attribute to the application user model ID that's associated with the corresponding app.
|
||||
|
||||
The following example shows how to pin the File Explorer Windows desktop application:
|
||||
|
||||
```XML
|
||||
<start:DesktopApplicationTile
|
||||
DesktopApplicationID="Microsoft.Windows.Explorer"
|
||||
Size="2x2"
|
||||
Row="0"
|
||||
Column="2"/>
|
||||
```
|
||||
|
||||
|
||||
You can also use the **start:DesktopApplicationTile** tag as one of the methods for pinning a Web link to Start. The other method is to use a Microsoft Edge secondary tile.
|
||||
|
||||
To pin a legacy `.url` shortcut to Start, you must create a `.url` file (right-click on the desktop, select **New** > **Shortcut**, and then type a Web URL). You must add this `.url` file in a legacy Start Menu directory before first boot; for example, `%APPDATA%\Microsoft\Windows\Start Menu\Programs\` or the all users profile `%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\`.
|
||||
|
||||
The following example shows how to create a tile of the Web site's URL, which you can treat similarly to a Windows desktop application tile:
|
||||
|
||||
```XML
|
||||
<start:DesktopApplicationTile
|
||||
DesktopApplicationID="http://www.contoso.com/"
|
||||
Size="2x2"
|
||||
Row="0"
|
||||
Column="2"/>
|
||||
```
|
||||
|
||||
>[!NOTE]
|
||||
>In Windows 10, version 1703, **Export-StartLayout** will use **DesktopApplicationLinkPath** for the .url shortcut. You must change **DesktopApplicationLinkPath** to **DesktopApplicationID** and provide the URL.
|
||||
|
||||
<span id="start-secondarytile" />
|
||||
#### start:SecondaryTile
|
||||
|
||||
You can use the **start:SecondaryTile** tag to pin a Web link through a Microsoft Edge secondary tile. This method doesn't require any additional action compared to the method of using legacy `.url` shortcuts (through the start:DesktopApplicationTile tag).
|
||||
|
||||
The following example shows how to create a tile of the Web site's URL using the Microsoft Edge secondary tile:
|
||||
|
||||
```XML
|
||||
<start:SecondaryTile
|
||||
AppUserModelID="Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge"
|
||||
TileID="MyWeblinkTile"
|
||||
Arguments="http://msn.com"
|
||||
DisplayName="MySite"
|
||||
Square150x150LogoUri="ms-appx:///Assets/MicrosoftEdgeSquare150x150.png"
|
||||
|
||||
Wide310x150LogoUri="ms-appx:///Assets/MicrosoftEdgeWide310x150.png"
|
||||
ShowNameOnSquare150x150Logo="true"
|
||||
ShowNameOnWide310x150Logo="false"
|
||||
BackgroundColor="#FF112233"
|
||||
Size="2x2"
|
||||
Row="0"
|
||||
Column="4"/>
|
||||
```
|
||||
|
||||
The following table describes the other attributes that you can use with the **start:SecondaryTile** tag in addition to **Size**, **Row**, and **Column**.
|
||||
|
||||
| Attribute | Required/optional | Description |
|
||||
| --- | --- | --- |
|
||||
| AppUserModelID | Required | Must point to Microsoft Edge. Note that AppUserModelID is case-sensitive. |
|
||||
| TileID | Required | Must uniquely identify your Web site tile. |
|
||||
| Arguments | Required | Must contain the URL of your Web site. |
|
||||
| DisplayName | Required | Must specify the text that you want users to see. |
|
||||
| Square150x150LogoUri | Required | Specifies the logo to use on the 2x2 tile. |
|
||||
| Wide310x150LogoUri | Optional | Specifies the logo to use on the 4x2 tile. |
|
||||
| ShowNameOnSquare150x150Logo | Optional | Specifies whether the display name is shown on the 2x2 tile. The values you can use for this attribute are true or false. |
|
||||
| ShowNameOnWide310x150Logo | Optional | Specifies whether the display name is shown on the 4x2 tile. The values you can use for this attribute are true or false. |
|
||||
| BackgroundColor | Optional | Specifies the color of the tile. You can specify the value in ARGB hexadecimal (for example, #FF112233) or specify "transparent". |
|
||||
| ForegroundText | Optional | Specifies the color of the foreground text. Set the value to either "light" or "dark". |
|
||||
|
||||
Secondary Microsoft Edge tiles have the same size and location behavior as a Universal Windows app, Windows 8 app, or Windows 8.1 app.
|
||||
|
||||
#### TopMFUApps
|
||||
|
||||
>[!NOTE]
|
||||
>Only applies to versions of Windows 10 earlier than version 1709. In Windows 10, version 1709, you can no longer pin apps to the Most Frequently Used apps list in Start.
|
||||
|
||||
You can use the **TopMFUApps** tag to add up to 3 default apps to the frequently used apps section in the system area, which delivers system-driven lists to the user including important or frequently accessed system locations and recently installed apps.
|
||||
|
||||
You can use this tag to add:
|
||||
|
||||
- Apps with an **AppUserModelID** attribute - This includes Windows desktop applications that have a known application user model ID. Use a **Tile** tag with the **AppUserModelID** attribute set to the app's application user model ID.
|
||||
- Apps without a **AppUserModelID** attribute - For these apps, you must create a .lnk file that points to the installed app and place the .lnk file in the `%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs` directory. Use a **DesktopApplicationTile** tag with the **LinkFilePath** attribute set to the .lnk file name and path.
|
||||
|
||||
The following example shows how to modify your LayoutModification.xml file to add both kinds of apps to the system area in Start:
|
||||
|
||||
```XML
|
||||
<LayoutModificationTemplate
|
||||
xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification"
|
||||
xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout"
|
||||
xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout"
|
||||
Version="1">
|
||||
<TopMFUApps>
|
||||
<Tile AppUserModelID="Microsoft.WindowsCalculator_8wekyb3d8bbwe!App" />
|
||||
<Tile AppUserModelID="Microsoft.Getstarted_8wekyb3d8bbwe!App" />
|
||||
<DesktopApplicationTile LinkFilePath="%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\Win32App.lnk" />
|
||||
</TopMFUApps>
|
||||
</LayoutModificationTemplate>
|
||||
```
|
||||
|
||||
#### AppendOfficeSuite
|
||||
|
||||
You can use the **AppendOfficeSuite** tag to add the in-box installed Office suite of apps to Start.
|
||||
|
||||
>[!NOTE]
|
||||
>The OEM must have installed Office for this tag to work.
|
||||
|
||||
The following example shows how to add the **AppendOfficeSuite** tag to your LayoutModification.xml file to append the full Universal Office suite to Start:
|
||||
|
||||
```XML
|
||||
<LayoutModificationTemplate
|
||||
xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification"
|
||||
xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout"
|
||||
xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout"
|
||||
Version="1">
|
||||
<AppendOfficeSuite/>
|
||||
</LayoutModificationTemplate>
|
||||
```
|
||||
|
||||
#### AppendOfficeSuiteChoice
|
||||
|
||||
This tag is added in Windows 10, version 1803. You have two options in this tag:
|
||||
|
||||
- `<AppendOfficeSuiteChoice Choice="DesktopBridgeSubscription"/>`
|
||||
- `<AppendOfficeSuiteChoice Choice="DesktopBridge"/>`
|
||||
|
||||
Use `Choice=DesktopBridgeSubscription` on devices running Windows 10, version 1803, that have Office 365 preinstalled. This will set the heading of the Office suite of tiles to **Office 365**, to highlight the Office 365 apps that you've made available on the device.
|
||||
|
||||
Use `Choice=DesktopBridge` on devices running versions of Windows 10 earlier than version 1803, and on devices shipping with [perpetual licenses for Office](/archive/blogs/ausoemteam/choosing-the-right-office-version-for-your-customers). This will set the heading of the Office suite of tiles to **Create**.
|
||||
|
||||
For more information, see [Customize the Office suite of tiles](/windows-hardware/customize/desktop/customize-start-layout#customize-the-office-suite-of-tiles).
|
||||
|
||||
|
||||
#### AppendDownloadOfficeTile
|
||||
|
||||
You can use the **AppendDownloadOfficeTile** tag to append the Office trial installer to Start. This tag adds the **Download Office** tile to Start and the download tile will appear at the bottom right-hand side of the second group.
|
||||
|
||||
>[!NOTE]
|
||||
>The OEM must have installed the Office trial installer for this tag to work.
|
||||
|
||||
The following example shows how to add the **AppendDownloadOfficeTile** tag to your LayoutModification.xml file:
|
||||
|
||||
```XML
|
||||
<LayoutModificationTemplate
|
||||
xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification"
|
||||
xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout"
|
||||
xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout"
|
||||
Version="1">
|
||||
<AppendDownloadOfficeTile/>
|
||||
</LayoutModificationTemplate>
|
||||
```
|
||||
|
||||
## Sample LayoutModification.xml
|
||||
|
||||
The following sample LayoutModification.xml shows how you can configure the Start layout for devices running Windows 10 for desktop editions:
|
||||
|
||||
```XML
|
||||
<LayoutModificationTemplate
|
||||
xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification"
|
||||
xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout"
|
||||
xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout"
|
||||
Version="1">
|
||||
<RequiredStartGroupsCollection>
|
||||
<RequiredStartGroups
|
||||
Region="DE|ES|FR|GB|IT|US">
|
||||
<AppendGroup
|
||||
Name="Fabrikam Group 1">
|
||||
<start:Tile
|
||||
AppUserModelID="Microsoft.Office.Word_8wekyb3d8bbwe!microsoft.word"
|
||||
Size="2x2"
|
||||
Row="0"
|
||||
Column="0"/>
|
||||
<start:DesktopApplicationTile
|
||||
DesktopApplicationID="Microsoft.Windows.Explorer"
|
||||
Size="2x2"
|
||||
Row="0"
|
||||
Column="2"/>
|
||||
<start:Tile
|
||||
AppUserModelID="Microsoft.Office.Excel_8wekyb3d8bbwe!microsoft.excel"
|
||||
Size="2x2"
|
||||
Row="0"
|
||||
Column="4"/>
|
||||
</AppendGroup>
|
||||
|
||||
<AppendGroup
|
||||
Name="Fabrikam Group 2">
|
||||
<start:Tile
|
||||
AppUserModelID="Microsoft.Reader_8wekyb3d8bbwe!Microsoft.Reader"
|
||||
Size="2x2"
|
||||
Row="0"
|
||||
Column="0"/>
|
||||
<start:DesktopApplicationTile
|
||||
DesktopApplicationID="http://www.bing.com/"
|
||||
Size="2x2"
|
||||
Row="0"
|
||||
Column="2"/>
|
||||
<start:DesktopApplicationTile
|
||||
DesktopApplicationLinkPath="%ALLUSERSPROFILE%\Microsoft\Windows\Start Menu\Programs\Accessories\Paint.lnk"
|
||||
Size="2x2"
|
||||
Row="0"
|
||||
Column="4"/>
|
||||
</AppendGroup>
|
||||
</RequiredStartGroups>
|
||||
<RequiredStartGroups>
|
||||
<AppendGroup
|
||||
Name="Fabrikam Group 1">
|
||||
<start:Tile
|
||||
AppUserModelID="Microsoft.Office.Word_8wekyb3d8bbwe!microsoft.word"
|
||||
Size="2x2"
|
||||
Row="0"
|
||||
Column="0"/>
|
||||
<start:SecondaryTile
|
||||
AppUserModelID="Microsoft.MicrosoftEdge_8wekyb3d8bbwe!MicrosoftEdge"
|
||||
TileID="FabrikamWeblinkTile"
|
||||
Arguments="http://www.fabrikam.com"
|
||||
DisplayName="Fabrikam"
|
||||
Square150x150LogoUri="ms-appx:///Assets/MicrosoftEdgeSquare150x150.png"
|
||||
ShowNameOnSquare150x150Logo="true"
|
||||
BackgroundColor="#FF112233"
|
||||
Size="2x2"
|
||||
Row="0"
|
||||
Column="2"/>
|
||||
</AppendGroup>
|
||||
|
||||
</RequiredStartGroups>
|
||||
</RequiredStartGroupsCollection>
|
||||
|
||||
</LayoutModificationTemplate>
|
||||
```
|
||||
|
||||
## Use Windows Provisioning multivariant support
|
||||
|
||||
The Windows Provisioning multivariant capability allows you to declare target conditions that, when met, supply specific customizations for each variant condition. For Start customization, you can create specific layouts for each variant that you have. To do this, you must create a separate LayoutModification.xml file for each variant that you want to support and then include these in your provisioning package. For more information on how to do this, see [Create a provisioning package with multivariant settings](./provisioning-packages/provisioning-multivariant.md).
|
||||
|
||||
The provisioning engine chooses the right customization file based on the target conditions that were met, adds the file in the location that's specified for the setting, and then uses the specific file to customize Start. To differentiate between layouts, you can add modifiers to the LayoutModification.xml filename such as "LayoutCustomization1". Regardless of the modifier that you use, the provisioning engine will always output "LayoutCustomization.xml" so that the operating system has a consistent file name to query against.
|
||||
|
||||
For example, if you want to ensure that there's a specific layout for a certain condition, you can:
|
||||
1. Create a specific layout customization file and then name it LayoutCustomization1.xml.
|
||||
2. Include the file as part of your provisioning package.
|
||||
3. Create your multivariant target and reference the XML file within the target condition in the main customization XML file.
|
||||
|
||||
The following example shows what the overall customization file might look like with multivariant support for Start:
|
||||
|
||||
```XML
|
||||
<?xml version="1.0" encoding="utf-8"?>
|
||||
<WindowsCustomizatons>
|
||||
<PackageConfig xmlns="urn:schemas-Microsoft-com:Windows-ICD-Package-Config.v1.0">
|
||||
<ID>{6aaa4dfa-00d7-4aaa-8adf-73c6a7e2501e}</ID>
|
||||
<Name>My Provisioning Package</Name>
|
||||
<Version>1.0</Version>
|
||||
<OwnerType>OEM</OwnerType>
|
||||
<Rank>50</Rank>
|
||||
</PackageConfig>
|
||||
<Settings xmlns="urn:schemas-microsoft-com:windows-provisioning">
|
||||
<Customizations>
|
||||
<Targets>
|
||||
<Target Id="Processor ABC">
|
||||
<TargetState>
|
||||
<TargetState>
|
||||
|
||||
<Condition Name="ProcessorName" Value="Pattern:.*Celeron.*" />
|
||||
|
||||
<Condition Name="ProcessorType" Value="Pattern:.*I|intel.*" />
|
||||
|
||||
</TargetState>
|
||||
</TargetState>
|
||||
</Target>
|
||||
</Targets>
|
||||
<Common>
|
||||
<Settings>
|
||||
|
||||
<Policies>
|
||||
|
||||
<AllowBrowser>1</AllowBrowser>
|
||||
|
||||
<AllowCamera>1</AllowCamera>
|
||||
|
||||
<AllowBluetooth>1</AllowBluetooth>
|
||||
|
||||
</Policies>
|
||||
|
||||
<HotSpot>
|
||||
|
||||
<Enabled>1</Enabled>
|
||||
|
||||
</HotSpot>
|
||||
|
||||
</Settings>
|
||||
|
||||
</Common>
|
||||
<Variant>
|
||||
<TargetRefs>
|
||||
<TargetRef Id="Processor ABC" />
|
||||
</TargetRefs>
|
||||
<Settings>
|
||||
<StartLayout>c:\users\<userprofile>\appdata\local\Microsoft\Windows\Shell\LayoutCustomization1.XML</StartLayout>
|
||||
<HotSpot>
|
||||
<Enabled>1</Enabled>
|
||||
</HotSpot>
|
||||
</Settings>
|
||||
</Variant>
|
||||
</Customizations>
|
||||
</Settings>
|
||||
</WindowsCustomizatons>
|
||||
```
|
||||
|
||||
When the condition is met, the provisioning engine takes the XML file and places it in the location that the operating system has set and then the Start subsystem reads the file and applies the specific customized layout.
|
||||
|
||||
You must repeat this process for all variants that you want to support so that each variant can have a distinct layout for each of the conditions and targets that need to be supported. For example, if you add a **Language** condition, you can create a Start layout that has its own localized group.
|
||||
|
||||
## Add the LayoutModification.xml file to the device
|
||||
|
||||
Once you have created your LayoutModification.xml file to customize devices that will run Windows 10 for desktop editions, you can use Windows ICD methods to add the XML file to the device.
|
||||
|
||||
1. In the **Available customizations** pane, expand **Runtime settings**, select **Start** > Select the **StartLayout** setting.
|
||||
2. In the middle pane, click **Browse** to open File Explorer.
|
||||
3. In the File Explorer window, navigate to the location where you saved your LayoutModification.xml file.
|
||||
|
||||
4. Select the file and then click **Open**.
|
||||
|
||||
This should set the value of **StartLayout**. The setting appears in the **Selected customizations** pane.
|
||||
|
||||
>[!NOTE]
|
||||
>There is currently no way to add the .url and .lnk files through Windows ICD.
|
||||
|
||||
Once you have created the LayoutModification.xml file and it is present in the device, the system overrides the base default layout and any Unattend settings used to customize Start.
|
||||
|
||||
|
||||
## Related topics
|
||||
|
||||
- [Manage Windows 10 Start and taskbar layout](windows-10-start-layout-options-and-policies.md)
|
||||
- [Configure Windows 10 taskbar](configure-windows-10-taskbar.md)
|
||||
- [Customize and export Start layout](customize-and-export-start-layout.md)
|
||||
- [Add image for secondary tiles](start-secondary-tiles.md)
|
||||
- [Customize Windows 10 Start and taskbar with Group Policy](customize-windows-10-start-screens-by-using-group-policy.md)
|
||||
- [Customize Windows 10 Start and taskbar with provisioning packages](customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md)
|
||||
- [Customize Windows 10 Start and taskbar with mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md)
|
||||
- [Changes to Start policies in Windows 10](changes-to-start-policies-in-windows-10.md)
|
||||
238
windows/configuration/start/start-secondary-tiles.md
Normal file
238
windows/configuration/start/start-secondary-tiles.md
Normal file
@ -0,0 +1,238 @@
|
||||
---
|
||||
title: Add image for secondary Microsoft Edge tiles
|
||||
description: Add app tiles on Windows 10 that's a secondary tile.
|
||||
|
||||
ms.topic: article
|
||||
|
||||
ms.date: 12/31/2017
|
||||
---
|
||||
|
||||
# Add image for secondary Microsoft Edge tiles
|
||||
|
||||
**Applies to**
|
||||
|
||||
- Windows 10
|
||||
|
||||
App tiles are the Start screen tiles that represent and launch an app. A tile that allows a user to go to a specific location in an app is a *secondary tile*. Some examples of secondary tiles include:
|
||||
|
||||
- Weather updates for a specific city in a weather app
|
||||
- A summary of upcoming events in a calendar app
|
||||
- Status and updates from an important contact in a social app
|
||||
- A website in Microsoft Edge
|
||||
|
||||
In a Start layout for Windows 10, version 1703, you can include secondary tiles for Microsoft Edge that display a custom image, rather than a tile with the standard Microsoft Edge logo.
|
||||
|
||||
Suppose that the [Start layout that you export](customize-and-export-start-layout.md) had two secondary tiles, such as in the following image:
|
||||
|
||||
|
||||
|
||||
In prior versions of Windows 10, when you applied the Start layout to a device, the tiles would display as shown in the following image:
|
||||
|
||||
|
||||
|
||||
In Windows 10, version 1703, by using the PowerShell cmdlet `export-StartLayoutEdgeAssets` and the policy setting `ImportEdgeAssets`, the tiles will now display the same as they did on the device from which you exported the Start layout.
|
||||
|
||||
|
||||
|
||||
**Example of secondary tiles in XML generated by Export-StartLayout**
|
||||
|
||||
|
||||
```xml
|
||||
<start:SecondaryTile
|
||||
|
||||
AppUserModelID="Microsoft.MicrosoftEdge.Stable_8wekyb3d8bbwe!App"
|
||||
|
||||
TileID="-9513911450"
|
||||
|
||||
DisplayName="Bing"
|
||||
|
||||
Size="2x2"
|
||||
|
||||
Column="0"
|
||||
|
||||
Row="0"
|
||||
|
||||
Arguments="-contentTile -formatVersion 0x00000003 -pinnedTimeLow 0x36a8c2e4 -pinnedTimeHigh 0x01d0919b -securityFlags 0x00000000 -tileType 0x00000000 -url 0x00000014 http://www.bing.com/" Square150x150LogoUri="ms-appdata:///local/PinnedTiles/-9513911450/lowres.png"
|
||||
|
||||
Wide310x150LogoUri="ms-appx:///"
|
||||
|
||||
ShowNameOnSquare150x150Logo="true"
|
||||
|
||||
ShowNameOnWide310x150Logo="true"
|
||||
|
||||
BackgroundColor="#7fffffff"
|
||||
|
||||
/>
|
||||
```
|
||||
|
||||
## Export Start layout and assets
|
||||
|
||||
1. Follow the instructions in [Customize and export Start layout](customize-and-export-start-layout.md#customize-the-start-screen-on-your-test-computer) to customize the Start screen on your test computer.
|
||||
2. Open Windows PowerShell as an administrator and enter the following command:
|
||||
|
||||
```powershell
|
||||
Export-StartLayout -path <path><file name>.xml
|
||||
```
|
||||
|
||||
In the previous command, `-path` is a required parameter that specifies the path and file name for the export file. You can specify a local path or a UNC path (for example, \\\\FileServer01\\StartLayouts\\StartLayoutMarketing.xml).
|
||||
|
||||
Use a file name of your choice—for example, StartLayoutMarketing.xml. Include the .xml file name extension. The [Export-StartLayout](/powershell/module/startlayout/export-startlayout) cmdlet doesn't append the file name extension, and the policy settings require the extension.
|
||||
|
||||
3. If you’d like to change the image for a secondary tile to your own custom image, open the layout.xml file, and look for the images that the tile references.
|
||||
- For example, your layout.xml contains `Square150x150LogoUri="ms-appdata:///local/PinnedTiles/21581260870/hires.png" Wide310x150LogoUri="ms-appx:///"`
|
||||
|
||||
- Open `C:\Users\<username>\AppData\Local\Packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\LocalState\PinnedTiles\21581260870\` and replace those images with your customized images.
|
||||
|
||||
4. In Windows PowerShell, enter the following command:
|
||||
|
||||
|
||||
```powershell
|
||||
Export-StartLayoutEdgeAssets assets.xml
|
||||
```
|
||||
|
||||
## Configure policy settings
|
||||
|
||||
You can apply the customized Start layout with images for secondary tiles by using [mobile device management](customize-windows-10-start-screens-by-using-mobile-device-management.md) or [a provisioning package](customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md). However, because you're including the images for secondary tiles, you must configure another setting to import the Edge assets.
|
||||
|
||||
### Using MDM
|
||||
|
||||
In Microsoft Intune, you create a device restrictions policy to apply to device group. For other MDM solutions, you may need to use an OMA-URI setting for Start layout, based on the [Policy configuration service provider (CSP)](/windows/client-management/mdm/policy-configuration-service-provider). The OMA-URI setting is `./User/Vendor/MSFT/Policy/Config/Start/StartLayout`.
|
||||
|
||||
1. Sign in to the [Intune admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
2. Select **Devices** > **Configuration profiles** > **Create profile**.
|
||||
3. Enter the following properties:
|
||||
|
||||
- **Platform**: Select **Windows 10 and later**.
|
||||
- **Profile**: Select **Templates** > **Device restrictions**.
|
||||
|
||||
4. Select **Create**.
|
||||
5. In **Basics**, enter the following properties:
|
||||
|
||||
- **Name**: Enter a descriptive name for the policy. Name your policies so you can easily identify them later.
|
||||
- **Description**: Enter a description for the policy. This setting is optional, but recommended.
|
||||
|
||||
6. Select **Next**.
|
||||
|
||||
7. In **Configuration settings**, select **Start**. Configure the following properties:
|
||||
|
||||
- **Start menu layout**: Browse to, and select your Start layout XML file.
|
||||
- **Pin websites to tiles in Start menu**: Browse to, and select your assets XML file.
|
||||
|
||||
There are more Start menu settings you can configure. For more information on these settings, see [Start settings in Intune](/intune/device-restrictions-windows-10#start)
|
||||
|
||||
8. Select **Next**.
|
||||
9. In **Scope tags** (optional), assign a tag to filter the profile to specific IT groups, such as `US-NC IT Team` or `JohnGlenn_ITDepartment`. For more information about scope tags, see [Use RBAC and scope tags for distributed IT](/mem/intune/fundamentals/scope-tags).
|
||||
|
||||
Select **Next**.
|
||||
|
||||
10. In **Assignments**, select the users or groups that will receive your profile. For more information on assigning profiles, see [Assign user and device profiles](/mem/intune/configuration/device-profile-assign).
|
||||
|
||||
Select **Next**.
|
||||
|
||||
11. In **Review + create**, review your settings. When you select **Create**, your changes are saved, and the profile is assigned. The policy is also shown in the profiles list.
|
||||
|
||||
### Using a provisioning package
|
||||
|
||||
#### <a href="" id="escape"></a>Prepare the Start layout and Edge assets XML files
|
||||
|
||||
The **export-StartLayout** and **export-StartLayoutEdgeAssets** cmdlets produce XML files. Because Windows Configuration Designer produces a customizations.xml file that contains the configuration settings, adding the Start layout and Edge assets sections to the customizations.xml file directly would result in an XML file embedded in an XML file. Before you add the Start layout and Edge assets sections to the customizations.xml file, you must replace the markup characters in your layout.xml with escape characters.
|
||||
|
||||
|
||||
|
||||
1. Copy the contents of layout.xml into an online tool that escapes characters.
|
||||
|
||||
2. Copy the contents of assets.xml into an online tool that escapes characters.
|
||||
|
||||
3. When you create a provisioning package, you'll copy the text with the escape characters and paste it in the customizations.xml file for your project.
|
||||
|
||||
#### Create a provisioning package that contains a customized Start layout
|
||||
|
||||
|
||||
|
||||
Use the Windows Configuration Designer tool to create a provisioning package. [Learn how to install Windows Configuration Designer.](provisioning-packages/provisioning-install-icd.md)
|
||||
|
||||
>[!IMPORTANT]
|
||||
>When you build a provisioning package, you may include sensitive information in the project files and in the provisioning package (.ppkg) file. Although you have the option to encrypt the .ppkg file, project files are not encrypted. You should store the project files in a secure location and delete the project files when they are no longer needed.
|
||||
|
||||
1. Open Windows Configuration Designer (by default, %systemdrive%\\Program Files (x86)\\Windows Kits\\10\\Assessment and Deployment Kit\\Imaging and Configuration Designer\\x86\\ICD.exe).
|
||||
|
||||
2. Choose **Advanced provisioning**.
|
||||
|
||||
3. Name your project, and select **Next**.
|
||||
|
||||
4. Choose **All Windows desktop editions** and select **Next**.
|
||||
|
||||
5. On **New project**, select **Finish**. The workspace for your package opens.
|
||||
|
||||
6. Expand **Runtime settings** > **Policies** > **Start**, and select **StartLayout**.
|
||||
|
||||
>[!TIP]
|
||||
>If **Start** is not listed, check the type of settings you selected in step 4. You must create the project using settings for **All Windows desktop editions**.
|
||||
|
||||
7. Enter **layout.xml**. This value creates a placeholder in the customizations.xml file that you'll replace with the contents of the layout.xml file in a later step.
|
||||
|
||||
8. In the **Available customizations** pane, select **ImportEdgeAssets**.
|
||||
|
||||
9. Enter **assets.xml**. This value creates a placeholder in the customizations.xml file that you'll replace with the contents of the assets.xml file in a later step.
|
||||
|
||||
10. Save your project and close Windows Configuration Designer.
|
||||
|
||||
11. In File Explorer, open the project's directory. (The default location is C:\Users\\*user name*\Documents\Windows Imaging and Configuration Designer (WICD)\\*project name*)
|
||||
|
||||
12. Open the customizations.xml file in a text editor. The **<Customizations>** section will look like this:
|
||||
|
||||
|
||||
|
||||
13. Replace **layout.xml** with the text from the layout.xml file, [with markup characters replaced with escape characters](#escape).
|
||||
|
||||
14. Replace **assets.xml** with the text from the assets.xml file, [with markup characters replaced with escape characters](#escape).
|
||||
|
||||
15. Save and close the customizations.xml file.
|
||||
|
||||
16. Open Windows Configuration Designer and open your project.
|
||||
|
||||
17. On the **File** menu, select **Save.**
|
||||
|
||||
18. On the **Export** menu, select **Provisioning package**.
|
||||
|
||||
19. Change **Owner** to **IT Admin**, which will set the precedence of this provisioning package higher than provisioning packages applied to this device from other sources, and then select **Next.**
|
||||
|
||||
20. Optional. In the **Provisioning package security** window, you can choose to encrypt the package and enable package signing.
|
||||
|
||||
- **Enable package encryption** - If you select this option, an auto-generated password will be shown on the screen.
|
||||
|
||||
- **Enable package signing** - If you select this option, you must select a valid certificate to use for signing the package. You can specify the certificate by clicking **Select...** and choosing the certificate you want to use to sign the package.
|
||||
|
||||
21. Select **Next** to specify the output location where you want the provisioning package to go when it's built. By default, Windows Imaging and Configuration Designer (ICD) uses the project folder as the output location.
|
||||
|
||||
Optionally, you can select **Browse** to change the default output location.
|
||||
|
||||
22. Select **Next**.
|
||||
|
||||
23. Select **Build** to start building the package. The provisioning package doesn't take long to build. The project information is displayed in the build page and the progress bar indicates the build status.
|
||||
|
||||
If you need to cancel the build, select **Cancel**. It cancels the current build process, closes the wizard, and takes you back to the **Customizations Page**.
|
||||
|
||||
24. If your build fails, an error message will show up that includes a link to the project folder. You can scan the logs to determine what caused the error. Once you fix the issue, try building the package again.
|
||||
|
||||
If your build is successful, the name of the provisioning package, output directory, and project directory will be shown.
|
||||
|
||||
- If you choose, you can build the provisioning package again and pick a different path for the output package. To change the path, select **Back** to change the output package name and path, and then select **Next** to start another build.
|
||||
- If you're done, select **Finish** to close the wizard and go back to the **Customizations Page**.
|
||||
|
||||
25. Copy the provisioning package to the target device.
|
||||
|
||||
26. Double-click the ppkg file and allow it to install.
|
||||
|
||||
## Related articles
|
||||
|
||||
|
||||
- [Manage Windows 10 Start and taskbar layout](windows-10-start-layout-options-and-policies.md)
|
||||
- [Configure Windows 10 taskbar](configure-windows-10-taskbar.md)
|
||||
- [Customize and export Start layout](customize-and-export-start-layout.md)
|
||||
- [Start layout XML for desktop editions of Windows 10 (reference)](start-layout-xml-desktop.md)
|
||||
- [Customize Windows 10 Start and taskbar with Group Policy](customize-windows-10-start-screens-by-using-group-policy.md)
|
||||
- [Customize Windows 10 Start and taskbar with provisioning packages](customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md)
|
||||
- [Customize Windows 10 Start and taskbar with mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md)
|
||||
- [Changes to Start policies in Windows 10](changes-to-start-policies-in-windows-10.md)
|
||||
|
||||
@ -0,0 +1,76 @@
|
||||
---
|
||||
title: Supported CSP policies to customize Start menu on Windows 11 | Microsoft Docs
|
||||
description: See a list of the Policy CSP - Start items that are supported on Windows 11 to customize the Start menu.
|
||||
ms.reviewer: ericpapa
|
||||
|
||||
ms.date: 12/31/2017
|
||||
ms.topic: article
|
||||
---
|
||||
|
||||
# Supported configuration service provider (CSP) policies for Windows 11 Start menu
|
||||
|
||||
**Applies to**:
|
||||
|
||||
- Windows 11
|
||||
- Windows 11, version 22H2
|
||||
|
||||
The Windows OS exposes CSPs that are used by MDM providers, like [Microsoft Intune](/mem/intune/fundamentals/what-is-intune). In an MDM policy, these CSPs are settings that you configure in a policy. When the policy is ready, you deploy the policy to your devices.
|
||||
|
||||
This article lists the CSPs that are available to customize the Start menu for Windows 11 devices. Windows 11 uses the [Policy CSP - Start](/windows/client-management/mdm/policy-csp-start). For more general information, see [Configuration service provider (CSP) reference](/windows/client-management/mdm/configuration-service-provider-reference).
|
||||
|
||||
For information on customizing the Start menu layout using policy, see [Customize the Start menu layout on Windows 11](customize-start-menu-layout-windows-11.md).
|
||||
|
||||
## Existing Windows CSP policies that Windows 11 supports
|
||||
|
||||
- [Start/AllowPinnedFolderDocuments](/windows/client-management/mdm/policy-csp-start#start-allowpinnedfolderdocuments)
|
||||
- [Start/AllowPinnedFolderDownloads](/windows/client-management/mdm/policy-csp-start#start-allowpinnedfolderfileexplorer)
|
||||
- [Start/AllowPinnedFolderFileExplorer](/windows/client-management/mdm/policy-csp-start#start-allowpinnedfolderhomegroup)
|
||||
- [Start/AllowPinnedFolderHomeGroup](/windows/client-management/mdm/policy-csp-start#start-allowpinnedfolderhomegroup)
|
||||
- [Start/AllowPinnedFolderMusic](/windows/client-management/mdm/policy-csp-start#start-allowpinnedfoldermusic)
|
||||
- [Start/AllowPinnedFolderNetwork](/windows/client-management/mdm/policy-csp-start#start-allowpinnedfoldernetwork)
|
||||
- [Start/AllowPinnedFolderPersonalFolder](/windows/client-management/mdm/policy-csp-start#start-allowpinnedfolderpersonalfolder)
|
||||
- [Start/AllowPinnedFolderPictures](/windows/client-management/mdm/policy-csp-start#start-allowpinnedfolderpictures)
|
||||
- [Start/AllowPinnedFolderSettings](/windows/client-management/mdm/policy-csp-start#start-allowpinnedfoldersettings)
|
||||
- [Start/AllowPinnedFolderVideos](/windows/client-management/mdm/policy-csp-start#start-allowpinnedfoldervideos)
|
||||
- [Start/HideChangeAccountSettings](/windows/client-management/mdm/policy-csp-start#start-hidechangeaccountsettings)
|
||||
- [Start/HideHibernate](/windows/client-management/mdm/policy-csp-start#start-hidehibernate)
|
||||
- [Start/HideLock](/windows/client-management/mdm/policy-csp-start#start-hidelock)
|
||||
- [Start/HidePowerButton](/windows/client-management/mdm/policy-csp-start#start-hidepowerbutton)
|
||||
- [Start/HideRestart](/windows/client-management/mdm/policy-csp-start#start-hiderestart)
|
||||
- [Start/HideShutDown](/windows/client-management/mdm/policy-csp-start#start-hideshutdown)
|
||||
- [Start/HideSignOut](/windows/client-management/mdm/policy-csp-start#start-hidesignout)
|
||||
- [Start/HideSleep](/windows/client-management/mdm/policy-csp-start#start-hidesleep)
|
||||
- [Start/HideSwitchAccount](/windows/client-management/mdm/policy-csp-start#start-hideswitchaccount)
|
||||
- [Start/HideUserTile](/windows/client-management/mdm/policy-csp-start#start-hideusertile)
|
||||
- [Start/HideRecentJumplists](/windows/client-management/mdm/policy-csp-start#start-hiderecentjumplists)
|
||||
- [Start/NoPinningToTaskbar](/windows/client-management/mdm/policy-csp-start#start-nopinningtotaskbar)
|
||||
- **Start/ShowOrHideMostUsedApps**: New policy starting with Windows 11. This policy enforces always showing Most Used Apps, or always hiding Most Used Apps in the Start menu. If you use this policy, the [Start/HideFrequentlyUsedApps](/windows/client-management/mdm/policy-csp-start#start-hidefrequentlyusedapps) policy is ignored.
|
||||
|
||||
The [Start/HideFrequentlyUsedApps](/windows/client-management/mdm/policy-csp-start#start-hidefrequentlyusedapps) policy enforces hiding Most Used Apps on the Start menu. You can't use this policy to enforce always showing Most Used Apps on the Start menu.
|
||||
|
||||
**The following policies are supported starting with Windows 11, version 22H2:**
|
||||
|
||||
- [Start/HideAppList](/windows/client-management/mdm/policy-csp-start#start-hideapplist)
|
||||
- [Start/DisableContextMenus](/windows/client-management/mdm/policy-csp-start#start-disablecontextmenus)
|
||||
## Existing CSP policies that Windows 11 doesn't support
|
||||
|
||||
- [Start/StartLayout](/windows/client-management/mdm/policy-csp-start#start-startlayout)
|
||||
- Group policy: `User Configuration\Administrative Templates\Start Menu and Taskbar\Start Layout`
|
||||
|
||||
- [Start/HideRecentlyAddedApps](/windows/client-management/mdm/policy-csp-start#start-hiderecentlyaddedapps)
|
||||
- Group policy: `Computer Configuration\Administrative Templates\Start Menu and Taskbar\Remove "Recently added" list from Start Menu`
|
||||
|
||||
|
||||
> [!NOTE]
|
||||
> The following two policies are supported starting in Windows 11, version 22H2
|
||||
|
||||
- [Start/HideAppList](/windows/client-management/mdm/policy-csp-start#start-hideapplist)
|
||||
- Group policy:
|
||||
- `Computer Configuration\Administrative Templates\Start Menu and Taskbar\Remove All Programs list from the Start menu`
|
||||
- `User Configuration\Administrative Templates\Start Menu and Taskbar\Remove All Programs list from the Start menu`
|
||||
|
||||
- [Start/DisableContextMenus](/windows/client-management/mdm/policy-csp-start#start-disablecontextmenus)
|
||||
- Group policy:
|
||||
|
||||
- `Computer Configuration\Administrative Templates\Start Menu and Taskbar\Disable context menus in the Start Menu`
|
||||
- `User Configuration\Administrative Templates\Start Menu and Taskbar\Disable context menus in the Start Menu`
|
||||
@ -0,0 +1,222 @@
|
||||
---
|
||||
title: Customize and manage the Windows 10 Start and taskbar layout
|
||||
description: On Windows devices, customize the start menu layout and taskbar using XML, group policy, provisioning package, or MDM policy. You can add pinned folders, add a start menu size, pin apps to the taskbar, and more.
|
||||
ms.topic: article
|
||||
ms.date: 08/05/2021
|
||||
---
|
||||
|
||||
# Customize the Start menu and taskbar layout on Windows 10 and later devices
|
||||
|
||||
**Applies to**:
|
||||
|
||||
- Windows 10 version 1607 and later
|
||||
- Windows Server 2016 with Desktop Experience
|
||||
- Windows Server 2019 with Desktop Experience
|
||||
|
||||
> **Looking for consumer information?** [See what's on the Start menu](https://support.microsoft.com/help/17195/windows-10-see-whats-on-the-menu)
|
||||
>
|
||||
> **Looking for OEM information?** See [Customize the Taskbar](/windows-hardware/customize/desktop/customize-the-windows-11-taskbar) and [Customize the Start layout](/windows-hardware/customize/desktop/customize-the-windows-11-start-menu).
|
||||
|
||||
Your organization can deploy a customized Start and taskbar to Windows 10 Professional, Enterprise, or Education devices. Use a standard, customized Start layout on devices that are common to multiple users, and devices that are locked down. Configuring the taskbar allows you to pin useful apps for your users, and remove apps that are pinned by default.
|
||||
|
||||
>[!NOTE]
|
||||
>Support for applying a customized taskbar using MDM is added in Windows 10, version 1703.
|
||||
|
||||
As administrator, you can use these features to customize Start and taskbar to meet your organization needs. This article describes the different ways you can customize Start and taskbar, and lists the Start policies. It also includes taskbar information on a clean operating system (OS) installation, and when an OS is upgraded.
|
||||
|
||||
>[!NOTE]
|
||||
>For information on using the layout modification XML to configure Start with roaming user profiles, see [Deploy Roaming User Profiles](/windows-server/storage/folder-redirection/deploy-roaming-user-profiles#step-7-optionally-specify-a-start-layout-for-windows-10-pcs).
|
||||
>
|
||||
>Using CopyProfile for Start menu customization in Windows 10 isn't supported. For more information [Customize the Default User Profile by Using CopyProfile](/windows-hardware/manufacture/desktop/customize-the-default-user-profile-by-using-copyprofile)
|
||||
|
||||
## Use XML
|
||||
|
||||
On an existing Windows device, you can set up the **Start** screen, and then export the layout to an XML file. When you have the XML file, add this file to a group policy, a Windows Configuration Designer provisioning package, or a mobile device management (MDM) policy. Using these methods, you can deploy the XML file to your devices. When the devices receive your policy, they'll use the layout configured in the XML file.
|
||||
|
||||
For more information, see [Customize and export Start layout](customize-and-export-start-layout.md).
|
||||
|
||||
For the **taskbar**, you can use the same XML file as the start screen. Or, you can create a new XML file. When you have the XML file, add this file to a group policy or a provisioning package. Using these methods, you can deploy the XML file to your devices. When the devices receive your policy, they'll use the taskbar settings you configured in the XML file.
|
||||
|
||||
For more information, see [Configure Windows 10 taskbar](configure-windows-10-taskbar.md).
|
||||
|
||||
## Use group policy
|
||||
|
||||
Using group policy objects (GPO), you can manage different parts of the Start menu and taskbar. You don't need to reimage the devices. Using administrative templates, you configure settings in a policy, and then deploy this policy to your devices. [Start menu policy settings](#start-menu-policy-settings) (in this article) lists the policies you can configure.
|
||||
|
||||
For more information, see [Use group policy to customize Windows 10 Start and taskbar](customize-windows-10-start-screens-by-using-group-policy.md).
|
||||
|
||||
## Use provisioning packages
|
||||
|
||||
Provisioning packages are containers that include a set of configuration settings. They're designed to configure a device quickly, without installing a new image. For more information on what provisioning packages are, and what they do, see [Provisioning packages](./provisioning-packages/provisioning-packages.md).
|
||||
|
||||
Using a provisioning package, you can customize the Start and taskbar. For more information, see [Use provisioning packages to customize Windows 10 Start and taskbar](customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md).
|
||||
|
||||
## Use a mobile device management (MDM) solution
|
||||
|
||||
Using an MDM solution, you add an XML file to a policy, and then deploy this policy to your devices.
|
||||
|
||||
If you use Microsoft Intune for your MDM solution, then you can use settings to configure Start and the taskbar. For more information on the settings you can configure, see [Start settings in Microsoft Intune](/mem/intune/configuration/device-restrictions-windows-10#start).
|
||||
|
||||
For more information, see [Use MDM to customize Windows 10 Start and taskbar](customize-windows-10-start-screens-by-using-mobile-device-management.md).
|
||||
|
||||
## Start menu policy settings
|
||||
|
||||
|
||||
|
||||
The following list includes the different Start options, and any policy or local settings. The settings in the list can also be used in a provisioning package. If you use a provisioning package, see the [Windows Configuration Designer reference](./wcd/wcd-policies.md#start).
|
||||
|
||||
- **User tile**
|
||||
- **Group policy**: `User Configuration\Administrative Templates\Start Menu and Taskbar\Remove Logoff on the Start menu`
|
||||
- **Local setting**: None
|
||||
- **MDM policy**:
|
||||
- Start/HideUserTile
|
||||
- Start/HideSwitchAccount
|
||||
- Start/HideSignOut
|
||||
- Start/HideLock
|
||||
- Start/HideChangeAccountSettings
|
||||
|
||||
- **Most used**
|
||||
- **Group policy**: `User Configuration\Administrative Templates\Start Menu and Taskbar\Remove frequent programs from the Start menu`
|
||||
- **Local setting**: Settings > Personalization > Start > Show most used apps
|
||||
- **MDM policy**: Start/HideFrequentlyUsedApps
|
||||
|
||||
- **Suggestions, Dynamically inserted app tile**
|
||||
- **Group policy**: `Computer Configuration\Administrative Templates\Windows Components\Cloud Content\Turn off Microsoft consumer experiences`
|
||||
|
||||
This policy also enables or disables notifications for:
|
||||
|
||||
- A user's Microsoft account
|
||||
- App tiles that Microsoft dynamically adds to the default Start menu
|
||||
|
||||
- **Local setting**: Settings > Personalization > Start > Occasionally show suggestions in Start
|
||||
- **MDM policy**: Allow Windows Consumer Features
|
||||
|
||||
- **Recently added**
|
||||
- **Group policy**: `Computer configuration\Administrative Template\Start Menu and Taskbar\Remove "Recently Added" list from Start Menu`
|
||||
|
||||
This policy applies to:
|
||||
|
||||
- Windows 10 version 1803 and later
|
||||
|
||||
- **Local setting**: Settings > Personalization > Start > Show recently added apps
|
||||
- **MDM policy**: Start/HideRecentlyAddedApps
|
||||
|
||||
- **Pinned folders**
|
||||
- **Local setting**: Settings > Personalization > Start > Choose which folders appear on Start
|
||||
- **MDM policy**: AllowPinnedFolder
|
||||
|
||||
- **Power**
|
||||
- **Group policy**: `User Configuration\Administrative Templates\Start Menu and Taskbar\Remove and prevent access to the Shut Down, Restart, Sleep, and Hibernate commands`
|
||||
- **Local setting**: None
|
||||
- **MDM policy**:
|
||||
- Start/HidePowerButton
|
||||
- Start/HideHibernate
|
||||
- Start/HideRestart
|
||||
- Start/HideShutDown
|
||||
- Start/HideSleep
|
||||
|
||||
- **Start layout**
|
||||
- **Group policy**: `User Configuration\Administrative Templates\Start Menu and Taskbar\Prevent users from customizing their Start screen`
|
||||
|
||||
When a full Start screen layout is imported with Group Policy or MDM, users can't pin, unpin, or uninstall apps from the Start screen. Users can see and open all apps in the **All Apps** view, but they can't pin any apps to the Start screen. When a partial Start screen layout is imported, users can't change the tile groups applied by the partial layout. They can change other tile groups, and create their own tile groups.
|
||||
|
||||
**Start layout** policy can be used to pin apps to the taskbar based on an XML File you provide. Users can change the order of pinned apps, unpin apps, and pin more apps to the taskbar.
|
||||
|
||||
- **Local setting**: None
|
||||
- **MDM policy**:
|
||||
- Start layout
|
||||
- ImportEdgeAssets
|
||||
|
||||
- **Jump lists**
|
||||
- **Group policy**: `User Configuration\Administrative Templates\Start Menu and Taskbar\Do not keep history of recently opened documents`
|
||||
- **Local setting**: Settings > Personalization > Start > Show recently opened items in Jump Lists on Start or the taskbar
|
||||
- **MDM policy**: Start/HideRecentJumplists
|
||||
|
||||
- **Start size**
|
||||
- **Group policy**: `User Configuration\Administrative Templates\Start Menu and Taskbar\Force Start to be either full screen size or menu size`
|
||||
- **Local setting**: Settings > Personalization > Start > Use Start full screen
|
||||
- **MDM policy**: Force Start size
|
||||
|
||||
- **App list**
|
||||
- **Local setting**: Settings > Personalization > Start > Show app list in Start menu
|
||||
- **MDM policy**: Start/HideAppList
|
||||
|
||||
- **All settings**
|
||||
- **Group policy**: `User Configuration\Administrative Templates\Prevent changes to Taskbar and Start Menu Settings`
|
||||
- **Local setting**: None
|
||||
|
||||
- **Taskbar**
|
||||
- **Local setting**: None
|
||||
- **MDM policy**: Start/NoPinningToTaskbar
|
||||
|
||||
> [!NOTE]
|
||||
> In the **Settings** app > **Personalization** > **Start**, there is a **Show more tiles on Start** option. The default tile layout for Start tiles is 3 columns of medium sized tiles. **Show more tiles on Start** enables 4 columns. To configure the 4-column layout when you [customize and export a Start layout](customize-and-export-start-layout.md), turn on the **Show more tiles** setting, and then arrange your tiles.
|
||||
|
||||
## Taskbar options
|
||||
|
||||
Starting in Windows 10 version 1607, you can pin more apps to the taskbar, and remove default pinned apps from the taskbar. You can select different taskbar configurations based on device locale or region.
|
||||
|
||||
There are three app categories that could be pinned to a taskbar:
|
||||
|
||||
- Apps pinned by the user
|
||||
- Default Windows apps pinned during the OS installation, such as Microsoft Edge, File Explorer, and Store
|
||||
- Apps pinned by your organization, such as in an unattended Windows setup
|
||||
|
||||
In an unattended Windows setup file, it's recommended to use the [layoutmodification.xml method](configure-windows-10-taskbar.md) to configure the taskbar options. It's not recommended to use [TaskbarLinks](/windows-hardware/customize/desktop/unattend/microsoft-windows-shell-setup-taskbarlinks).
|
||||
|
||||
The following example shows how apps are pinned. In OS configured to use a right-to-left language, the taskbar order is reversed:
|
||||
|
||||
- Windows default apps to the left (blue circle)
|
||||
- Apps pinned by the user in the center (orange triangle)
|
||||
- Apps that you pin using XML to the right (green square)
|
||||
|
||||
|
||||
|
||||
If you apply the taskbar configuration to a clean install or an update, users can still:
|
||||
|
||||
- Pin more apps
|
||||
- Change the order of pinned apps
|
||||
- Unpin any app
|
||||
|
||||
> [!TIP]
|
||||
> In Windows 10 version 1703, you can apply the `Start/NoPinningToTaskbar` MDM policy. This policy prevents users from pinning and unpinning apps on the taskbar.
|
||||
|
||||
### Taskbar configuration applied to clean install of Windows 10
|
||||
|
||||
In a clean install, if you apply a taskbar layout, only the following apps are pinned to the taskbar:
|
||||
|
||||
- Apps you specifically add
|
||||
- Any default apps you don't remove
|
||||
|
||||
After the layout is applied, users can pin more apps to the taskbar.
|
||||
|
||||
### Taskbar configuration applied to Windows 10 upgrades
|
||||
|
||||
When a device is upgraded to Windows 10, apps are already pinned to the taskbar. Some apps may have been pinned to the taskbar by a user, by a customized base image, or by using Windows unattended setup.
|
||||
|
||||
On Windows 10 version 1607 and later, the new taskbar layout for upgrades apply the following behavior:
|
||||
|
||||
- If users pinned apps to the taskbar, then those pinned apps remain. New apps are added to the right.
|
||||
- If users didn't pin any apps (they're pinned during installation or by policy), and the apps aren't in an updated layout file, then the apps are unpinned.
|
||||
- If a user didn't pin the app, and the app is in the updated layout file, then the app is pinned to the right.
|
||||
- New apps specified in updated layout file are pinned to right of user's pinned apps.
|
||||
|
||||
[Learn how to configure Windows 10 taskbar](configure-windows-10-taskbar.md).
|
||||
|
||||
## Start layout configuration errors
|
||||
|
||||
If your Start layout customization isn't applied as you expect, open the **Event Viewer**. Go to **Applications and Services Log** > **Microsoft** > **Windows** > **ShellCommon-StartLayoutPopulation** > **Operational**. Look for the following events:
|
||||
|
||||
- **Event 22**: The XML is malformed. The specified file isn't valid XML. This event can happen if the file has extra spaces or unexpected characters. Or, if the file isn't saved in the UTF8 format.
|
||||
- **Event 64**: The XML is valid, and has unexpected values. This event can happen when the configuration isn't understood, elements aren't in [the required order](start-layout-xml-desktop.md#required-order), or source isn't found, such as a missing or misspelled `.lnk`.
|
||||
|
||||
## Next steps
|
||||
|
||||
- [Configure Windows 10 taskbar](configure-windows-10-taskbar.md)
|
||||
- [Customize and export Start layout](customize-and-export-start-layout.md)
|
||||
- [Add image for secondary tiles](start-secondary-tiles.md)
|
||||
- [Start layout XML for desktop editions of Windows 10 (reference)](start-layout-xml-desktop.md)
|
||||
- [Customize Windows 10 Start and taskbar with Group Policy](customize-windows-10-start-screens-by-using-group-policy.md)
|
||||
- [Customize Windows 10 Start and taskbar with provisioning packages](customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md)
|
||||
- [Customize Windows 10 Start and taskbar with mobile device management (MDM)](customize-windows-10-start-screens-by-using-mobile-device-management.md)
|
||||
- [Changes to Start policies in Windows 10](changes-to-start-policies-in-windows-10.md)
|
||||
Reference in New Issue
Block a user