Windows - Software - Install Cisco Webex

What the Cisco Webex deployment Worklet does

This Automox Worklet™ deploys Cisco Webex to Windows endpoints and confirms the install through the Windows uninstall registry. The Worklet inspects the 64-bit and 32-bit uninstall hives for an existing Webex DisplayName entry, then downloads the matching MSI from Cisco and runs a silent install when the client is absent.

The script checks [System.Environment]::Is64BitOperatingSystem to select either Webex_en.msi (64-bit) or Webex_x86_en.msi (32-bit) from binaries.webex.com. The installer is staged to C:\temp\Automox\WebexInstall and executed through msiexec.exe with ALLUSERS=1 and ACCEPT_EULA=TRUE for a system-wide install. On 64-bit Windows, the install runs through sysnative PowerShell so the 64-bit MSI is processed in the native environment.

The Worklet writes a verbose msiexec log to C:\ProgramData\amagent\Webex64_install.log or Webex32_install.log depending on architecture, waits up to 300 seconds for msiexec to finish, and removes the staging directory on exit. Subsequent evaluations are idempotent: once a Webex DisplayName appears in either uninstall hive, the Worklet exits with success and skips remediation.

Why deploy Cisco Webex through a Worklet

Manual Webex deployments produce version drift, mixed install sources, and incomplete inventory. New hires file help-desk tickets when the client is missing on day one. Security teams cannot confirm which endpoints have the corporate-approved client versus a sideloaded MSI from webex.com. A standardized Worklet gives you one Webex install path that every Windows endpoint follows, with msiexec logs at C:\ProgramData\amagent\ you can audit and a registry check you can verify without touching the endpoint.

Schedule this Worklet against a Windows workstation group so the architecture check picks the 64-bit or 32-bit MSI for each endpoint and msiexec installs in the background. Results report back through the Activity Log, so a failed deployment surfaces in the policy result rather than as a user ticket weeks later.

How the Cisco Webex deployment works

1. Evaluation phase: The Worklet enumerates HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall (64-bit applications) and HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall (32-bit applications on 64-bit Windows) and reads each subkey's DisplayName. If a DisplayName matching *Webex* is present in either hive, the endpoint is reported compliant and remediation is skipped. If no Webex DisplayName is found, the endpoint exits 1 and is flagged for remediation.

2. Remediation phase: On a 64-bit OS, the Worklet relaunches under C:\Windows\sysnative\WindowsPowerShell\v1.0\powershell.exe and runs the install scriptblock in the native 64-bit environment. The script creates C:\temp\Automox\WebexInstall, calls (New-Object System.Net.WebClient).DownloadFile to pull Webex_en.msi (64-bit) or Webex_x86_en.msi (32-bit) from binaries.webex.com, and runs msiexec.exe /i <Webex.msi> /qn /norestart ACCEPT_EULA=TRUE ALLUSERS=1 /l*v C:\ProgramData\amagent\Webex64_install.log (or Webex32_install.log). The script waits up to 300 seconds for msiexec to exit, treats exit codes 0 and 3010 as success, removes the staging directory, and writes a final status line. Any other exit code, or a timeout, fails the remediation with exit 1.

Cisco Webex deployment requirements

• Windows 10 or later (Windows 10, Windows 11, Windows Server 2016 or newer) with PowerShell 5.1 or later

• Administrative privileges on the endpoint (the Automox agent's default SYSTEM context satisfies this)

• Outbound HTTPS connectivity to binaries.webex.com to pull Webex_en.msi or Webex_x86_en.msi

• Free disk space on C:\ for the staging directory C:\temp\Automox\WebexInstall plus the installed client

• Write access to C:\ProgramData\amagent\ for the Webex64_install.log or Webex32_install.log msiexec transcript

• FixNow compatible: pair the policy with FixNow for on-demand rollout to a target endpoint group ahead of the next scheduled evaluation

Expected endpoint state after the Cisco Webex deployment

After a successful run, Webex is registered under HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall on a 64-bit install, or under HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall when the 32-bit MSI is used on 64-bit Windows. The DisplayName contains Webex and DisplayVersion is populated by the MSI. Because the install uses ALLUSERS=1, the client is registered system-wide and is available to every user profile on the endpoint from the Start menu and Windows Search.

Validate the deployment on a pilot endpoint by running Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object DisplayName -like '*Webex*' from an elevated PowerShell session. Confirm the installer log at C:\ProgramData\amagent\Webex64_install.log (or Webex32_install.log) ends with msiexec return value 0, or 3010 if a deferred restart is required. The Worklet runs silently and does not prompt the signed-in user. Subsequent Automox evaluations report the endpoint compliant and skip remediation until the client is uninstalled or the policy is re-scoped.