How to deploy screen-break software with Microsoft Intune

For managed Windows estates, the clean rollout order is: licence the people, apply the organisation configuration, then install the application.

Published 7 September 2026 · 20-20-20 Vision LTD

For organisations managing Windows endpoints with Microsoft Intune, 20-20-20 Vision for Workplaces can be deployed without asking every employee to download an application, configure it independently and enter a licence key themselves.

The rollout order matters

Licence the people → apply organisation settings → install the application.

Why deploy centrally?

Manual installation can be reasonable for a handful of employees. Across a larger Windows estate it creates unnecessary variation: people may forget to install the software, postpone it, or configure reminders differently from the organisation's intended defaults.

IT professional using a laptop and multiple computer displays — Central deployment is about consistency: apply the organisation configuration first, then roll the application out across the managed Windows estate.

Assign licences

Installing Workplaces does not automatically allocate a licence. Assign the intended users in the Workplaces dashboard before rollout; Workplaces licences belong to people rather than devices.

Download the deployment files

Obtain the per-machine MSI installer, the administrative template and your organisation key from the Workplaces dashboard.

Decide your organisation settings

Choose defaults such as reminder interval, rest duration, working hours, quiet periods, pausing behaviour, snooze allowances and optional adherence reporting.

Import the ADMX template into Intune

For cloud-managed estates, import the supplied ADMX as an imported administrative template, configure the organisation licence setting first, then the other settings you need, and assign the profile to the appropriate device groups.

Confirm the settings are present

Before installing across the wider estate, verify on a pilot device that the organisation key and expected policy values have arrived.

Prepare the MSI for Intune

Prepare the Workplaces MSI as a Win32 package using Microsoft’s Win32 Content Prep Tool and upload the resulting .intunewin package.

Add the application to Intune

Create a Windows app (Win32), upload the prepared package, and configure app information, requirements and detection rules according to your normal endpoint-management standards.

Choose the assignment

Use Required deployment or make the application Available through Company Portal according to your organisation's normal software-distribution policy.

Pilot before wider deployment

Confirm configuration, installation, centrally managed values, licensed-user recognition and expected dashboard information on a small set of devices.

Roll out to the wider workforce

Once the pilot succeeds, expand assignments to the intended device groups. Users do not need to download an installer, enter a licence key or perform an elevated installation themselves.

Silent installation

The Workplaces MSI installs silently with:

msiexec /i "20-20-20-Vision-Teams-<version>.msi" /qn /norestart

Replace <version> with the release you downloaded from your dashboard. Installation requires administrator rights because Workplaces is installed per machine. The MSI file name still carries this tier's previous name, Teams, because the build has not been renamed yet. The application itself runs as the signed-in user and does not require runtime elevation.

Security and application-control review

The Security & IT Reference documents the current executables, runtime privileges, network behaviour, privacy model and application-control considerations.

Use the live Deployment Guide as the source of truth

Installer names, registry paths, ADMX categories, licence sequencing and troubleshooting can change as the product evolves. The Deployment Guide is kept current with each release and is the reference for low-level rollout detail.

Use the maintained rollout instructions

The Deployment Guide is the source of truth for the current installer, registry paths, ADMX categories, verification steps and troubleshooting.

Open the Deployment Guide Review 20-20-20 Vision for Workplaces Security & IT Reference