Skip to main content

Windows MDM Policies (aka Profiles)

What

Windows configuration policies let you define and enforce settings on Windows devices that are enrolled in MDM. They are the Windows equivalent of a profile and cover settings such as BitLocker, Bluetooth, connectivity, cloud and storage, and device restrictions.

When/Why

Use a Windows profile when you want to apply Windows policy settings through FileWave to MDM-enrolled devices. Before creating the profile, complete Windows MDM setup and enroll a pilot Windows device. Installing the FileWave Client alone does not establish Windows MDM enrollment. Confirm that the device details report Windows MDM before targeting the policy.

How

To create a Windows profile in FileWave Anywhere, use the configuration action available in your version. The screenshots below show the older Create Profile interface; current Profiles and Policies in FileWave Anywhere instructions use Create Configuration.

  1. Open Payloads.

  2. Select Create Configuration and choose the Windows MDM policy type. In the older interface shown below, select Create Profile, then Create Windows Profile.

    Make New Profile.jpg

  3. Configure the profile settings you want to enforce. The General category is mandatory, the profile must include at least one payload category before it can be saved, and the Installation Scope can be set to System or User.

    Profile.jpg

  4. Save the profile, then create a Deployment for the pilot device or test group. Review the selected settings and targets, coordinate other administrators’ pending work, and update the model to publish the change.

  5. After the pilot device receives the policy, check the intended setting on that Windows device. Saving a profile or increasing the server model number does not prove Windows applied the setting.

Expand the Deployment after the pilot has the expected settings. If a setting did not apply, check Windows MDM enrollment and device communication before extending the rollout. Keep the profile’s installation scope and the target Windows version in mind when investigating the result.

FileWave does not currently show policy installation command history for Windows MDM profiles in the admin UI.