Provisioning packages are still a new method of deploying changes to Windows clients. They are created using the Windows Configuration Designer included in the Windows Assessment and Deployment Kit (Windows ADK). You can also download the standalone Windows Configuration Designer app from the Microsoft Store. The Microsoft Store Windows Configuration Designer app will auto-update to the latest version available.

Note Download Windows ADK

You can download the Windows ADK from the Microsoft website at https://learn.microsoft.com/windows-hardware/get-started/adk-install. Make sure to download the version of Windows ADK that matches the Windows 11 version you intend to deploy.

Provisioning packages use very small configuration files. These are used to modify existing Windows 11 installations and configure their runtime settings.

A provisioning package can perform a variety of functions, such as:

• Configure the computer name and user accounts
• Add the computer to a domain
• Upgrade the Windows 11 version, such as upgrading Windows 11 Home to Windows 11 Enterprise
• Configure the Windows user interface
• Add additional files or install apps
• Remove installed software
• Configure network connectivity settings
• Install certificates
• Implement security settings
• Reset Windows 11
• Run PowerShell scripts

To create a provisioning package, you should complete the Windows Configuration Designer installation process using either Windows ADK or the Microsoft Store. Once done, you can create and deploy your provisioning packages. Start by opening Windows Configuration Designer. On the Start page displayed in Figure 1-1, select the option that best describes the type of provisioning you want. If you’re unsure, choose the Advanced provisioning tile.

FIGURE 1-1 Creating a new provisioning package

Use the following procedure to create your provisioning package to deploy a universal line of business (LOB) app:

1. Select the Advanced provisioning tile.
2. In the New project wizard, on the Enter project details page, enter the name and a meaningful description for your provisioning package. For example, enter Deploy LOB App1 and then select Next.
3. On the Choose which settings to view and configure page, select All Windows desktop editions, and select Next.
4. On the Import a provisioning package (optional) page, select Finish. (You can use this option to import settings from a previously configured package that mostly, but not entirely, meets your needs.)
5. On the Available customizations page, in View, select All settings, and then expand Runtime settings, as displayed in Figure 1-2.
6. On the Available customizations page, in the navigation pane, expand UniversalAppInstall, and then select DeviceContextApp.
7. In the details pane, in the PackageFamilyName text box, enter a name for this collection of apps. For example, enter LOB App1.
8. Select the PackageFamilyName: LOB App1 node.
9. In the ApplicationFile text box, select Browse. Navigate to and select the .appx file representing your app, as displayed in Figure 1-2.

FIGURE 1-2 Available customizations for your provisioning package

10. In the File menu, select Save and note the location of the saved provisioning package file.

You have created a customization for your app and are now ready to deploy this customization by applying the provisioning package.

Note Deploy Powershell Scripts from Provisioning Packages

If you want to use PowerShell scripts with provisioning packages, select All Windows Desktop Editions on the Choose Which Settings To View And Configure page within Advanced Provisioning. You can then add command line files in the Runtime Settings\ProvisioningCommands\DeviceContext area of the available customizations. To view detailed information about using scripts in provisioning packages, visit this Microsoft website at https://learn.microsoft.com/windows/configuration/provisioning-packages/provisioning-script-to-install-app.