The WingMDM model

The core of WingMDM’s model is in separating the device from the location it’s placed in.

All configuration is applied to a location:

• Which apps to install
• App configuration
• Home screen layout
• Wallpapers

A device is then assigned to a locations. At that point, it inherits all the configuration for that location, and WingMDM prepares to update it accordingly.

If a device is assigened to a different location, WingMDM works out the set of changes needed to adapt it to the new location - adding and removing app, setting a new wallpaper, rearranging the homescreen.

If a location is edited (for example, to add a new app or change the wallpaper), any device assigned to that location is re-evaulated and any changes are queued up ready for pushing.

Queueing changes

WingMDM takes the position that it will never make changes to a device without explicit confirmation.

This ensures that you can’t accidentally mess up an iPad that is currently in a guest area, and risk impacting guest experience.

Instead, when any changes are required on a device, WingMDM will list the pending changes, show details of those changes, and wait for you to push out those changes. This allows you to get changes ready, then wait for an appropriate window to roll them out.

Managing software updates

iOS updates can be difficult to manage - they require large downloads, and the iPad restarts spends a few minutes updating during which it can’t be used. Not what you want during a guest trip!

WingMDM instructs devices to delay software updates, then provides facilities for detecting necessary updates.

This allows you to detect updates and push them out during an appropriate window, instead of having guests see notifications on an iPad asking them to update.

Once an appropriate window is established, the updates can triggered on as many devices as you like simultaneously, without having to individually visit all the devices to trigger them.