Delete unused images and update documentation
@ -34,8 +34,8 @@
|
||||
"education",
|
||||
"tier2"
|
||||
],
|
||||
"ms.prod": "windows-client",
|
||||
"ms.technology": "itpro-edu",
|
||||
"ms.subservice": "itpro-edu",
|
||||
"ms.service": "windows-client",
|
||||
"author": "paolomatarazzo",
|
||||
"ms.author": "paoloma",
|
||||
"manager": "aaroncz",
|
||||
|
@ -201,8 +201,6 @@ The following issues are known to affect student shared devices:
|
||||
|
||||
For student shared devices, it's recommended to configure the account management policies to automatically delete the user profiles after a certain period of inactivity or disk levels. For more information, see [Set up a shared or guest Windows device][WIN-3].
|
||||
|
||||
<a name='preferred-azure-ad-tenant-name'></a>
|
||||
|
||||
### Preferred Microsoft Entra tenant name
|
||||
|
||||
To improve the user experience, you can configure the *preferred Microsoft Entra tenant name* feature.\
|
||||
@ -210,8 +208,6 @@ When using preferred Microsoft Entra tenant name, the users bypass the disambigu
|
||||
|
||||
For more information about preferred tenant name, see [Authentication CSP - PreferredAadTenantDomainName][WIN-4].
|
||||
|
||||
<a name='identity-matching-in-azure-ad'></a>
|
||||
|
||||
### Identity matching in Microsoft Entra ID
|
||||
|
||||
When a Microsoft Entra user is federated, the user's identity from the IdP must match an existing user object in Microsoft Entra ID.
|
||||
@ -275,5 +271,5 @@ Update-MgUser -UserId alton@example.onmicrosoft.com -UserPrincipalName alton@exa
|
||||
|
||||
[WIN-1]: /windows/client-management/mdm/sharedpc-csp
|
||||
[WIN-2]: /windows/client-management/mdm/policy-csp-localpoliciessecurityoptions#localpoliciessecurityoptions-interactivelogon-donotdisplaylastsignedin
|
||||
[WIN-3]: /windows/configuration/shared-pc/set-up-shared-or-guest-pc
|
||||
[WIN-3]: /windows/configuration/set-up-shared-or-guest-pc
|
||||
[WIN-4]: /windows/client-management/mdm/policy-csp-authentication#preferredaadtenantdomainname
|
||||
|
@ -6,8 +6,6 @@ brand: windows
|
||||
|
||||
metadata:
|
||||
ms.topic: hub-page
|
||||
ms.prod: windows-client
|
||||
ms.technology: itpro-edu
|
||||
ms.collection:
|
||||
- education
|
||||
- tier1
|
||||
@ -78,7 +76,7 @@ productDirectory:
|
||||
links:
|
||||
- url: /education/windows/tutorial-school-deployment/configure-devices-overview
|
||||
text: Configure settings and applications with Microsoft Intune
|
||||
- url: /windows/configuration/shared-pc/set-up-shared-or-guest-pc
|
||||
- url: /windows/configuration/set-up-shared-or-guest-pc
|
||||
text: Set up a shared or guest Windows device
|
||||
- url: /education/windows/take-tests-in-windows
|
||||
text: Take tests and assessments in Windows
|
||||
|
@ -11,7 +11,7 @@ appliesto:
|
||||
|
||||
The Set up School PCs app builds a specialized provisioning package with school-optimized settings.
|
||||
|
||||
A key feature of the provisioning package is SharedPC mode. To learn about the technical framework of SharedPC mode, including the description of each setting, see the [Manage multi-user and guest Windows devices with Shared PC](/windows/configuration/shared-pc/shared-pc-technical) article.
|
||||
A key feature of the provisioning package is SharedPC mode. To learn about the technical framework of SharedPC mode, including the description of each setting, see the [Manage multi-user and guest Windows devices with Shared PC](/windows/configuration/shared-pc-technical) article.
|
||||
|
||||
## Shared PC Mode policies
|
||||
|
||||
@ -23,7 +23,7 @@ The following table outlines the policies applied to devices in SharedPC mode. I
|
||||
|
||||
In the table, *True* means that the setting is enabled, allowed, or applied. Use the **Description** column to help you understand the context for each setting.
|
||||
|
||||
For a more detailed look at the policies, see the Windows article [Set up shared or guest PC](/windows/configuration/shared-pc/set-up-shared-or-guest-pc#policies-set-by-shared-pc-mode).
|
||||
For a more detailed look at the policies, see the Windows article [Set up shared or guest PC](/windows/configuration/set-up-shared-or-guest-pc#policies-set-by-shared-pc-mode).
|
||||
|
||||
| Policy name | Default value | Description |
|
||||
|--|--|--|
|
||||
|
@ -110,6 +110,8 @@
|
||||
"✅ <a href=\"https://learn.microsoft.com/windows/release-health/supported-versions-windows-client\" target=\"_blank\">Windows 11</a>",
|
||||
"✅ <a href=\"https://learn.microsoft.com/windows/release-health/supported-versions-windows-client\" target=\"_blank\">Windows 10</a>"
|
||||
],
|
||||
"ue-v//**/*.md": "✅ <a href=\"https://learn.microsoft.com/windows/release-health/supported-versions-windows-client\" target=\"_blank\">Windows 10</a>",
|
||||
"cortana-at-work//**/*.md": "✅ <a href=\"https://learn.microsoft.com/windows/release-health/supported-versions-windows-client\" target=\"_blank\">Windows 10</a>",
|
||||
"wcd//**/*.md": ""
|
||||
}
|
||||
},
|
||||
|
Before Width: | Height: | Size: 6.8 KiB After Width: | Height: | Size: 6.8 KiB |
Before Width: | Height: | Size: 6.8 KiB After Width: | Height: | Size: 6.8 KiB |
Before Width: | Height: | Size: 7.9 KiB After Width: | Height: | Size: 7.9 KiB |
@ -112,35 +112,26 @@ When you set up a kiosk (also known as *assigned access*) in **Settings** for Wi
|
||||
**To set up assigned access in PC settings**
|
||||
|
||||
1. Go to **Start** > **Settings** > **Accounts** > **Other people**.
|
||||
|
||||
1. Select **Set up assigned access**.
|
||||
|
||||
1. Choose an account.
|
||||
|
||||
1. Choose an app. Only apps that can run above the lock screen will be available in the list of apps to choose from. For more information, see [Guidelines for choosing an app for assigned access](guidelines-for-assigned-access-app.md).
|
||||
|
||||
1. Close **Settings** - your choices are saved automatically, and will be applied the next time that user account signs in.
|
||||
|
||||
To remove assigned access, choose **Turn off assigned access and sign out of the selected account**.
|
||||
|
||||
<span id="powershell"/>
|
||||
|
||||
## Set up a kiosk using Windows PowerShell
|
||||
|
||||
App type:
|
||||
|
||||
- UWP
|
||||
|
||||
>App type:
|
||||
OS:
|
||||
|
||||
> - UWP
|
||||
>
|
||||
>OS:
|
||||
- Windows 10 Pro, Ent, Edu
|
||||
- Windows 11
|
||||
|
||||
> - Windows 10 Pro, Ent, Edu
|
||||
> - Windows 11
|
||||
>
|
||||
>Account type:
|
||||
Account type:
|
||||
|
||||
> - Local standard user
|
||||
- Local standard user
|
||||
|
||||

|
||||
|
||||
@ -179,19 +170,21 @@ Clear-AssignedAccess
|
||||
|
||||
## Set up a kiosk using the kiosk wizard in Windows Configuration Designer
|
||||
|
||||
>App type:
|
||||
> - UWP
|
||||
App type:
|
||||
|
||||
> - Windows desktop application
|
||||
>
|
||||
>OS:
|
||||
> - Windows 10 Pro version 1709+ for UWP only
|
||||
> - Windows 10 Ent, Edu for UWP and Windows desktop applications
|
||||
> - Windows 11
|
||||
>
|
||||
>Account type:
|
||||
> - Local standard user
|
||||
> - Active Directory
|
||||
- UWP
|
||||
- Windows desktop application
|
||||
|
||||
OS:
|
||||
|
||||
- Windows 10 Pro version 1709+ for UWP only
|
||||
- Windows 10 Ent, Edu for UWP and Windows desktop applications
|
||||
- Windows 11
|
||||
|
||||
Account type:
|
||||
|
||||
- Local standard user
|
||||
- Active Directory
|
||||
|
||||

|
||||
|
||||
|
@ -150,7 +150,7 @@ The following example allows Photos, Weather, Calculator, Paint, and Notepad app
|
||||
|
||||
##### StartPins
|
||||
|
||||
After you define the list of allowed applications, you can customize the Start layout for your kiosk experience. The easiest way to create a customized Start layout to apply to other Windows client devices is to set up the Start screen on a test device and then export the layout. Once you've decided, you can get the JSON needed for your kiosk configuration by following the steps to [Get the pinnedList JSON](customize-and-export-start-layout.md). If you opt to do this using the PowerShell command, make sure that the system you run the command on has the same file structure as the device on which you will apply the kiosk (the path to the allowed apps must be the same). At the end of this step, you should have a JSON pinnedList that looks something like the below.
|
||||
After you define the list of allowed applications, you can customize the Start layout for your kiosk experience. The easiest way to create a customized Start layout to apply to other Windows client devices is to set up the Start screen on a test device and then export the layout. Once you've decided, you can get the JSON needed for your kiosk configuration by following the steps to [Get the pinnedList JSON](../start/customize-and-export-start-layout.md). If you opt to do this using the PowerShell command, make sure that the system you run the command on has the same file structure as the device on which you will apply the kiosk (the path to the allowed apps must be the same). At the end of this step, you should have a JSON pinnedList that looks something like the below.
|
||||
|
||||
Add your pinnedList JSON into the StartPins tag in your XML file.
|
||||
|
||||
|
Before Width: | Height: | Size: 59 KiB After Width: | Height: | Size: 59 KiB |
Before Width: | Height: | Size: 23 KiB After Width: | Height: | Size: 23 KiB |
Before Width: | Height: | Size: 36 KiB After Width: | Height: | Size: 36 KiB |
Before Width: | Height: | Size: 70 KiB After Width: | Height: | Size: 70 KiB |
Before Width: | Height: | Size: 64 KiB After Width: | Height: | Size: 64 KiB |
@ -18,9 +18,7 @@ When you add an app in a Windows Configuration Designer wizard, the appropriate
|
||||
## Settings for UWP apps
|
||||
|
||||
- **License Path**: Specify the license file if it is an app from the Microsoft Store. This is optional if you have a certificate for the app.
|
||||
|
||||
- **Package family name**: Specify the package family name if you don't specify a license. This field will be autopopulated after you specify a license.
|
||||
|
||||
- **Required appx dependencies**: Specify the appx dependency packages that are required for the installation of the app
|
||||
|
||||
## Settings for Windows desktop applications
|
||||
|
@ -2,8 +2,6 @@
|
||||
title: Create a provisioning package with multivariant settings (Windows 10/11)
|
||||
description: Create a provisioning package with multivariant settings to customize the provisioned settings for defined conditions.
|
||||
ms.topic: article
|
||||
|
||||
ms.reviewer: gkomatsu
|
||||
ms.date: 12/31/2017
|
||||
---
|
||||
|
||||
|
@ -33,21 +33,15 @@ Windows Configuration Designer is available as an [app in the Microsoft Store](h
|
||||
Provisioning packages let you:
|
||||
|
||||
- Quickly configure a new device without going through the process of installing a new image.
|
||||
|
||||
- Save time by configuring multiple devices using one provisioning package.
|
||||
|
||||
- Quickly configure employee-owned devices in an organization without a mobile device management (MDM) infrastructure.
|
||||
|
||||
- Set up a device without the device having network connectivity.
|
||||
|
||||
Provisioning packages can be:
|
||||
|
||||
- Installed using removable media such as an SD card or USB flash drive.
|
||||
|
||||
- Attached to an email.
|
||||
|
||||
- Downloaded from a network share.
|
||||
|
||||
- Deployed in NFC tags or barcodes.
|
||||
|
||||
## What you can configure
|
||||
@ -104,20 +98,17 @@ WCD, simplified common provisioning scenarios.
|
||||
|
||||
WCD supports the following scenarios for IT administrators:
|
||||
|
||||
* **Simple provisioning** - Enables IT administrators to define a desired configuration in WCD and then apply that configuration on target devices. The simple provisioning wizard makes the entire process quick and easy by guiding an IT administrator through common configuration settings in a step-by-step manner.
|
||||
- **Simple provisioning** - Enables IT administrators to define a desired configuration in WCD and then apply that configuration on target devices. The simple provisioning wizard makes the entire process quick and easy by guiding an IT administrator through common configuration settings in a step-by-step manner.
|
||||
|
||||
[Learn how to use simple provisioning to configure Windows computers.](provision-pcs-for-initial-deployment.md)
|
||||
|
||||
* **Advanced provisioning (deployment of classic (Win32) and Universal Windows Platform (UWP) apps, and certificates)** - Allows an IT administrator to use WCD to open provisioning packages in the advanced settings editor and include apps for deployment on end-user devices.
|
||||
- **Advanced provisioning (deployment of classic (Win32) and Universal Windows Platform (UWP) apps, and certificates)** - Allows an IT administrator to use WCD to open provisioning packages in the advanced settings editor and include apps for deployment on end-user devices.
|
||||
|
||||
* **Mobile device enrollment into management** - Enables IT administrators to purchase off-the-shelf retail Windows devices and enroll them into mobile device management (MDM) before handing them to end users in the organization. IT administrators can use WCD to specify the management endpoint and apply the configuration on target devices by connecting them to a Windows PC (tethered deployment) or through an SD card. Supported management end-points include:
|
||||
- **Mobile device enrollment into management** - Enables IT administrators to purchase off-the-shelf retail Windows devices and enroll them into mobile device management (MDM) before handing them to end users in the organization. IT administrators can use WCD to specify the management endpoint and apply the configuration on target devices by connecting them to a Windows PC (tethered deployment) or through an SD card. Supported management end-points include:
|
||||
|
||||
- Microsoft Intune (certificate-based enrollment)
|
||||
|
||||
- AirWatch (password-string based enrollment)
|
||||
|
||||
- MobileIron (password-string based enrollment)
|
||||
|
||||
- Other MDMs (cert-based enrollment)
|
||||
|
||||
<!-- > [!NOTE] -->
|
||||
|
@ -22,73 +22,28 @@ This walkthrough describes how to include scripts in a Windows client provisioni
|
||||
|
||||
```ddf
|
||||
;*** MSDN Sample Source Code MakeCAB Directive file example
|
||||
|
||||
|
||||
;
|
||||
|
||||
|
||||
.OPTION EXPLICIT ; Generate errors on variable typos
|
||||
|
||||
|
||||
.set DiskDirectoryTemplate=CDROM ; All cabinets go in a single directory
|
||||
|
||||
|
||||
.Set MaxDiskFileCount=1000; Limit file count per cabinet, so that
|
||||
|
||||
|
||||
; scanning is not too slow
|
||||
|
||||
|
||||
.Set FolderSizeThreshold=200000 ; Aim for ~200K per folder
|
||||
|
||||
|
||||
.Set CompressionType=MSZIP
|
||||
|
||||
|
||||
;** All files are compressed in cabinet files
|
||||
|
||||
|
||||
.Set Cabinet=on
|
||||
|
||||
|
||||
.Set Compress=on
|
||||
|
||||
|
||||
;-------------------------------------------------------------------
|
||||
|
||||
|
||||
;** CabinetNameTemplate = name of cab
|
||||
|
||||
|
||||
;** DiskDirectory1 = output directory where cab will be created
|
||||
|
||||
|
||||
;-------------------------------------------------------------------
|
||||
|
||||
|
||||
.Set CabinetNameTemplate=tt.cab
|
||||
|
||||
|
||||
.Set DiskDirectory1=.
|
||||
|
||||
|
||||
;-------------------------------------------------------------------
|
||||
|
||||
|
||||
; Replace <file> with actual files you want to package
|
||||
|
||||
|
||||
;-------------------------------------------------------------------
|
||||
|
||||
|
||||
<file1>
|
||||
|
||||
|
||||
<file2>
|
||||
|
||||
|
||||
;*** <the end>
|
||||
|
||||
```
|
||||
|
||||
1. Use makecab to create the cab files.
|
||||
@ -115,7 +70,6 @@ Granular logging is not built in, so the logging must be built into the script i
|
||||
```log
|
||||
set LOGFILE=%SystemDrive%\HelloWorld.log
|
||||
echo Hello, World >> %LOGFILE%
|
||||
|
||||
```
|
||||
|
||||
### .exe example
|
||||
@ -176,8 +130,6 @@ You are allowed one **CommandLine** per provisioning package. The batch files sh
|
||||
|
||||
Here's a table describing this relationship, using the PowerShell example from above:
|
||||
|
||||
|
||||
|
||||
|ICD Setting | Value | Description |
|
||||
| --- | --- | --- |
|
||||
| ProvisioningCommands/DeviceContext/CommandLine | cmd /c PowerShell_Example.bat | The command line needed to invoke the orchestrator script. |
|
||||
@ -206,14 +158,14 @@ In Windows Configuration Designer, that is done by adding files under the `Provi
|
||||
|
||||
When you are done, [build the package](provisioning-create-package.md#build-package).
|
||||
|
||||
|
||||
|
||||
### Remarks
|
||||
|
||||
1. No user interaction or console output is supported via ProvisioningCommands. All work needs to be silent. If your script attempts to do any of the following it will cause undefined behavior, and could put the device in an unrecoverable state if executed during setup or the Out of Box Experience:
|
||||
a. Echo to console
|
||||
b. Display anything on the screen
|
||||
c. Prompt the user with a dialog or install wizard
|
||||
|
||||
1. Echo to console
|
||||
1. Display anything on the screen
|
||||
1. Prompt the user with a dialog or install wizard
|
||||
|
||||
1. When applied at first boot, provisioning runs early in the boot sequence and before a user context has been established; care must be taken to only include installers that can run at this time. Other installers can be provisioned via a management tool.
|
||||
1. If the device is put into an unrecoverable state because of a bad script, you can reset it using [recovery options in Windows client](https://support.microsoft.com/help/12415/windows-10-recovery-options).
|
||||
1. The CommandFile assets are deployed on the device to a temporary folder unique to each package.
|
||||
@ -244,4 +196,3 @@ When you are done, [build the package](provisioning-create-package.md#build-pack
|
||||
- [Windows Configuration Designer command-line interface (reference)](provisioning-command-line.md)
|
||||
- [PowerShell cmdlets for provisioning Windows client (reference)](provisioning-powershell.md)
|
||||
- [Create a provisioning package with multivariant settings](provisioning-multivariant.md)
|
||||
|
||||
|
@ -26,75 +26,34 @@ The registry-based settings that are revertible when a provisioning package is u
|
||||
- UniversalAppInstall / LaunchAppAtLogin
|
||||
- [Power](/previous-versions//dn953704(v=vs.85))
|
||||
- [TabletMode](../wcd/wcd-tabletmode.md)
|
||||
|
||||
- [Maps](../wcd/wcd-maps.md)
|
||||
|
||||
- [Browser](../wcd/wcd-browser.md)
|
||||
- [DeviceFormFactor](../wcd/wcd-deviceformfactor.md)
|
||||
|
||||
- [USBErrorsOEMOverride](/previous-versions/windows/hardware/previsioning-framework/mt769908(v=vs.85))
|
||||
|
||||
- [WeakCharger](../wcd/wcd-weakcharger.md)
|
||||
|
||||
|
||||
|
||||
## CSP-based settings
|
||||
|
||||
Here is the list of revertible settings based on configuration service providers (CSPs).
|
||||
|
||||
[ActiveSync CSP](/windows/client-management/mdm/activesync-csp)
|
||||
|
||||
[AppLocker CSP](/windows/client-management/mdm/applocker-csp)
|
||||
|
||||
[BrowserFavorite CSP](/windows/client-management/mdm/browserfavorite-csp)
|
||||
|
||||
[CertificateStore CSP](/windows/client-management/mdm/certificatestore-csp)
|
||||
|
||||
[ClientCertificateInstall CSP](/windows/client-management/mdm/clientcertificateinstall-csp)
|
||||
|
||||
[RootCATrustedCertificates CSP](/windows/client-management/mdm/rootcacertificates-csp)
|
||||
|
||||
[CM_CellularEntries CSP](/windows/client-management/mdm/cm-cellularentries-csp)
|
||||
|
||||
[CM_ProxyEntries CSP](/windows/client-management/mdm/cm-proxyentries-csp)
|
||||
|
||||
[CMPolicy CSP](/windows/client-management/mdm/cmpolicy-csp)
|
||||
|
||||
[CMPolicyEnterprise CSP](/windows/client-management/mdm/cmpolicyenterprise-csp)
|
||||
|
||||
[EMAIL2 CSP](/windows/client-management/mdm/email2-csp)
|
||||
|
||||
[EnterpriseAPN CSP](/windows/client-management/mdm/enterpriseapn-csp)
|
||||
|
||||
[EnterpriseDesktopAppManagement CSP](/windows/client-management/mdm/enterprisedesktopappmanagement-csp)
|
||||
|
||||
[EnterpriseModernAppManagement CSP](/windows/client-management/mdm/enterprisemodernappmanagement-csp)
|
||||
|
||||
[NAP CSP](/windows/client-management/mdm/nap-csp)
|
||||
|
||||
[PassportForWork CSP](/windows/client-management/mdm/passportforwork-csp)
|
||||
|
||||
[Provisioning CSP](/windows/client-management/mdm/provisioning-csp)
|
||||
|
||||
[SecureAssessment CSP](/windows/client-management/mdm/secureassessment-csp)
|
||||
|
||||
[VPN CSP](/windows/client-management/mdm/vpn-csp)
|
||||
|
||||
[VPNv2 CSP](/windows/client-management/mdm/vpnv2-csp)
|
||||
|
||||
[WiFi CSP](/windows/client-management/mdm/wifi-csp)
|
||||
|
||||
|
||||
|
||||
## Related articles
|
||||
|
||||
- [Provisioning packages for Windows client](provisioning-packages.md)
|
||||
- [How provisioning works in Windows client](provisioning-how-it-works.md)
|
||||
- [Install Windows Configuration Designer](provisioning-install-icd.md)
|
||||
- [Create a provisioning package](provisioning-create-package.md)
|
||||
- [Apply a provisioning package](provisioning-apply-package.md)
|
||||
- [Provision PCs with common settings for initial deployment (simple provisioning)](provision-pcs-for-initial-deployment.md)
|
||||
- [Use a script to install a desktop app in provisioning packages](provisioning-script-to-install-app.md)
|
||||
- [PowerShell cmdlets for provisioning Windows client (reference)](provisioning-powershell.md)
|
||||
- [Windows Configuration Designer command-line interface (reference)](provisioning-command-line.md)
|
||||
- [Create a provisioning package with multivariant settings](provisioning-multivariant.md)
|
||||
|
@ -147,21 +147,3 @@ If the Start layout is applied by Group Policy or MDM, and the policy is removed
|
||||
|
||||
> [!NOTE]
|
||||
> Office 2019 tiles might be removed from the Start menu when you upgrade Office 201. 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](../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)
|
||||
|
@ -37,7 +37,7 @@ This article shows you how to export an existing Start menu layout, and use the
|
||||
|
||||
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.":::
|
||||
:::image type="content" source="./images/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:
|
||||
|
||||
@ -91,31 +91,22 @@ If you're familiar with creating JSON files, you can create your own `LayoutModi
|
||||
|
||||
```json
|
||||
{
|
||||
|
||||
"pinnedList": [
|
||||
|
||||
{ "desktopAppId": "MSEdge" },
|
||||
|
||||
{ "desktopAppId": "Microsoft.Office.WINWORD.EXE.15" },
|
||||
|
||||
{ "packagedAppId": "Microsoft.WindowsStore_8wekyb3d8bbwe!App" },
|
||||
|
||||
{ "packagedAppId": "Microsoft.WindowsNotepad_8wekyb3d8bbwe!App" }
|
||||
|
||||
]
|
||||
|
||||
}
|
||||
|
||||
```
|
||||
|
||||
1. 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. |
|
||||
| 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
|
||||
|
||||
@ -153,26 +144,18 @@ To deploy this policy, the devices must be enrolled, and managed by your organiz
|
||||
|
||||
```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":::
|
||||
:::image type="content" source="./images/endpoint-manager-admin-center-custom-oma-uri-start-layout.png" alt-text="Custom OMA-URI settings to customize Start menu layout using pinnedList":::
|
||||
|
||||
1. Select **Save** > **Next** to save your changes.
|
||||
1. Configure the rest of the policy settings. For more specific information, see [Create a profile with custom settings](/mem/intune/configuration/custom-settings-configure).
|
||||
|
@ -21,8 +21,6 @@ In Windows 10 Pro, Windows 10 Enterprise, and Windows 10 Education, you can use
|
||||
>[!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:
|
||||
@ -32,8 +30,6 @@ Two features enable Start layout control:
|
||||
>[!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]
|
||||
@ -71,14 +67,3 @@ The following example uses Microsoft Intune to configure an MDM policy that appl
|
||||
|
||||
> [!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](../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)
|
||||
|
@ -112,16 +112,4 @@ Use the Windows Configuration Designer tool to create a provisioning package. [L
|
||||
- If you are done, click **Finish** to close the wizard and go back to the **Customizations Page**.
|
||||
|
||||
1. Copy the provisioning package to the target device.
|
||||
|
||||
1. 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](../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)
|
||||
|
@ -439,11 +439,12 @@ The following sample LayoutModification.xml shows how you can configure the Star
|
||||
|
||||
## 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 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.
|
||||
1. Include the file as part of your provisioning package.
|
||||
1. Create your multivariant target and reference the XML file within the target condition in the main customization XML file.
|
||||
@ -533,14 +534,3 @@ This should set the value of **StartLayout**. The setting appears in the **Selec
|
||||
>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](../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)
|
||||
|
@ -203,14 +203,3 @@ If your Start layout customization isn't applied as you expect, open the **Event
|
||||
|
||||
- **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](../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](../start/changes-to-start-policies-in-windows-10.md)
|
||||
|
@ -28,16 +28,19 @@ The following example shows how apps will be pinned: Windows default apps to the
|
||||

|
||||
|
||||
## Configure taskbar (general)
|
||||
*To configure the taskbar:
|
||||
|
||||
**To configure the taskbar:**
|
||||
1. Create the XML file
|
||||
|
||||
1. Create the XML file.
|
||||
- If you're also [customizing the Start layout](../start/customize-and-export-start-layout.md), use `Export-StartLayout` to create the XML, and then add the `<CustomTaskbarLayoutCollection>` section from [the following sample](#sample-taskbar-configuration-added-to-start-layout-xml-file) to the file.
|
||||
- If you're only configuring the taskbar, use [the following sample](#sample-taskbar-configuration-xml-file) to create a layout modification XML file.
|
||||
1. Edit and save the XML file. You can use [AUMID](../kiosk/find-the-application-user-model-id-of-an-installed-app.md) or Desktop Application Link Path to identify the apps to pin to the taskbar.
|
||||
- If you're only configuring the taskbar, use [the following sample](#sample-taskbar-configuration-xml-file) to create a layout modification XML file
|
||||
|
||||
1. Edit and save the XML file. You can use [AUMID](../kiosk/find-the-application-user-model-id-of-an-installed-app.md) or Desktop Application Link Path to identify the apps to pin to the taskbar
|
||||
|
||||
- Add `xmlns:taskbar="http://schemas.microsoft.com/Start/2014/TaskbarLayout"` to the first line of the file, before the closing \>.
|
||||
- Use `<taskbar:UWA>` and [AUMID](../kiosk/find-the-application-user-model-id-of-an-installed-app.md) to pin Universal Windows Platform apps.
|
||||
- Use `<taskbar:DesktopApp>` and Desktop Application Link Path to pin desktop applications.
|
||||
- Use `<taskbar:UWA>` and [AUMID](../kiosk/find-the-application-user-model-id-of-an-installed-app.md) to pin Universal Windows Platform apps
|
||||
- Use `<taskbar:DesktopApp>` and Desktop Application Link Path to pin desktop applications
|
||||
|
||||
1. Apply the layout modification XML file to devices using [Group Policy](../start/customize-windows-10-start-screens-by-using-group-policy.md) or a [provisioning package created in Windows Imaging and Configuration Designer (Windows ICD)](../start/customize-windows-10-start-screens-by-using-provisioning-packages-and-icd.md).
|
||||
|
||||
>[!IMPORTANT]
|
||||
|
@ -142,7 +142,7 @@ Use the following steps to add your XML file to a group policy, and apply the po
|
||||
|
||||
Your policy looks like the following policy:
|
||||
|
||||
:::image type="content" source="./images/customize-taskbar-windows-11/start-layout-group-policy.png" alt-text="Add your taskbar layout XML file to the Start Layout policy on Windows devices.":::
|
||||
:::image type="content" source="images/customize-taskbar-windows-11/start-layout-group-policy.png" alt-text="Add your taskbar layout XML file to the Start Layout policy on Windows devices.":::
|
||||
|
||||
The `User Configuration\Administrative Templates\Start Menu and Taskbar` policy includes other settings that control the taskbar. Some policies may not work as expected. Be sure to test your policies before broadly deploying them across your devices.
|
||||
|
||||
|
Before Width: | Height: | Size: 8.0 KiB After Width: | Height: | Size: 8.0 KiB |
@ -13,7 +13,8 @@ Use these settings to configure the out-of-box experience (OOBE) to set up HoloL
|
||||
|
||||
| Setting | Windows client | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: |
|
||||
| All settings | | | X | |
|
||||
| All settings | | | ✅ | |
|
||||
|
||||
| Setting | Description |
|
||||
| --- | --- |
|
||||
| PreferredRegion | Enter the [geographical location identifier](/windows/win32/intl/table-of-geographical-locations) for the region. |
|
||||
|
@ -18,24 +18,20 @@ Use KioskBrowser settings to configure Internet sharing.
|
||||
>[!NOTE]
|
||||
>To configure Kiosk Browser settings for Windows client, go to [Policies > KioskBrowser](wcd-policies.md#kioskbrowser).
|
||||
|
||||
Kiosk Browser settings | Use this setting to
|
||||
--- | ---
|
||||
Blocked URL Exceptions | Specify URLs that people can navigate to, even though the URL is in your blocked URL list. You can use wildcards. <br><br>For example, if you want people to be limited to `contoso.com` only, you would add `contoso.com` to blocked URL exception list and then block all other URLs.
|
||||
Blocked URLs | Specify URLs that people can't navigate to. You can use wildcards. <br><br>If you want to limit people to a specific site, add `https://*` to the blocked URL list, and then specify the site to be allowed in the blocked URL exceptions list.
|
||||
Default URL | Specify the URL that Kiosk Browser will open with. **Tip!** Make sure your blocked URLs don't include your default URL.
|
||||
Enable Home Button | Show a Home button in Kiosk Browser. Home will return the browser to the default URL.
|
||||
Enable Navigation Buttons | Show forward and back buttons in Kiosk Browser.
|
||||
Restart on Idle Time | Specify when Kiosk Browser should restart in a fresh state after an amount of idle time since the last user interaction.
|
||||
| Kiosk Browser settings | Use this setting to |
|
||||
|--|--|
|
||||
| Blocked URL Exceptions | Specify URLs that people can navigate to, even though the URL is in your blocked URL list. You can use wildcards. <br><br>For example, if you want people to be limited to `contoso.com` only, you would add `contoso.com` to blocked URL exception list and then block all other URLs. |
|
||||
| Blocked URLs | Specify URLs that people can't navigate to. You can use wildcards. <br><br>If you want to limit people to a specific site, add `https://*` to the blocked URL list, and then specify the site to be allowed in the blocked URL exceptions list. |
|
||||
| Default URL | Specify the URL that Kiosk Browser will open with. **Tip!** Make sure your blocked URLs don't include your default URL. |
|
||||
| Enable Home Button | Show a Home button in Kiosk Browser. Home will return the browser to the default URL. |
|
||||
| Enable Navigation Buttons | Show forward and back buttons in Kiosk Browser. |
|
||||
| Restart on Idle Time | Specify when Kiosk Browser should restart in a fresh state after an amount of idle time since the last user interaction. |
|
||||
|
||||
> [!IMPORTANT]
|
||||
> To configure multiple URLs for **Blocked URL Exceptions** or **Blocked URLs** in Windows Configuration Designer:
|
||||
>
|
||||
To configure multiple URLs for **Blocked URL Exceptions** or **Blocked URLs** in Windows Configuration Designer:
|
||||
|
||||
> 1. Create the provisioning package. When ready to export, close the project in Windows Configuration Designer.
|
||||
> 1. Open the customizations.xml file in the project folder (e.g C:\Users\name\Documents\Windows Imaging and Configuration Designer (WICD)\Project_18).
|
||||
|
||||
> 1. Insert the null character string in between each URL (e.g www.bing.com``www.contoso.com).
|
||||
|
||||
> 1. Save the XML file.
|
||||
> 1. Open the project again in Windows Configuration Designer.
|
||||
> 1. Export the package. Ensure you do not revisit the created policies under Kiosk Browser or else the null character will be removed.
|
||||
1. Create the provisioning package. When ready to export, close the project in Windows Configuration Designer.
|
||||
1. Open the customizations.xml file in the project folder (e.g C:\Users\name\Documents\Windows Imaging and Configuration Designer (WICD)\Project_18).
|
||||
1. Insert the null character string in between each URL (e.g https://www.bing.com``https://www.contoso.com).
|
||||
1. Save the XML file.
|
||||
1. Open the project again in Windows Configuration Designer.
|
||||
1. Export the package. Ensure you do not revisit the created policies under Kiosk Browser or else the null character will be removed.
|
||||
|
@ -13,7 +13,6 @@ Use SharedPC settings to optimize Windows devices for shared use scenarios, such
|
||||
|
||||
| Setting | Windows client | Surface Hub | HoloLens | IoT Core |
|
||||
| --- | :---: | :---: | :---: | :---: |
|
||||
|
||||
| All settings | ✅ | | | |
|
||||
|
||||
## AccountManagement
|
||||
|