Configure Windows MDM Notification Type to Use Polling

In restricted or offline environments, skip WNS setup by using polling-based notifications. This lets Windows devices check in with the MDM server on a schedule—no push credentials needed.

Overview

In secure or offline environments where Windows Notification Services (WNS) can't be used, you can switch to polling-based notifications. This setup lets Windows devices check in with the MDM server at regular intervals without needing push services. It’s ideal for air-gapped or high-security networks, ensuring reliable device management without internet-based notifications.

Advantages

  • Eliminates dependency on WNS credentials.
  • Suitable for air-gapped or offline environments.
  • Ensures reliable MDM communication via periodic polling.
  • Simple configuration using environment variables.

Environment variables

Variable Description
WIN_NOTIFICATION_TYPE This property defines how the Windows MDM server communicates with endpoints.

  • Options:

    • push (default): Requires WNS credentials.

    • poll: Devices check in at defined intervals.
WIN_POLLING_INTERVAL

Defines how often (in minutes) the enrolled device contacts the MDM server.

  • Default value: 360 (every 6 hours)

Applicable only when WIN_NOTIFICATION_TYPE is set to poll.

Steps to Configure Poll Notification

  1. Install BigFix MDM Service for Windows with dummy WNS credentials. Example wnscredentials.json
    {
"client_id": "ms-app://S-1-15-2-2204092716-2083274486",
"client_secret":"9dM8Q~.eCsYfNHQvUw5Ah",
"PFN":"60994testbgfx.wnsCredTest_n0qtg1pedrr"}
  2. Set the following values to enable polling:
    sh /opt/BESUEM/configure-mdm.sh WIN_NOTIFICATION_TYPE=poll WIN_POLLING_INTERVAL=10
  3. Restart the MCM containers to apply changes:
    cd /opt/BESUEM
sh service-mdm.sh restart
  4. Enroll Windows devices to apply the configuration.

The enrolled device will poll the MDM server every 10 minutes to check for pending actions such as commands, policies, or app installations.

Tip:
  • Use a reasonable polling interval (for example, 10–30 minutes) to balance responsiveness and server load.