Windows MDM Policies (aka Profiles)

What

Windows Configuration policies allow you to define attributes on your Windows endpoints, such as "Bluetooth is not allowed".  These configuration policies are similar to what you may have done in the past through Group Policy objects.

When/Why

We'll use configuration policies whenever we want to configure Windows 10 endpoints for items that ease setup, or restrict device usage.  Policies will always be a work in progress as more and more are added to the platform over time.  In this iteration we start with the critical core policy settings.

How

How can a FileWave administrator create the Windows policies?

1. Open the FileWave WebAdmin → navigate to payloads → click on + button.

2. Click Create Windows Profile.

    

   

    

3. Here you will be able to select what should be controlled by the profile and the settings for those controls

    

   

    

4. Once the profile is saved you can deploy the profile to the single or group of devices using deployment view.

5. The FileWave server will reach to the devices using push model via WNS (Windows notification services.)

6. The device will now reach to the FileWave server and sync for the assigned payloads. In case the device is not online there is a caching mechanism built to retry for several hours. 

You have now deployed a profile to manage settings!

Note that at this time there is no method for seeing command history in the FileWave admin with regard to policy installation, but this feature will be coming in a later update.

Related Content

Pre-Requisites of Windows MDM Setup

Part 1) Win MDM Setup: Custom FileWave Client

Part 2) Win MDM Setup: Setting up Terms

Part 3) Win MDM Setup: The Portal App

Manually Enrolling a Device Into FileWave Windows MDM

Integrating with AutoPilot

Reset Windows Device through a script (Recipe)

Windows MDM Policies (aka Profiles)