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

What the Attendant Pro installer does

This Automox Worklet™ deploys the latest Attendant Pro (32-bit) version to Windows endpoints. The Worklet begins by checking if Attendant Pro is already installed in any form, examining both the 32-bit and 64-bit registry uninstall keys to detect existing installations.

If Attendant Pro is not found, the Worklet downloads the latest 32-bit installer directly from the Automox API and executes a silent installation using Windows Installer (msiexec.exe). The installation process logs detailed information to help troubleshoot any issues that may occur.

The Worklet handles both 32-bit and 64-bit Windows operating systems, automatically adjusting its registry checks based on the system architecture. This flexibility maintains consistent behavior regardless of your endpoint's OS version.

Why deploy Attendant Pro through Automox

Deploying Attendant Pro across your IT operations environment is critical for maintaining communication and coordination capabilities. Manual deployment is time-consuming and error-prone, especially across large endpoint populations. Using Automox eliminates these challenges by automating the entire process.

The Worklet maintains every endpoint with Attendant Pro can communicate with your organization's infrastructure. By automating the installation, you reduce manual touch points and human error. The Worklet also prevents duplicate installations by detecting both 32-bit and 64-bit versions, verifying you deploy only when needed.

FixNow compatibility means you can execute this installation immediately on demand through the Automox console, without waiting for scheduled remediations. This is particularly valuable when onboarding new endpoints or recovering systems where Attendant Pro was unintentionally removed.

How Attendant Pro deployment works

1. Evaluation phase: The Worklet checks the Windows registry Uninstall keys (both 64-bit and 32-bit locations) for existing Attendant Pro installations. It looks in HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ and HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\ depending on system architecture. If any version of Attendant Pro is found, the Worklet exits without further action.

2. Remediation phase: The Worklet downloads the latest 32-bit Attendant Pro installer from https://api.automox.com/api/cache?cmd=downloadLatestVersion&name=Attendant_Pro&os=Windows&arch=32. It then executes msiexec.exe with silent installation flags (/norestart, /qn), logs output to C:\ProgramData\amagent\Attendant_Pro_x86_install.log, and waits up to five minutes for installation completion. After successful installation, the Worklet removes the installer file.

Attendant Pro deployment requirements

• Windows 7, Windows 10, Windows 11, or Windows Server 2008 R2 and later

• Local Administrator rights required to modify registry and install software

• Internet connectivity to download installer from Automox API

• Sufficient disk space in C:\ProgramData\amagent\ for temporary installer storage

• Windows Installer service (msiexec.exe) available on the endpoint

Expected state after Attendant Pro deployment

After the Worklet completes successfully, Attendant Pro (32-bit) is installed and ready to use on your endpoint. The application appears in Control Panel's Programs and Features (Add/Remove Programs) list under the name "Attendant Pro". The installation process creates necessary registry entries and application files in the default installation directory.

You can verify successful installation by checking the log file at C:\ProgramData\amagent\Attendant_Pro_x86_install.log. The Worklet automatically cleans up the temporary installer file after installation completes. Subsequent Worklet executions will skip remediation since Attendant Pro is now detected as installed.

How to validate install attendant pro (32-bit) changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for install attendant pro (32-bit).

2. Confirm Automox activity logs show successful completion and exit code 0.

3. Verify endpoint state using checks aligned to evaluation script logic, such as Write-Output, Get-ChildItem, Get-ItemProperty.

4. Validate remediation effects from script operations such as Get-ChildItem, Get-ItemProperty, Where-Object, then rerun evaluation for compliance.