Windows - Software Lifecycle - Install ThinkCell

What the think-cell Installer does

This Automox Worklet™ installs think-cell on Windows endpoints. Think-cell is a premium add-in for Microsoft PowerPoint that streamlines the creation of professional charts, data visualizations, and slide layouts used extensively in business consulting and finance.

The Worklet requires you to upload the think-cell MSI installer (setup_think-cell.msi) to the Worklet payload. Your organization's license key must be configured as an Automox Shared Secret named "licenseKey" to activate the software during installation.

During remediation, the Worklet creates a cache directory, copies the MSI from the payload, and executes the installer with the LICENSEKEY parameter for silent activation. A configurable timeout (default 5 minutes) prevents installations from hanging.

Why deploy think-cell through Automox

think-cell is essential for organizations that require professional-grade chart creation in PowerPoint presentations. Manual deployment of licensed software across multiple endpoints requires significant IT resources and creates delays for new employees who need the tool immediately.

Automating think-cell deployment through this Worklet standardizes the installation and handles license activation automatically. The integration with Automox Shared Secrets keeps your license key secure while enabling automated deployment at scale.

The Worklet provides visibility into which endpoints have think-cell installed, helping you manage software licenses and identify users who may need the add-in for their presentation work.

How think-cell installation works

1. Evaluation phase: The Worklet searches Windows registry uninstall keys for "think-cell" in both 64-bit and 32-bit registry paths. If found, the endpoint is marked compliant. If not found, the endpoint proceeds to remediation.

2. Remediation phase: The Worklet validates that the licenseKey Shared Secret and payload are configured, creates a cache directory, copies the MSI installer, executes msiexec with /qn, /norestart, LICENSEKEY arguments, logs the installation, waits for completion (configurable timeout), and removes the installer file.

think-cell installation requirements

• Active think-cell subscription with valid license key

• Automox Shared Secret named "licenseKey" configured with your think-cell license

• think-cell MSI installer (setup_think-cell.msi) uploaded to Worklet payload

• Microsoft PowerPoint installed on the endpoint

• Administrative privileges for software installation

• Optional: Configure installTimeout parameter (default 300 seconds)

Expected state after think-cell installation

After successful remediation, think-cell appears in the Windows Programs list and registry uninstall keys. You can verify successful installation by checking the installed applications list in Control Panel or by searching for the application in the Start menu. The think-cell tab becomes available in the PowerPoint ribbon when users launch the application. The software is pre-activated with your organization's license key.

Installation logs are saved to ProgramData\amagent\WorkletCache\WSE-856\think-cell_install.log for troubleshooting. The installer file is automatically removed after installation. Subsequent Worklet runs will detect the existing installation and exit without action.

How to validate install thinkcell changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for install thinkcell.

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 Secrets-Management, Write-Output.

4. Validate remediation effects from script operations such as Secrets-Management, Write-Error, New-WorkletCache, then rerun evaluation for compliance.

For technical validation, compare endpoint state to the Worklet evaluation logic and remediation flow for install thinkcell. This supports repeatable software lifecycle workflows, faster change control review, and auditable compliance evidence.

Useful script references for this Worklet include evaluation operations such as Secrets-Management, Write-Output and remediation operations such as Secrets-Management, Write-Error, New-WorkletCache. Use these indicators to verify that endpoint changes match intended policy outcomes.