# Configure the FileWave Client Package for Windows MDM

#### **What**

FileWave Windows MDM uses both Microsoft's MDM protocol and the native FileWave Client. MDM handles enrollment and policy commands, while the FileWave Client provides Filesets, inventory, and other client-based management.

#### **When/Why**

Configure the Windows Client enrollment package before enrolling Windows devices so the native FileWave Client can be installed automatically. FileWave Server 16.4.0 and later builds and stores the package directly in FileWave Central. FileWave Server 16.3.x and earlier requires a separately built custom MSI to be uploaded.

<p class="callout info">**Enrollment package:** This package is for new Client installations and Windows MDM enrollment. It is not the workflow for upgrading an already enrolled FileWave Client.</p>

#### **How**

<p class="callout warning">**Before you begin:** Confirm that the FileWave Server is healthy and backed up, uses a valid trusted certificate, has saved Preferences at least once, and has completed at least one Model Update. Saving Preferences creates required shared settings; Model Update creates the internal URLs used by this workflow.</p>

<table id="bkmrk-version-workflow"><thead><tr><th>FileWave Server version</th><th>Windows Client package workflow</th></tr></thead><tbody><tr><td>**16.4.0 and later**</td><td>Build the package on the **Mobile &gt; Windows** settings page in FileWave Central. No separate upload is required.</td></tr><tr><td>**16.3.x and earlier**</td><td>Build the MSI with the [Customer Installer Builder](https://custom.filewave.com/py/custom_client_win.py), then upload it on the **Mobile &gt; Windows** settings page.</td></tr></tbody></table>

##### FileWave Server 16.4.0 and later: Build the package in Central

1. Open FileWave Central, then open **Preferences**.
2. Open **Mobile &gt; Windows**.
3. Select **Show settings** and review the enrollment-package configuration.
4. Select **Build Windows client package**.
5. Wait for the page to show **Ready for Enrollment**. The package is now stored for Windows MDM enrollment; there is no separate upload step.
6. Use **Download Windows client package** only when you need a standalone copy of the generated installer.
7. Enable **Keep the package up to date** if FileWave should automatically regenerate the Windows Client package after a Server upgrade.

![FileWave Central 16.4 Windows settings with Build Windows client package, Download Windows client package, Show settings, and Keep the package up to date controls](https://kb.filewave.com/uploads/images/gallery/2026-07/scaled-1680-/XiFWnBzY4UOlucAE-hosted-server-16-4-windows-client-package.png)

*FileWave 16.4.0 and later builds and stores the Windows Client package directly on Mobile &gt; Windows.*

##### FileWave Server 16.3.x and earlier: Upload the custom MSI

1. Build the custom Windows Client MSI with the [Customer Installer Builder](https://custom.filewave.com/py/custom_client_win.py).
2. Open FileWave Central, then open **Preferences**.
3. Open **Mobile &gt; Windows**.
4. Upload the custom Client MSI as shown below.

![Pre-16.4 FileWave Central Windows settings for uploading a custom FileWave Client MSI](https://kb.filewave.com/uploads/images/gallery/2023-06/v4CcTNUdMTOkaFg9-upload-custom-msi.png)

*FileWave 16.3.x and earlier uses the upload workflow shown in this older interface.*