Build a tenant-bound package
- Open Emergency alerts (CAP), then Devices & Windows app.
- Optionally preassign the package to one location. Leave it blank to use IP mapping and the district-wide default.
- Optionally limit enrollments for a small pilot or location-specific deployment.
- Select Generate. The EXE and MSI are created together, usually within 5–10 minutes. The page checks the build automatically and displays both downloads when they are ready.
- Each download is a small ZIP wrapper produced by GitHub Actions. Extract it first; it contains the selected MSI or EXE plus SHA256SUMS.json for integrity verification.
- Keep the package inside the organization. Its short-lived bootstrap credential enrolls only into this tenant and cannot sign a user into the portal.
Interactive installation
- MSI: double-click the MSI and complete the Windows installer flow. The client is installed machine-wide and starts for signed-in users.
- EXE: the standalone EXE can be used for a controlled test. Use the MSI for managed, machine-wide production deployment.
- Install or assign the package before its enrollment window expires. Generate a fresh package for later deployment waves instead of reusing an old bootstrap credential.
Silent MDM installation
Use the exact MSI from the tenant package. The standard Windows Installer switches work with Microsoft Intune, Configuration Manager, Group Policy software installation, and other systems that can run an MSI in the device context.
- Upload the MSI as a line-of-business or Windows installer application.
- Install command: msiexec.exe /i "Organization-Intranet-Tools.msi" /qn /norestart
- Uninstall command: msiexec.exe /x {PRODUCT-CODE-FROM-MSI} /qn /norestart. Most MDM products read the product code directly from the MSI.
- Run in the device or SYSTEM context and target 64-bit Windows 10/11 devices.
- Use the installed-file rule for Dmtg.IntranetTools.exe under Program Files\DMTG Technologies, or the MSI product-code rule.
Pilot and verification
- Deploy to a small safety/IT pilot that includes single- and multi-monitor devices.
- Confirm each device appears under Enrolled Windows devices with the expected location and current client version.
- Send a controlled procedure to the pilot location, verify it appears on every monitor within five seconds, then end it and verify the takeover clears.
- Disconnect a pilot device from the network, reconnect it, and confirm the current active snapshot is reconciled.
- Expand deployment only after alert wording, sound, accessibility, firewall, proxy, and endpoint-security behavior are approved.
Updates and revocation
The client checks the protected API for current alerts and version information. Managed environments should keep the MSI assigned so endpoint management can enforce upgrades silently. Revoke a missing or retired device from the portal; it loses both realtime and polling access.