commit 13f1090ee65f4a6e80ebbded8a29a5b7cc18e0ec Merge: ff49098a b7022583 Author: jdeckerMS <jdecker@microsoft.com> Date: Fri Mar 31 09:11:06 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2edge commit ff49098a8fc4e286ab2002c15fe410901afbc548 Merge: d30056bd 2a8a5861 Author: jdeckerMS <jdecker@microsoft.com> Date: Fri Mar 31 08:54:32 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2edge commit d30056bdaa7c65fdd9292293fdd74d0067f6843c Merge: 061aa7ff 5c840fcd Author: jdeckerMS <jdecker@microsoft.com> Date: Fri Mar 31 08:50:35 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2edge commit 061aa7ffa41809f11caab7c50abcfeeb66eaf765 Author: jdeckerMS <jdecker@microsoft.com> Date: Fri Mar 31 08:49:21 2017 -0700 got rid of redundant text commit 28f92a6e71c7bb2c18297cbe9aa4f344b501167b Author: jdeckerMS <jdecker@microsoft.com> Date: Fri Mar 31 08:38:10 2017 -0700 format commit 9f42b3c3f6b40c333aeb0dbe269037d76e8a6681 Author: jdeckerMS <jdecker@microsoft.com> Date: Fri Mar 31 08:36:30 2017 -0700 numbering commit c825690f4158baeaaf899f33c362f49ab2e0d1da Author: jdeckerMS <jdecker@microsoft.com> Date: Fri Mar 31 08:26:11 2017 -0700 sync commit d665b656bcc139af3d7a0b9c8b88c6fd4e70be0e Author: jdeckerMS <jdecker@microsoft.com> Date: Fri Mar 31 08:25:39 2017 -0700 change escape procedure commit 42088746e72d410a4487c46122fcd24267d4bfe9 Author: jdeckerMS <jdecker@microsoft.com> Date: Fri Mar 31 06:30:32 2017 -0700 fix typo commit 3658391492d70b9d1eb84cd57fe92f8a5c92698f Merge: ebd6e1c5 60e98765 Author: jdeckerMS <jdecker@microsoft.com> Date: Fri Mar 31 06:27:07 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2edge commit ebd6e1c5b65328f7b70cea0c1daca1625620766f Merge: 11e51f8f a45661ff Author: jdeckerMS <jdecker@microsoft.com> Date: Thu Mar 30 13:37:18 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2edge commit 11e51f8ff68689d8ee87cfd77eefc4595ce7617c Author: jdeckerMS <jdecker@microsoft.com> Date: Thu Mar 30 11:12:43 2017 -0700 inner links commit 22050763c07cd92931e57cecd96f5de259e1f4fb Merge: bf9b2cbe 7db06064 Author: jdeckerMS <jdecker@microsoft.com> Date: Thu Mar 30 11:06:28 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2edge commit bf9b2cbe5fcf618c3654dc8c94d3b7d28a0c4579 Merge: 7e06781a ebaa19a0 Author: jdeckerMS <jdecker@microsoft.com> Date: Mon Mar 27 14:08:43 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2edge commit 7e06781a86193250b71582ea22647367131e5324 Author: jdeckerMS <jdecker@microsoft.com> Date: Mon Mar 27 14:00:43 2017 -0700 fix link commit 265d164f59ef91e9485c69ce2ef76dc08e6d561c Author: jdeckerMS <jdecker@microsoft.com> Date: Mon Mar 27 13:49:15 2017 -0700 secondary tiles ready for review commit 8e0f57b38fe967a6a1c6794a4b5d97522139304a Merge: ec1be358 3fa1f32e Author: jdeckerMS <jdecker@microsoft.com> Date: Mon Mar 27 12:27:33 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2edge commit ec1be358670661446c5600d07f5cbec47bb4cc0e Merge: cb27a41b 0a2afbb1 Author: jdeckerMS <jdecker@microsoft.com> Date: Mon Mar 27 07:57:10 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2edge commit cb27a41b907a51e5a76613143bb1c605c4fb1628 Author: jdeckerMS <jdecker@microsoft.com> Date: Fri Mar 24 13:44:55 2017 -0700 sync commit 56206d7637064329783c711821c1a8f494c5a57e Merge: 7c6d6f3c 233b34ce Author: jdeckerMS <jdecker@microsoft.com> Date: Fri Mar 24 11:15:49 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2edge commit 7c6d6f3c481aedb01ab25633660867cf1e38400a Author: jdeckerMS <jdecker@microsoft.com> Date: Fri Mar 24 11:15:20 2017 -0700 sync notes commit 465871de30b4e9f470bfbe370438c35e36a9927d Author: jdeckerMS <jdecker@microsoft.com> Date: Thu Mar 23 13:23:39 2017 -0700 notes for new secondary tile topic commit b102a01ee80e5d73052ae273cb371ef62d127429 Merge: 24c55704 8d2cf84e Author: jdeckerMS <jdecker@microsoft.com> Date: Thu Mar 23 13:10:29 2017 -0700 Merge remote-tracking branch 'refs/remotes/origin/rs2' into jdrs2edge
8.5 KiB
title, description, ms.assetid, keywords, ms.prod, ms.mktglfcycl, ms.sitesec, author, localizationpriority
title | description | ms.assetid | keywords | ms.prod | ms.mktglfcycl | ms.sitesec | author | localizationpriority | |
---|---|---|---|---|---|---|---|---|---|
Customize and export Start layout (Windows 10) | The easiest method for creating a customized Start layout is to set up the Start screen and export the layout. | CA8DF327-5DD4-452F-9FE5-F17C514B6236 |
|
w10 | manage | library | jdeckerMS | high |
Customize and export Start layout
Applies to
- Windows 10
Looking for consumer information? See Customize the Start menu
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 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.
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:
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
-
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.
-
Create a new user account that you will use to customize the Start layout.
-
Sign in to your test computer with the user account that you created.
-
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 click Pin to Start.
To view all apps, click 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 click Unpin from Start.
-
Drag tiles on Start to reorder or group apps.
-
Resize tiles. To resize tiles, right-click the tile and then click Resize.
-
Create your own app groups. Drag the apps to an empty area. To name a group, click above the group of tiles and then type the name in the Name group field that appears above the group.
-
When you have the Start layout that you want your users to see, use the Export-StartLayout cmdlet in Windows PowerShell to export the Start layout to an .xml file.
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 for instructions.
To export the Start layout to an .xml file
-
From Start, open Windows PowerShell.
-
At the Windows PowerShell command prompt, enter the following command:
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 cmdlet does not 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="http://schemas.microsoft.com/Start/2014/LayoutModification"> <DefaultLayoutOverride> <StartLayoutCollection> <defaultlayout:StartLayout GroupCellWidth="6" xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout"> <start:Group Name="Life at a glance" xmlns:start="http://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>
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 cannot 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
-
Open the layout .xml file. There is a
<DefaultLayoutOverride>
element. AddLayoutCustomizationRestrictionType="OnlySpecifiedGroups"
to the DefaultLayoutOverride element as follows:<DefaultLayoutOverride LayoutCustomizationRestrictionType="OnlySpecifiedGroups">
-
Save the file and apply using any of the deployment methods.
Related topics
- Manage Windows 10 Start and taskbar layout
- Configure Windows 10 taskbar
- Add image for secondary tiles
- Start layout XML for desktop editions of Windows 10 (reference)
- Customize Windows 10 Start and taskbar with Group Policy
- Customize Windows 10 Start and taskbar with provisioning packages
- Customize Windows 10 Start and tasbkar with mobile device management (MDM)
- Changes to Start policies in Windows 10