mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-05-12 13:27:23 +00:00
Update cmdlet names in documentation
This commit is contained in:
Paolo Matarazzo
parent
7ee09637da
commit
530417384a
@ -181,7 +181,7 @@ Here you can find an example of Start layout that you can use as a reference:
|
||||
|
||||
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.
|
||||
- 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.
|
||||
@ -198,16 +198,14 @@ You can use a provisioning package that you create with Windows Configuration De
|
||||
|
||||
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.
|
||||
- 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.
|
||||
|
||||
|
||||
|
||||
### 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.
|
||||
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
|
||||
1. 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
|
||||
@ -281,24 +279,27 @@ Alternatively, you can configure devices using a [custom policy][MEM-1] with the
|
||||
|
||||
## User experience
|
||||
|
||||
:::row:::
|
||||
:::column span="2":::
|
||||
|
||||
After the settings are applied, sign in to the device. You'll see the Start layout that you configured:
|
||||
|
||||
::: zone pivot="windows-10"
|
||||
:::image type="content" source="images/windows-10.png" alt-text="Screenshot of the Windows 10 Start menu." border="false":::
|
||||
|
||||
> [!NOTE]
|
||||
> When you apply the policy setting, it results in a complete replacement of the existing layout, unless a partial Start layout is configured. This means users can't modify the Start layout once it's set by policy settings. If you want to allow users to modify the layout, use a partial Start layout instead.
|
||||
|
||||
::: zone-end
|
||||
|
||||
::: zone pivot="windows-11"
|
||||
:::image type="content" source="images/windows-11.png" alt-text="Screenshot of the Windows 11 Start menu." border="false":::
|
||||
|
||||
> [!NOTE]
|
||||
> When you configure the Start layout with policy settings, you overwrite the entire layout. Users can change the order of the pinned elements, pin, or unpin itmes. When a user signs in again, the Start layout specified in the policy setting is reapplied, without retaining any user changes.
|
||||
|
||||
:::column-end:::
|
||||
:::column span="2":::
|
||||
::: zone pivot="windows-10"
|
||||
:::image type="content" source="images/windows-10.png" alt-text="Screenshot of the Windows 10 Start menu." border="false" lightbox=".images/windows-10.png":::
|
||||
::: zone-end
|
||||
|
||||
::: zone pivot="windows-11"
|
||||
:::image type="content" source="images/windows-11.png" alt-text="Screenshot of the Windows 11 Start menu." border="false" lightbox=".images/windows-11.png":::
|
||||
::: zone-end
|
||||
|
||||
:::column-end:::
|
||||
:::row-end:::
|
||||
|
||||
## Next steps
|
||||
|
||||
- To learn more about the policy settings available to configure the Start menu using the Configuration Service Provider (CSP) and Group Policy (GPO), see [Start menu policy settings](policy-settings.md).
|
||||
|
||||
@ -226,7 +226,7 @@ The following example shows how to create a tile of the Web site's URL, which yo
|
||||
```
|
||||
|
||||
>[!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.
|
||||
>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
|
||||
@ -568,7 +568,7 @@ Example of secondary tiles in XML generated by Export-StartLayout:
|
||||
|
||||
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.
|
||||
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.
|
||||
1. Copy the contents of assets.xml into an online tool that escapes characters.
|
||||
|
||||
@ -57,7 +57,7 @@ This section describes the user data that USMT migrates by default, using the `M
|
||||
|
||||
> [!IMPORTANT]
|
||||
>
|
||||
> USMT doesn't migrate the Start menu layout. To migrate a user's Start menu, settings must be exported and then imported using the Windows PowerShell cmdlets **Export-StartLayout** and **Import-StartLayout**. For more information, see [USMT common issues](/troubleshoot/windows-client/deployment/usmt-common-issues#usmt-doesnt-migrate-the-start-layout).
|
||||
> USMT doesn't migrate the Start menu layout. To migrate a user's Start menu, settings must be exported and then imported using the Windows PowerShell cmdlets `Export-StartLayout` and **Import-StartLayout**. For more information, see [USMT common issues](/troubleshoot/windows-client/deployment/usmt-common-issues#usmt-doesnt-migrate-the-start-layout).
|
||||
|
||||
- **Folders from the All Users and Public profiles.** When the `MigUser.xml` file is specified, USMT also migrates the following from the **Public** profile in Windows:
|
||||
|
||||
@ -118,7 +118,7 @@ USMT migrates operating-system components to a destination computer. The followi
|
||||
1. Right-clicking on the Start menu and then selecting **Computer Management**.
|
||||
1. In the **Computer Management** console, expand **System tools** > **Local Users and Groups** > **Groups**.
|
||||
1. Inspect the individual groups in the results pane to see what users belong to what groups.
|
||||
|
||||
|
||||
The use of a **\<ProfileControl\>** section in the `Config.xml` file is required when running an offline migration.
|
||||
|
||||
- Microsoft Open Database Connectivity (ODBC) settings.
|
||||
@ -210,7 +210,7 @@ Also note the following items:
|
||||
|
||||
### Start menu layout
|
||||
|
||||
USMT doesn't migrate the Start menu layout. To migrate a user's Start menu, settings must be exported and then imported using the Windows PowerShell cmdlets **Export-StartLayout** and **Import-StartLayout**. For more information, see [USMT common issues](/troubleshoot/windows-client/deployment/usmt-common-issues#usmt-doesnt-migrate-the-start-layout).
|
||||
USMT doesn't migrate the Start menu layout. To migrate a user's Start menu, settings must be exported and then imported using the Windows PowerShell cmdlets `Export-StartLayout` and **Import-StartLayout**. For more information, see [USMT common issues](/troubleshoot/windows-client/deployment/usmt-common-issues#usmt-doesnt-migrate-the-start-layout).
|
||||
|
||||
### User profiles from Active Directory to Microsoft Entra ID
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user