Merge branch 'main' into Benny-54-ccleanup
Before Width: | Height: | Size: 20 KiB |
Before Width: | Height: | Size: 18 KiB |
BIN
windows/configuration/images/oobe.png
Normal file
After Width: | Height: | Size: 80 KiB |
Before Width: | Height: | Size: 11 KiB |
Before Width: | Height: | Size: 17 KiB |
BIN
windows/configuration/images/provisioning-oobe-choice.png
Normal file
After Width: | Height: | Size: 74 KiB |
After Width: | Height: | Size: 69 KiB |
BIN
windows/configuration/images/provisioning-oobe-installing.png
Normal file
After Width: | Height: | Size: 73 KiB |
BIN
windows/configuration/images/provisioning-runtime-UAC.png
Normal file
After Width: | Height: | Size: 62 KiB |
After Width: | Height: | Size: 37 KiB |
After Width: | Height: | Size: 78 KiB |
After Width: | Height: | Size: 72 KiB |
After Width: | Height: | Size: 108 KiB |
BIN
windows/configuration/images/provisioning-runtime-trust.png
Normal file
After Width: | Height: | Size: 84 KiB |
Before Width: | Height: | Size: 25 KiB |
Before Width: | Height: | Size: 42 KiB |
@ -404,7 +404,7 @@ Group accounts are specified using `<UserGroup>`. Nested groups aren't supported
|
||||
</Config>
|
||||
```
|
||||
|
||||
- Azure AD group: Use the group object ID from the Azure portal to uniquely identify the group in the Name attribute. You can find the object ID on the overview page for the group in **Users and groups** > **All groups**. Specify the group type as **AzureActiveDirectoryGroup**. The kiosk device must have internet connectivity when users that belong to the group sign in.
|
||||
- Azure AD group: Use the group object ID from the Azure portal to uniquely identify the group in the Name attribute. You can find the object ID on the overview page for the group in **Users and groups** > **All groups**. Specify the group type as **AzureActiveDirectoryGroup**. The kiosk device must have internet connectivity when users that belong to the group sign-in.
|
||||
|
||||
```xml
|
||||
<Config>
|
||||
@ -544,43 +544,11 @@ Use the Windows Configuration Designer tool to create a provisioning package. [L
|
||||
|
||||
### Apply provisioning package to device
|
||||
|
||||
Provisioning packages can be applied to a device during the first-run experience (out-of-box experience or "OOBE") and after ("runtime").
|
||||
|
||||
>[!TIP]
|
||||
>In addition to the methods below, you can use the PowerShell comdlet [install-provisioningpackage](/powershell/module/provisioning/Install-ProvisioningPackage) with `-LogsDirectoryPath` to get logs for the operation.
|
||||
|
||||
#### During initial setup, from a USB drive
|
||||
|
||||
1. Start with a computer on the first-run setup screen. If the PC has gone past this screen, reset the PC to start over. To reset the PC, go to **Settings** > **Update & security** > **Recovery** > **Reset this PC**.
|
||||
|
||||

|
||||
|
||||
2. Insert the USB drive. Windows Setup will recognize the drive and ask if you want to set up the device. Select **Set up**.
|
||||
|
||||

|
||||
|
||||
3. The next screen asks you to select a provisioning source. Select **Removable Media** and tap **Next**.
|
||||
|
||||

|
||||
|
||||
4. Select the provisioning package (\*.ppkg) that you want to apply, and tap **Next**.
|
||||
|
||||

|
||||
|
||||
5. Select **Yes, add it**.
|
||||
|
||||

|
||||
|
||||
#### After setup, from a USB drive, network folder, or SharePoint site
|
||||
|
||||
1. Sign in with an admin account.
|
||||
2. Insert the USB drive to a desktop computer, navigate to **Settings** > **Accounts** > **Access work or school** > **Add or remove a provisioning package** > **Add a package**, and select the package to install. For a provisioning package stored on a network folder or on a SharePoint site, navigate to the provisioning package and double-click it to begin installation.
|
||||
Provisioning packages can be applied to a device during initial setup (out-of-box experience or "OOBE") and after ("runtime"). For more information, see [Apply a provisioning package](./provisioning-packages/provisioning-apply-package.md).
|
||||
|
||||
> [!NOTE]
|
||||
> If your provisioning package doesn't include the assigned access user account creation, make sure the account you specified in the multi-app configuration XML exists on the device.
|
||||
|
||||

|
||||
|
||||
### Use MDM to deploy the multi-app configuration
|
||||
|
||||
Multi-app kiosk mode is enabled by the [AssignedAccess configuration service provider (CSP)](/windows/client-management/mdm/assignedaccess-csp). Your MDM policy can contain the assigned access configuration XML.
|
||||
|
@ -1,6 +1,6 @@
|
||||
---
|
||||
title: Apply a provisioning package (Windows 10/11)
|
||||
description: Provisioning packages can be applied to a device during the first-run experience (OOBE) and after ("runtime").
|
||||
description: Provisioning packages can be applied to a device during initial setup (OOBE) and after ("runtime").
|
||||
ms.prod: w10
|
||||
author: aczechowski
|
||||
ms.author: aaroncz
|
||||
@ -18,40 +18,82 @@ manager: dougeby
|
||||
- Windows 10
|
||||
- Windows 11
|
||||
|
||||
Provisioning packages can be applied to client devices during the first-run experience (out-of-box experience or "OOBE") and after ("runtime").
|
||||
Provisioning packages can be applied to a device during initial setup (out-of-box experience or "OOBE") and after ("runtime").
|
||||
|
||||
>[!NOTE]
|
||||
> [!NOTE]
|
||||
>
|
||||
> - Applying a provisioning package to a desktop device requires administrator privileges on the device.
|
||||
> - You can interrupt a long-running provisioning process by pressing ESC.
|
||||
|
||||
## During initial setup, from a USB drive
|
||||
> [!TIP]
|
||||
> In addition to the following methods, you can use the PowerShell cmdlet [Install-ProvisioningPackage](/powershell/module/provisioning/Install-ProvisioningPackage) with `-LogsDirectoryPath` to get logs for the operation.
|
||||
|
||||
1. Start with a computer on the first-run setup screen. If the PC has gone past this screen, reset the PC to start over. To reset the PC, go to **Settings** > **Update & security** > **Recovery** > **Reset this PC**.
|
||||
## During initial setup
|
||||
|
||||

|
||||
To apply a provisioning package from a USB drive during initial setup:
|
||||
|
||||
2. Insert the USB drive. Windows Setup will recognize the drive and ask if you want to set up the device. Select **Set up**.
|
||||
1. Start with a device on the initial setup screen. If the device has gone past this screen, reset the device to start over. To reset, go to **Settings** > **System** > [**Recovery**](ms-settings:recovery) > **Reset this PC**.
|
||||
|
||||

|
||||
:::image type="content" source="../images/oobe.png" alt-text="The first screen when setting up a new PC.":::
|
||||
|
||||
3. The next screen asks you to select a provisioning source. Select **Removable Media** and select **Next**.
|
||||
2. Insert the USB drive. If nothing happens when you insert the USB drive, press the Windows key five times.
|
||||
|
||||

|
||||
- If there is only one provisioning package on the USB drive, the provisioning package is applied. See step 5.
|
||||
- If there is more than one provisioning package on the USB drive, Windows setup will recognize the drive and ask how you want to provision the device. Select **Install provisioning package** and select **Next**.
|
||||
|
||||
4. Select the provisioning package (`.ppkg`) that you want to apply, and select **Next**.
|
||||
:::image type="content" source="../images/provisioning-oobe-choice.png" alt-text="What would you like to do?":::
|
||||
|
||||

|
||||
3. Select the provisioning package (`.ppkg`) that you want to apply, and select **Yes**.
|
||||
|
||||
5. Select **Yes, add it**.
|
||||
:::image type="content" source="../images/provisioning-oobe-choose-package.png" alt-text="Choose a package.":::
|
||||
|
||||

|
||||
4. The selected provisioning package will install and apply to the device.
|
||||
|
||||
## After setup, from a USB drive, network folder, or SharePoint site
|
||||
:::image type="content" source="../images/provisioning-oobe-installing.png" alt-text="Setting up your PC.":::
|
||||
|
||||
Insert the USB drive to a desktop computer, navigate to **Settings** > **Accounts** > **Access work or school** > **Add or remove a provisioning package** > **Add a package**, and select the package to install. For a provisioning package stored on a network folder or on a SharePoint site, navigate to the provisioning package and double-click it to begin installation.
|
||||
5. Wait for the device to load and begin applying the provisioning package. Once you see "You can remove your removable media now!" you can remove your USB drive. Windows will continue provisioning the device.
|
||||
|
||||

|
||||
## After initial setup
|
||||
|
||||
Provisioning packages can be applied after initial setup through Windows settings or by simply double-clicking a provisioning package.
|
||||
|
||||
### Windows Settings
|
||||
|
||||
1. Insert the USB drive, then navigate to **Settings** > **Accounts** > [**Access work or school**](ms-settings:workplace) > **Add or remove a provisioning package** > **Add a package**.
|
||||
|
||||
:::image type="content" source="../images/provisioning-runtime-manage-packages.png" alt-text="Add or remove a provisioning package.":::
|
||||
|
||||
2. Choose the method you want to use, such as **Removable Media**.
|
||||
|
||||
:::image type="content" source="../images/provisioning-runtime-choose-package.png" alt-text="Choose a method.":::
|
||||
|
||||
3. Select the provisioning package (`.ppkg`) that you want to apply, and select **Add**.
|
||||
|
||||
:::image type="content" source="../images/provisioning-runtime-add-package.png" alt-text="Select and add a package.":::
|
||||
|
||||
4. Provisioning packages require administrator privileges as they can modify system policies and run scripts at the system level. Ensure you trust the package you are installing before accepting the UAC prompt. Select **Yes**.
|
||||
|
||||
:::image type="content" source="../images/provisioning-runtime-UAC.png" alt-text="Do you want to allow changes to your device?":::
|
||||
|
||||
5. The provisioning runtime will ask if the package is from a source you trust. Verify that you are applying the correct package and that it is trusted. Select **Yes, add it**.
|
||||
|
||||
:::image type="content" source="../images/provisioning-runtime-trust.png" alt-text="Do you trust this package?":::
|
||||
|
||||
### Apply Directly
|
||||
|
||||
To apply a provisioning package directly, such as from a USB drive, folder, network, or SharePoint site:
|
||||
|
||||
1. Navigate to the provisioning package and double-click it to begin the installation.
|
||||
|
||||
:::image type="content" source="../images/provisioning-runtime-click-to-install.png" alt-text="Double-click package to being installation.":::
|
||||
|
||||
2. Provisioning packages require administrator privileges as they can modify system policies and run scripts at the system level. Ensure you trust the package you are installing before accepting the UAC prompt. Select **Yes**.
|
||||
|
||||
:::image type="content" source="../images/provisioning-runtime-UAC.png" alt-text="Do you want to allow changes to your device?":::
|
||||
|
||||
3. The provisioning runtime will ask if the package is from a source you trust. Verify that you are applying the correct package and that it is trusted. Select **Yes, add it**.
|
||||
|
||||
:::image type="content" source="../images/provisioning-runtime-trust.png" alt-text="Do you trust this package?":::
|
||||
|
||||
## Related articles
|
||||
|
||||
|
@ -62,7 +62,7 @@ Shared PC mode exposes a set of customizations to tailor the behavior to your re
|
||||
|:---|:---|
|
||||
| EnableSharedPCMode | Set as **True**. If this is not set to **True**, shared PC mode is not turned on and none of the other settings apply. This setting controls this API: [IsEnabled](/uwp/api/windows.system.profile.sharedmodesettings) </br></br>Some of the remaining settings in **SharedPC** are optional, but we strongly recommend that you also set `EnableAccountManager` to **True**. |
|
||||
| AccountManagement: AccountModel | This option controls how users can sign-in on the PC. Choosing domain-joined will enable any user in the domain to sign-in. <br/><br/>Specifying the guest option will add the **Guest** option to the sign-in screen and enable anonymous guest access to the PC. <br/><br/> - **Only guest** allows anyone to use the PC as a local standard (non-admin) account.<br/> - **Domain-joined only** allows users to sign in with an Active Directory or Azure AD account.<br/>- **Domain-joined and guest** allows users to sign in with an Active Directory, Azure AD, or local standard account. |
|
||||
| AccountManagement: DeletionPolicy | - **Delete immediately** will delete the account on sign-out. <br/><br/>- **Delete at disk space threshold** will start deleting accounts when available disk space falls below the threshold you set for **DiskLevelDeletion**, and it will stop deleting accounts when the available disk space reaches the threshold you set for **DiskLevelCaching**. Accounts are deleted in order of oldest accessed to most recently accessed. <br/><br/>Example: The caching number is 50 and the deletion number is 25. Accounts will be cached while the free disk space is above 25%. When the free disk space is less than 25% (the deletion number) at a maintenance period, accounts will be deleted (oldest last used first) until the free disk space is above 50% (the caching number). Accounts will be deleted immediately at sign off of an account if free space is under the deletion threshold and disk space is very low, regardless if the PC is actively in use or not. <br/>- **Delete at disk space threshold and inactive threshold** will apply the same disk space checks as noted above, but also delete accounts if they have not signed in within the number of days specified by **InactiveThreshold** |
|
||||
| AccountManagement: DeletionPolicy | - **Delete immediately** will delete the account on sign-out. <br/><br/>- **Delete at disk space threshold** will start deleting accounts when available disk space falls below the threshold you set for **DiskLevelDeletion**, and it will stop deleting accounts when the available disk space reaches the threshold you set for **DiskLevelCaching**. Accounts are deleted in order of oldest accessed to most recently accessed. <br/><br/>Example: The caching number is 50 and the deletion number is 25. Accounts will be cached while the free disk space is above 25%. When the free disk space is less than 25% (the deletion number) at a maintenance period, accounts will be deleted (oldest last used first) until the free disk space is above 50% (the caching number). Accounts will be deleted immediately at sign-off of an account if free space is under the deletion threshold and disk space is very low, regardless if the PC is actively in use or not. <br/>- **Delete at disk space threshold and inactive threshold** will apply the same disk space checks as noted above, but also delete accounts if they have not signed in within the number of days specified by **InactiveThreshold** |
|
||||
| AccountManagement: DiskLevelCaching | If you set **DeletionPolicy** to **Delete at disk space threshold**, set the percent of total disk space to be used as the disk space threshold for account caching. |
|
||||
| AccountManagement: DiskLevelDeletion | If you set **DeletionPolicy** to **Delete at disk space threshold**, set the percent of total disk space to be used as the disk space threshold for account deletion. |
|
||||
| AccountManagement: InactiveThreshold | If you set **DeletionPolicy** to **Delete at disk space threshold and inactive threshold**, set the number of days after which an account that has not signed in will be deleted. |
|
||||
@ -82,7 +82,7 @@ Shared PC mode exposes a set of customizations to tailor the behavior to your re
|
||||
|
||||
You can configure Windows to be in shared PC mode in a couple different ways:
|
||||
|
||||
- Mobile device management (MDM): Shared PC mode is enabled by the [SharedPC configuration service provider (CSP)](/windows/client-management/mdm/sharedpc-csp). To setup a shared device policy for Windows client in Intune, complete the following steps:
|
||||
- Mobile device management (MDM): Shared PC mode is enabled by the [SharedPC configuration service provider (CSP)](/windows/client-management/mdm/sharedpc-csp). To set up a shared device policy for Windows client in Intune, complete the following steps:
|
||||
|
||||
1. Sign in to the [Microsoft Endpoint Manager admin center](https://go.microsoft.com/fwlink/?linkid=2109431).
|
||||
|
||||
@ -182,30 +182,7 @@ You can configure Windows to be in shared PC mode in a couple different ways:
|
||||
|
||||
### Apply the provisioning package
|
||||
|
||||
You can apply the provisioning package to a PC during initial setup or to a PC that has already been set up.
|
||||
|
||||
**During initial setup**
|
||||
|
||||
1. Start with a PC on the setup screen.
|
||||
|
||||

|
||||
|
||||
2. Insert the USB drive. If nothing happens when you insert the USB drive, press the Windows key five times.
|
||||
|
||||
- If there is only one provisioning package on the USB drive, the provisioning package is applied.
|
||||
|
||||
- If there is more than one provisioning package on the USB drive, the **Set up device?** message displays. Click **Set up**, and select the provisioning package that you want to install.
|
||||
|
||||

|
||||
|
||||
3. Complete the setup process.
|
||||
|
||||
|
||||
**After setup**
|
||||
|
||||
On a desktop computer, navigate to **Settings** > **Accounts** > **Work access** > **Add or remove a management package** > **Add a package**, and selects the package to install.
|
||||
|
||||

|
||||
Provisioning packages can be applied to a device during initial setup (out-of-box experience or "OOBE") and after ("runtime"). For more information, see [Apply a provisioning package](./provisioning-packages/provisioning-apply-package.md).
|
||||
|
||||
> [!NOTE]
|
||||
> If you apply the setup file to a computer that has already been set up, existing accounts and data might be lost.
|
||||
@ -214,7 +191,7 @@ On a desktop computer, navigate to **Settings** > **Accounts** > **Work ac
|
||||
|
||||
* We recommend no local admin accounts on the PC to improve the reliability and security of the PC.
|
||||
|
||||
* When a PC is set up in shared PC mode with the default deletion policy, accounts will be cached automatically until disk space is low. Then, accounts will be deleted to reclaim disk space. This account management happens automatically. Both Azure AD and Active Directory domain accounts are managed in this way. Any accounts created through **Guest** and **Kiosk** will be deleted automatically at sign out.
|
||||
* When a PC is set up in shared PC mode with the default deletion policy, accounts will be cached automatically until disk space is low. Then, accounts will be deleted to reclaim disk space. This account management happens automatically. Both Azure AD and Active Directory domain accounts are managed in this way. Any accounts created through **Guest** and **Kiosk** will be deleted automatically at sign-out.
|
||||
* On a Windows PC joined to Azure Active Directory:
|
||||
* By default, the account that joined the PC to Azure AD will have an admin account on that PC. Global administrators for the Azure AD domain will also have admin accounts on the PC.
|
||||
* With Azure AD Premium, you can specify which accounts have admin accounts on a PC using the **Additional administrators on Azure AD Joined devices** setting on the Azure portal.
|
||||
|