Plan a Windows Device Refresh with FileWave

A Windows refresh can use Windows Autopilot, traditional imaging, an existing software-deployment tool, or a combination of those paths. Choose the provisioning method first, then plan FileWave enrollment, applications, policies, updates, and verification.

Choose the provisioning path

Windows Autopilot and FileWave Windows MDM

Windows Autopilot controls Microsoft's cloud provisioning and out-of-box experience. It is separate from FileWave Windows MDM and is not traditional re-imaging. Microsoft Entra automatic MDM enrollment routes the device to FileWave when the FileWave MDM application is configured and scoped for the user.

Use this path for new or reset devices that should join the correct Microsoft Entra tenant, receive an Autopilot deployment profile, and enroll in FileWave during setup. Before a large refresh, manually enroll one device to verify the FileWave Server URL, certificate, Microsoft Entra application, discovery URL, and MDM user scope.

Traditional Windows imaging

Use imaging when devices require a prepared Windows image, must be restored from bare metal, or cannot use the intended Autopilot and MDM enrollment path.

• Network Imaging / IVS is FileWave's supported bare-metal imaging workflow.
• PSImage - Alternative Windows Imaging uses Microsoft tools in a more customizable workflow created by FileWave Professional Services. Plan additional ownership and testing if you choose this do-it-yourself path.

Install the FileWave Client

FileWave Windows MDM enrollment and the native FileWave Client are separate parts of Windows management. For an existing fleet, deploy a custom FileWave Client MSI manually, through Group Policy, with your current management system, or as part of provisioning.

• FileWave Server 16.4.0 and later: Build and download the custom Client installer in FileWave Central.
• FileWave Server 16.3.3 and earlier: Build it at custom.filewave.com.

See Build Custom FileWave Client and Booster Installers for the exact builder and package checks. Test the MSI on a representative device and confirm that it checks in to the intended Server before wider deployment.

Plan identity and group targeting

Use Microsoft Entra ID for the Autopilot and Windows MDM enrollment path. If the organization also uses on-premises Active Directory, FileWave directory integration can make users and groups available for assignments and group-based targeting. Decide which directory owns users, groups, and device placement before the refresh so a newly enrolled device receives the intended content.

Plan applications and updates

• Deploy required applications and settings with Filesets, profiles, and Deployments.
• Use FileWave Software Updates for Windows operating-system updates and verify results in inventory.
• Use WinGet Filesets for supported third-party packages, or traditional Filesets when you need a private installer, extra files, or custom scripts.

Run a representative pilot

Test each planned hardware model, network location, and provisioning path before the refresh window. Verify FileWave Client check-in, Windows MDM enrollment when used, group placement, required profiles and Filesets, application installation, update status, and the rollback or recovery path. Record the expected end state so the refresh team can spot devices that stopped partway through the workflow.