Windows - Software Lifecycle - Install Dialpad Machine-Wide

What the Dialpad deployment Worklet does

This Automox Worklet™ deploys the Dialpad Machine-Wide Installer to Windows endpoints across your fleet. The Worklet first inspects the Windows uninstall registry to determine whether Dialpad Machine-Wide Installer is already present. If the entry exists, the endpoint is marked compliant and the Worklet exits without taking action.

When Dialpad is missing, the Worklet provisions a cache directory under %ProgramData%\amagent\WorkletCache\WSE-766, downloads the architecture-appropriate MSI from Dialpad's Google Cloud Storage bucket, and runs msiexec.exe in silent mode with the ALLUSERS=1 property so the install applies machine-wide. On 64-bit Windows the Worklet pulls DialpadSetup_x64.msi; on 32-bit Windows it pulls DialpadSetup.msi. The installer file is removed after the install completes.

Because Dialpad's installer finalizes per-user configuration on the next interactive login, the Worklet exits 0 as soon as msiexec returns 0 or 3010 (success or success-with-reboot-required). The Dialpad client appears in Add or Remove Programs as Dialpad Machine-Wide Installer and resolves into C:\Program Files\Dialpad once a user logs in and the per-user stub completes.

Why deploy Dialpad at fleet scale

Dialpad is the daily phone and meetings client for many end users. When it is missing on a new hire's machine or on a freshly reimaged laptop, the help desk receives a ticket quickly. Manually walking users through the MSI download, the silent install flags, and the ALLUSERS=1 toggle does not scale past a handful of endpoints, and per-user installs leave a second profile on the same laptop without Dialpad at all. The machine-wide MSI addresses both problems, but only if it actually lands on every endpoint.

Schedule this Worklet once against a Windows endpoint group and the Dialpad client lands on every member of the group with the correct architecture, the correct silent flags, and the correct machine-wide scope.

How Dialpad machine-wide deployment works

1. Evaluation phase: The Worklet opens HKLM with the registry view that matches the endpoint's bitness, then walks both SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall. It matches each subkey's DisplayName against Dialpad Machine-Wide Installer. A hit in either hive returns exit code 0 and marks the endpoint compliant. A miss returns exit code 2 and flags the endpoint for remediation.

2. Remediation phase: The script creates %ProgramData%\amagent\WorkletCache\WSE-766, downloads either DialpadSetup_x64.msi or DialpadSetup.msi from storage.googleapis.com using System.Net.WebClient, and invokes msiexec.exe with /i, /qn, /norestart, /l*v for verbose logging, and the ALLUSERS=1 property. A five-minute Wait-Process timeout guards against a hung install. Exit codes 0 and 3010 both count as success; any other code is logged to ${appName}_install.log inside the cache directory and re-thrown. After a successful install the MSI is deleted from the cache directory.

Dialpad deployment requirements

• Windows 7 or later for workstations, Windows Server 2012 or later for servers (both 32-bit and 64-bit supported)

• .NET Framework 4.5 or higher available to PowerShell on the endpoint

• TLS 1.2 enabled for outbound HTTPS so System.Net.WebClient can reach storage.googleapis.com

• Outbound 443 to storage.googleapis.com (x64 MSI under /dialpad_native/x64/, x86 MSI under /dialpad_native/)

• Local administrator rights for the Automox agent (default agent context already satisfies this)

• Approximately 250 MB of free space under %ProgramData% to hold the MSI during install, plus the installed footprint under C:\Program Files\Dialpad

Expected Dialpad state after deployment

After remediation, Dialpad Machine-Wide Installer appears in Add or Remove Programs and a product-code subkey with a DisplayName value of Dialpad Machine-Wide Installer lives under HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall (or its Wow6432Node sibling on 64-bit systems). The application binaries are staged under C:\Program Files\Dialpad. The MSI is not visible in the WorkletCache directory because the script deletes it as soon as msiexec.exe exits with 0 or 3010. The dialpad.exe user-mode client does not launch yet; per-user setup is deferred until the next interactive login, which is by design for machine-wide MSIs.

Validate the deployment by running Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object DisplayName -like 'Dialpad*' against the endpoint and confirming a DisplayName, DisplayVersion, and UninstallString are present. The companion install log at %ProgramData%\amagent\WorkletCache\WSE-766\DialpadMachine-WideInstaller_install.log captures the msiexec output for audit. Subsequent Worklet runs detect the existing installation and exit 0 without re-downloading the MSI, so the policy is safe to leave on a recurring schedule against the Windows endpoint group. The Worklet installs Dialpad only when it is absent; it does not upgrade existing installations. To roll out a newer Dialpad build, uninstall the current package out-of-band and let the next evaluation flag the endpoint for re-deployment.