Windows - Software - Install Attendant Pro (32-Bit)

What the Attendant Pro deployment Worklet does

This Automox Worklet™ deploys the latest 32-bit release of Attendant Pro to Windows endpoints across your contact-center and reception workstations. The evaluation script inspects the Windows registry uninstall hives for any DisplayName that matches Attendant Pro, and remediation runs only when the application is absent. The Worklet skips endpoints that already have Attendant Pro installed, so a recurring policy stays quiet on the workstations that pass and pulls the MSI only on the ones where the uninstall key is missing.

The remediation script downloads the current 32-bit MSI from the Automox installer cache, runs msiexec.exe with /qn and /norestart, and writes a verbose install log to C:\ProgramData\amagent\Attendant_Pro_x86_install.log for later review. The script removes the staged installer after the msiexec process exits so the endpoint does not retain stale binaries in the staging directory. Detection covers HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall, so the Worklet behaves correctly on both 32-bit and 64-bit Windows.

Because the Worklet is FixNow compatible, you can trigger Attendant Pro deployment to a specific endpoint on demand from the Automox console without waiting for the next scheduled policy window. That fits new-hire provisioning, a quick reinstall after a reimage, or covering a contact-center workstation that lost the application during an OS upgrade.

Why deploy Attendant Pro through Automox

Attendant Pro is a Microsoft Teams attendant console that receptionists, help desks, and contact-center agents use to route, transfer, and park calls. When the application is missing or out of date on an agent's workstation, callers wait longer in the queue. Automating the MSI install scales past the few-dozen-seat ceiling of touch deployment and pulls every endpoint onto a consistent version. The 32-bit build keeps Attendant Pro compatible with 32-bit Office installations, third-party plug-ins, and older accessibility tools that still ship 32-bit binaries.

Bind this Worklet to the contact-center workstation group on the Automox console. The msiexec install completes on agents working from a branch office, a remote home network, or a hot-desk laptop that only checks in twice a day. The Automox agent drives the install in place of an on-site operator.

How Attendant Pro deployment works

1. Evaluation phase: On 64-bit Windows, the Worklet opens HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall through the .NET Registry64 view and walks every subkey, reading the DisplayName value and matching it against Attendant Pro. It then queries HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall with Get-ChildItem and Get-ItemProperty filtered on DisplayName. On 32-bit Windows, only HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall is checked. If any matching entry exists in any of those hives, the endpoint is marked compliant and remediation is skipped. If no entry exists, evaluation exits 1 and remediation runs on the next policy execution.

2. Remediation phase: The Worklet pulls Attendant_Pro_x86.msi from the Automox installer cache at api.automox.com/api/cache using System.Net.WebClient and stages it in the script's working directory. It then invokes msiexec.exe with /i, /qn, /norestart, and /l*v pointing at C:\ProgramData\amagent\Attendant_Pro_x86_install.log. The script waits up to 300 seconds for msiexec to exit, then deletes the staged MSI. A timeout or a non-zero exit code other than 3010 exits 1 and the failure is written to the install log; an exit code of 0 or 3010 exits 0.

Attendant Pro deployment requirements

• Windows 10, Windows 11, or Windows Server 2016 and later, on workstation or server endpoints

• Local Administrator rights for the Automox agent (the default agent context already meets this)

• Outbound HTTPS reachability from the endpoint to api.automox.com so the MSI can be downloaded from the Automox installer cache

• Free disk space in C:\ProgramData\amagent\ for the staged MSI and the install log (allow at least 200 MB headroom)

• Windows Installer service (msiexec.exe) registered and not in a stuck or repairing state on the endpoint

• Choose this 32-bit Worklet for endpoints standardized on 32-bit Office or Attendant Pro plug-ins; use the 64-bit Attendant Pro Worklet for endpoints fully on 64-bit binaries

Expected state after Attendant Pro deployment

After remediation, Attendant Pro (32-bit) is installed under C:\Program Files (x86)\Attendant Pro\ on 64-bit Windows or C:\Program Files\Attendant Pro\ on 32-bit Windows. The application appears in Settings → Apps → Installed apps and in Control Panel → Programs and Features with publisher metadata visible. The corresponding uninstall entry is written to HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall on 64-bit Windows or HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall on 32-bit Windows, and the next evaluation run flags the endpoint compliant without re-running remediation.

Validate the deployment by opening Attendant Pro on the endpoint and confirming the version number against the vendor release page, or by running Get-ItemProperty on the relevant uninstall hive and reading the DisplayVersion value. For audit evidence, capture the contents of C:\ProgramData\amagent\Attendant_Pro_x86_install.log alongside the Automox activity log for the policy run. Exit code 0 from msiexec indicates a clean install and exit code 3010 indicates a successful install that requests a reboot, both of which the Worklet treats as success. Common failure codes include 1603 (fatal install error, often a permissions or pending-reboot issue) and 1618 (another install is already in progress). The Worklet does not force a reboot, so schedule a separate restart policy if Attendant Pro requests one to finish registering its Office add-in.