Hi @ccarpenter ,
In the command given in that linked article:
duo-win-login-4.0.7.exe /S /V" /qn IKEY="■■■■■■■■■■■■■■■■■■■■XX" SKEY="xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx" HOST="■■■■■■■■■■■■■■■■■■■■■■■■■■■■" AUTOPUSH="#1" FAILOPEN="#1" SMARTCARD="#1" RDPONLY="#0""
The you would replace the
DIXXXXX... value after
IKEY= with your integration key and the
xxxxx value after
SKEY= with your secret key. If you have an endpoint management tool that can run batch commands you can use that (or the msiexec equivalent in that same article) in a job you push to your workstations to install Duo for Windows Logon.
If your workstations are AD domain joined, you could also deploy Duo for Windows Logon via software install GPO.
ETA it occurs to me that you might want to mass-deploy Duo to Windows systems using a unique Duo application for each workstation (therefore a different ikey/skey value needed for each one). There is not a great way to do this, other than some advanced scripting.