Windows - Software Lifecycle - Install Dialpad Machine-Wide

What the Dialpad Machine-Wide installer does

This Automox Worklet™ installs the latest version of Dialpad (Machine-Wide) on Windows endpoints. The Worklet first checks whether Dialpad is already installed by scanning both 32-bit and 64-bit registry locations, accounting for system architecture differences. If the application is not found, the Worklet proceeds with installation.

During installation, the Worklet creates a cache directory, downloads the appropriate MSI installer based on endpoint architecture (x64 or x86), and executes a silent installation with the ALLUSERS parameter to deploy Dialpad machine-wide. The installer file is automatically removed after installation completes. The Worklet finalizes Dialpad's setup on the user's next login action, verifying all user-specific configuration occurs at the appropriate time.

exe" -ArgumentList $argumentList -PassThru", "Stop-Process", and "Test-Win32App".

Why deploy Dialpad through Automox

Consistent communication tools are critical for IT operations teams coordinating across endpoints. Manual Dialpad installation requires IT staff to visit each machine or provide installation instructions to users, consuming significant time and effort. Automating this deployment through Automox keeps all endpoints receive the same, latest version regardless of user actions or IT availability.

The Worklet's architecture detection handles both 32-bit and 64-bit Windows systems without additional configuration, eliminating the need to run separate deployments for different endpoint types. By installing at the machine level rather than per-user, the Worklet guarantees that all users on an endpoint have access to Dialpad, standardizing your communication infrastructure across the organization.

How Dialpad machine-wide installation works

1. Evaluation phase: The Worklet queries the Windows registry to check for existing Dialpad Machine-Wide Installer entries in both the native registry view (for 64-bit applications) and the Wow6432Node (for 32-bit applications on 64-bit systems). If Dialpad is found in either location, the endpoint is marked compliant and the Worklet exits without taking further action.

2. Remediation phase: The Worklet creates a cache directory at ProgramData/amagent/WorkletCache/WSE-766, downloads the appropriate Dialpad MSI (x64 or x86) from Dialpad's Google Cloud repository based on detected system architecture, executes a silent MSI installation with machine-wide parameters, logs the installation output, and removes the installer file upon completion. If the installation requires a reboot (exit code 3010), the Worklet completes successfully; the actual installation finalizes on the user's next login.

Dialpad installation requirements

• Windows Server 2012 and later, or Windows 7 and later for workstations

• Microsoft.NET Framework 4.5 or higher

• Outbound internet access to storage.googleapis.com for downloading the Dialpad MSI installer

• Local administrator privileges to create the cache directory and execute the MSI installer

• TLS 1.2 support enabled for secure file downloads (recommended by Automox for all modern deployments)

Expected Dialpad state after installation

After the Worklet completes successfully, Dialpad is installed at the machine level and will appear in the Windows Add/Remove Programs control panel under the Dialpad Machine-Wide Installer name. The installation does not launch Dialpad automatically; instead, the application finalizes its setup when the user first logs in after installation, allowing user-specific configuration to occur at login time.

Subsequent Worklet runs will detect the installed application and mark the endpoint compliant, skipping installation. If you need to update Dialpad to a newer version, run the Worklet again and it will download and install the latest MSI available from Dialpad's repository. For best results, consider using Automox's automatic restart feature to maintain any required restarts occur during maintenance windows, allowing the Worklet to complete fully before user sessions begin.

How to validate install dialpad machine-wide changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for install dialpad machine-wide.

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 Machine-Wide, Write-Output.

4. Validate remediation effects from script operations such as Machine-Wide, New-WorkletCache, Write-Verbose, then rerun evaluation for compliance.