The Duress Alert rollout playbook: from one server to every screen in an afternoon.
1. Pick the server PC
Any always-on Windows machine, reception or practice-management PC. No rack, no VM. The app restarts with Windows.
2. Build your configuration once
Client names (name each machine for its room or desk), server address, hotkey, notifications and escalation, set on the server. The server then generates client installers with all of it baked in.
3. Install the clients
Self-install in about 5 min/computer, or silent MSI via GPO/Intune/your RMM, we use NinjaOne ourselves. Standard msiexec /i DuressAlertClient.msi /qn works out of the box; every setting can also be passed as an MSI property for scripted rollouts.
4. Mac and shared desktops
Mac clients (provisioning bundle prepared by the server) join the same local alert path; RDS/published desktops get their own rollout path so every user has a button, certified on Windows Server 2025.
5. Pilot, then go live
Start with reception plus two responders. Run a drill. Then push to everyone, a full site is typically live within a week of starting.
6. Drill and evidence
Run a monthly drill; export the raise → respond → reset history for your incident register or safety committee.
Packaging a rollout from the server
Tell us about your site.
Tell us your team size and setting, and we’ll show you how Duress Alert works on your own desks and what a rollout looks like. We get back to you quickly.
Download the rollout playbook (PDF)
Name and email only. Request it here.
Start your free 21-day trial, covering up to 25 computers. Configure it and roll it out across your site, at no cost. The trial itself is free. If you go ahead afterwards, we can set it up with you for a one-off A$99. When you move from the trial to a full licence there is no extra effort, everything you have set up simply keeps running. No payment details to start, and you can cancel anytime.
