diff --git a/windows/configuration/lock-down-windows-10-to-specific-apps.md b/windows/configuration/lock-down-windows-10-to-specific-apps.md index 19be7a1355..137e4c7f25 100644 --- a/windows/configuration/lock-down-windows-10-to-specific-apps.md +++ b/windows/configuration/lock-down-windows-10-to-specific-apps.md @@ -541,10 +541,10 @@ Use the Windows Configuration Designer tool to create a provisioning package. [L ### Apply provisioning package to device -Provisioning packages can be applied to client devices 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)." +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. +> [!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 diff --git a/windows/configuration/provisioning-packages/provisioning-apply-package.md b/windows/configuration/provisioning-packages/provisioning-apply-package.md index 9bf1a1c098..c54ca85972 100644 --- a/windows/configuration/provisioning-packages/provisioning-apply-package.md +++ b/windows/configuration/provisioning-packages/provisioning-apply-package.md @@ -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 ms.mktglfcycl: deploy ms.sitesec: library @@ -20,15 +20,15 @@ manager: dougeby - Windows 10 - Windows 11 -Provisioning packages can be applied to client devices during initial setup (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. ->[!TIP] ->In addition to the methods below, you can use the PowerShell cmdlet [Install-ProvisioningPackage](/powershell/module/provisioning/Install-ProvisioningPackage) with `-LogsDirectoryPath` to get logs for the operation. +> [!TIP] +> In addition to the methods below, you can use the PowerShell cmdlet [Install-ProvisioningPackage](/powershell/module/provisioning/Install-ProvisioningPackage) with `-LogsDirectoryPath` to get logs for the operation. ## During initial setup @@ -40,7 +40,7 @@ To apply a provisioning package from a USB drive during initial setup: 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 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**. ![What would you like to do?](../images/provisioning-oobe-choice.png) @@ -57,7 +57,7 @@ To apply a provisioning package from a USB drive during initial setup: ## After initial setup -Provisioning packages can be applied after initial setup during runtime by user initiation. This can be done trough Windows settings or by simply double-clicking a provisioning package. +Provisioning packages can be applied after initial setup through Windows settings or by simply double-clicking a provisioning package. ### Windows Settings @@ -73,7 +73,7 @@ Provisioning packages can be applied after initial setup during runtime by user ![Select and add a package.](../images/provisioning-runtime-add-package.png) -4. Provisioning packages require administrator privileges as it can modify system policies and run scripts at the system level. Ensure you trust the package you are installing before you accept the UAC prompt. Select **Yes**. +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**. ![Do you want to allow changes to your device?](../images/provisioning-runtime-UAC.png) @@ -83,13 +83,13 @@ Provisioning packages can be applied after initial setup during runtime by user ### Apply Directly -To apply a provisioning package directly such as from a USB drive, folder, network, or SharePoint site: +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 installation. +1. Navigate to the provisioning package and double-click it to begin the installation. ![Double-click package to being installation.](../images/provisioning-runtime-click-to-install.png) -2. Provisioning packages require administrator privileges as it can modify system policies and run scripts at the system level. Ensure you trust the package you are installing before you accept the UAC prompt. Select **Yes**. +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**. ![Do you want to allow changes to your device?](../images/provisioning-runtime-UAC.png) diff --git a/windows/configuration/set-up-shared-or-guest-pc.md b/windows/configuration/set-up-shared-or-guest-pc.md index 15f15d92e3..48be4e36b3 100644 --- a/windows/configuration/set-up-shared-or-guest-pc.md +++ b/windows/configuration/set-up-shared-or-guest-pc.md @@ -185,7 +185,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 device during initial setup or to a device that has already been set up. For more information, see "[Apply a provisioning package](./provisioning-packages/provisioning-apply-package.md)." +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.