Skip to main content

Duo Authentication for Windows Logon Uninstallation

Summary

This internal monitor identifies computers that are no longer in scope for Duo Authentication for Windows Logon and queues them for automatic cleanup. It runs against all online Windows machines and checks the effective DUO_Auth_Deployment setting (Computer → Location → Client fallback). When the resolved value is Disable, it then verifies whether any remnants remain:

If either is present, the monitor returns Uninstall. The attached alert template △ Custom - Execute Script - Duo Authentication for Windows Logon Uninstallation immediately launches the Duo Authentication for Windows Logon Uninstallation script. That script removes the application and deletes the remote monitor without opening tickets.

Important: Computers where DUO_Auth_Deployment is not set (left empty at all levels) are not detected. Only an explicit Disable selection triggers uninstallation.

This monitor replaces the deprecated ProVal - Production - Uninstall DUO internal monitor.

EDFs and Detection Logic

EDFs Used

The monitor relies solely on the DUO_Auth_Deployment Extra Data Fields. All are in the Duo_Auth section.

NameLevelTypeOptionsSectionDescription
DUO_Auth_DeploymentClientDropdownWorkstations · Servers · Both · DisableDuo_AuthDefault deployment scope for all computers under this client.
DUO_Auth_DeploymentLocationDropdownWorkstations · Servers · Both · DisableDuo_AuthOverrides the client setting for a specific location.
DUO_Auth_DeploymentComputerDropdownWorkstations · Servers · Both · DisableDuo_AuthOverrides all higher levels for a specific computer.

How the Decision is Made

  1. Resolve the effective deployment – the monitor uses COALESCE(NULLIF(…), …) to walk the Computer → Location → Client chain, picking the first non‑empty value.
  2. Only act on explicit Disable – if the resolved value is exactly 'Disable', the machine is a candidate for cleanup. If all levels are empty (NULL), the computer is ignored.
  3. Check for remnants – for each candidate, the monitor checks:
  4. Return action – if either the application or the remote monitor exists, the computer is returned with TestValue = 'Uninstall'. If both are gone, the computer is already clean and is not returned.

Example Scenarios

Effective DeploymentApp Installed?Remote Monitor Present?ActionReason
DisableYesYesUninstallBoth remnants exist; full cleanup needed.
DisableYesNoUninstallApplication still present even though monitor was already removed.
DisableNoYesUninstallOnly the monitor remains; script will remove it.
DisableNoNoNone (skipped)Machine is already clean – nothing to do.
Not set (NULL)YesYesNone (skipped)Deployment was never configured; no uninstall should be performed.
Workstations / Servers / BothAnyAnyNone (skipped)Deployment is still enabled; uninstall logic does not apply.

Dependencies

Target

Global

Alert Template

△ Custom - Execute Script - Duo Authentication for Windows Logon Uninstallation

Changelog

2026-07-07

  • Initial version of the document.
  • Replaces the deprecated ProVal - Production - Uninstall DUO internal monitor.
  • Only triggers when deployment is explicitly Disable and remnants exist.