SafePrompt deploys across a managed fleet via Group Policy today, with Intune and SCCM available as a guided rollout — we'd rather tell you exactly what's field-tested and what isn't than have you find out mid-rollout.
Group Policy (GPO) — tested
A GPO startup-script deployment method is built and verified: a PowerShell script runs the same silent msiexec install used for a single machine, pushed via a domain startup script. This is the deployment path we recommend today.
Microsoft Intune — guided rollout
We have a written Intune deployment guide covering .intunewin packaging, install/detection commands, and assignment. It hasn't been field-validated against a real Intune tenant yet, so Enterprise customers get hands-on help from our team rather than a fully self-serve package.
SCCM — guided rollout
Same status as Intune: a correct application-deployment guide exists, not yet tested against a live SCCM site. Guided rollout with our team.
What this means for you
If GPO is your deployment mechanism, SafePrompt works today, tested. If you're an Intune or SCCM shop, Enterprise plans include working alongside your IT team to get the rollout right — not a black-box "just works" claim we haven't verified ourselves.
Contact sales to talk through your specific environment, or see Enterprise pricing.