# Provisioning Package Enrollment

> Enroll Windows devices at scale using a Provisioning Package generated from a Smart Enrollment in Applivery — no user interaction required.

Source: https://docs.applivery.com/en/device-management/windows/enrollment/provisioning-package-enrollment/  •  Last updated: 2026-07-14

**Key topics:** Provisioning Package generation, Windows Smart Enrollment deployment, Bulk Windows MDM enrollment, Windows, Applivery, PPKG, Smart Enrollment, Provisioning Package

---

**TL;DR:** From a Smart Enrollment in Applivery, click the vertical dots, select View instructions, choose Provisioning Package, and click Create provisioning to generate a PPKG file ready to deploy on Windows devices.

A **Provisioning Package (PPKG)** is a deployment method that lets you enroll Windows devices automatically using a file generated directly from a [Windows Smart Enrollment](https://docs.applivery.com/en/device-management/windows/enrollment/smart-enrollment/). It is ideal for bulk or zero-touch deployments, since no manual URL entry or user credentials are needed on the device.

## How to generate and deploy a Provisioning Package

:::info
Before you start, make sure you have a [Windows Smart Enrollment](https://docs.applivery.com/en/device-management/windows/enrollment/smart-enrollment/) already configured.
:::

**Open the Smart Enrollment instructions**

In the [**Applivery Dashboard**](https://dashboard.applivery.io/), go to the **Automation** section 1 and select **Smart Enrollments** 2. From the left-hand menu, choose **Windows** 3 as the platform.

Click the three vertical dots 4 next to the Smart Enrollment you want to use and select **View instructions** 5.

![provisioning package](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/04fddb99-cb0c-4220-b08b-b6b4b483b184.png)

**Generate the Provisioning Package**

In the side panel, select **Provisioning Package** 6 and click the **\+ Create provisioning** button 7.

:::warning
Devices enrolled through this package will be initially linked to a single user or department. You can reassign them later using a script. You can create as many Provisioning Packages as you need from the same enrollment.
:::

**Apply the package to your devices**

Once the package is generated, click **Select** 8.

![create and select ppkg](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/f245477a-0821-4af4-8181-84b872368662.png)

The on-screen instructions will guide you through applying the PPKG file to your Windows devices.

* * *

## Enrolling during OOBE (Out-of-Box Experience)

When you apply a Provisioning Package during the Windows **OOBE** — the initial setup wizard that runs on a brand-new or freshly reset device — enrollment needs an extra step to stick.

During OOBE, Windows runs under a temporary session (`defaultuser0`) that is **not persistent**. If you enroll straight from that stage, the Applivery enrollment gets tied to that temporary session and is silently removed once the session is cleaned up — leaving the device unenrolled.

To avoid this, you split the process into two stages:

-   **OOBE stage**: the user account and everything unrelated to Applivery enrollment is set up on the device.
    
-   **After the first Windows login**: the actual Applivery enrollment runs, attached to a **persistent** user, so it survives reboots.
    

:::info
This procedure is only required when the PPKG is applied from the **OOBE wizard**. For devices that are already activated (past the initial setup), you only need the single `Enroll.ppkg` described in the section above.
:::

**Create the Smart Enrollment and export Enroll.ppkg**

In the [**Applivery Dashboard**](https://dashboard.applivery.io/), create a **Windows Smart Enrollment**, select **Anonymous login**, and add a policy.

![Anonymous](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/e3ed0e2a-a89e-4415-b5ee-93c1e9801e1a.png)

Generate a Provisioning Package following the dashboard instructions (as in the section above), including **only the Workplace configuration to enroll**.

Export it as `Enroll.ppkg` to your desktop. Note that a `.cat` catalog file with the same name is created alongside it.

![configure windows configuration designer](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/316fa9e3-81c7-4633-a7de-13bb2cb3f51b.png)

**Build the wrapper package in Windows Configuration Designer**

Create a **new provisioning package project** in **Windows Configuration Designer** and set up the following.

**a) Create the user account**

Create a user account and make sure it belongs to the local **Administrators** group. If it is a standard user, enrollment after RunOnce will fail due to permissions.

![admin user](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/af549dab-c8f3-45d3-ad10-7c1cdfda3fac.png)

**b) Add Enroll.ppkg to the delivered files**

Scroll down to the **Folders** node under **Runtime settings** and expand it. Files added here are delivered to `C:\Users\Public\Documents` on the target device. Add the `Enroll.ppkg` and its `.cat` catalog file, then click **Add**. They will appear inside the **Runtime** tree.

![folders](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/7f5464e1-4106-4c31-9485-c5c4a7fb1b0b.png)

**c) Configure OOBE**

Scroll down to the **OOBE** node and configure it as shown.

![node configuration](https://docs.applivery.com/int/_r2/media/09ac0a4e-3ad8-478f-9f15-3474973eec71/1fa609fa-753e-48e6-a746-c92a0c8d4601.png)

**d) Add the RunOnce provisioning command**

This is the key step. Scroll down to **Provisioning Commands** and expand it. Click **Device Context** and select the **CommandLine** field from the left tree.

Add the following one-liner command:

```
reg add "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce" /v "AppliveryOOBEEnroll" /t REG_SZ /d "powershell.exe -ExecutionPolicy Bypass -Command \"Install-ProvisioningPackage -PackagePath C:\Users\Public\Documents\Enroll.ppkg -QuietInstall -ForceInstall\"" /f
```

**Export and deploy**

Export the PPKG, and you are good to go.

The command injects a **RunOnce** entry into the Windows Registry that runs silently right after the user's first login following the OOBE provisioning. This attaches the Applivery enrollment to the persistent user who has just logged in.

To confirm, go to **Settings > Accounts > Access work or school** — the **Applivery** account will already be listed. From that point, enrollment persists across reboots.