Install Google Drive

What the Google Drive installer does

This Automox Worklet™ detects whether Google Drive is installed on a Windows endpoint by checking both 64-bit and 32-bit registry locations. If Google Drive is absent, the Worklet downloads the latest installer from Automox's cached source and executes a silent installation.

The evaluation phase inspects the Windows registry uninstall keys to determine installation status. The remediation phase retrieves the Google Drive installer from Automox's infrastructure and installs it without user interaction or reboots.

Why deploy Google Drive through Automox

Maintaining consistent software deployments across a fleet of Windows endpoints creates operational efficiency and reduces support tickets. Google Drive provides users direct access to cloud-based files, reducing dependency on shared network drives while improving mobility and collaboration.

Automating Google Drive deployment eliminates manual installation steps, reduces configuration drift, and gives all endpoints access to the application at the same version. This approach scales across hundreds of endpoints without administrative overhead.

How Google Drive installation works

1. Evaluation phase: The Worklet queries the Windows registry to check the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall registry key. On 64-bit systems, it checks both the native 64-bit registry path and the 32-bit compatibility path (Wow6432Node). If Google Drive is found in any location, the Worklet exits successfully. If Google Drive is not found, the Worklet proceeds to remediation.

2. Remediation phase: The Worklet downloads GoogleDriveSetup.exe from Automox's cached installer repository. It then executes the installer with the --silent flag, which installs Google Drive without displaying any user interface or requiring interaction. After installation completes, the Worklet removes the temporary installer file and reports success.

Google Drive installation requirements

• Windows 8 or later (Windows 10, Windows 11, Windows Server 2012 R2 or later)

• Internet connectivity to reach Automox's cached installer service (api.automox.com)

• Administrative privileges to modify registry and install software

• Approximately 20-50 MB free disk space for the installer and Google Drive application

Expected state after Google Drive installation

After successful execution, Google Drive will be installed on the Windows endpoint and ready for use. Users can launch Google Drive from the system tray or Start menu to access their Google account and sync files. Subsequent Worklet executions will detect the installed application and exit without reinstalling, preventing unnecessary repetition. You can verify this change through the Automox Activity Log or by checking the endpoint configuration directly.

If installation fails, the Worklet will report an error message indicating that Google Drive could not be installed. Common failure reasons include network connectivity issues, insufficient disk space, or missing administrative privileges. Verify these prerequisites and rerun the Worklet after addressing any blocking conditions.

How to validate install google drive changes

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

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 Get-ChildItem, Get-ItemProperty, Where-Object.

4. Validate remediation effects from script operations such as Start-Process, Remove-Item, Write-Output, then rerun evaluation for compliance.

For technical validation, compare endpoint state to the Worklet evaluation logic and remediation flow for install google drive. 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 Get-ChildItem, Get-ItemProperty, Where-Object and remediation operations such as Start-Process, Remove-Item, Write-Output. Use these indicators to verify that endpoint changes match intended policy outcomes.