Upgrade FileCloud Sync Classic

What the FileCloud Sync Classic Upgrader does

This Automox Worklet™ detects endpoints running older versions of FileCloud Sync Classic and upgrades them to a version you specify. The Worklet queries the Windows registry to find FileCloud Sync Classic installations and compares the installed version against your target version number.

You download the FileCloud Sync Classic installer EXE from the official FileCloud downloads page and upload it to the Automox console. The Worklet then uses this installer to perform silent upgrades on endpoints where older versions are detected. Endpoints without FileCloud Sync Classic are skipped as not applicable.

The Worklet uses Inno Setup installer arguments for silent operation, which FileCloud Sync Classic supports. You can customize the installer arguments to include options like /VERYSILENT, /NORESTART, /CLOSEAPPLICATIONS, or /LOG depending on your deployment requirements.

Sync failures from outdated FileCloud clients

Outdated FileCloud Sync Classic versions create sync failures with updated server infrastructure. File conflicts, incomplete downloads, and upload errors disrupt productivity when client-server version mismatches prevent proper synchronization. Users experience perpetual "sync pending" states where file changes never propagate to other endpoints, leading to data loss from unsynchronized work.

Version incompatibility generates authentication failures, SSL certificate errors, and connection timeouts that block file access entirely. Security vulnerabilities in older clients remain unpatched, exposing cloud storage credentials and synchronized data to exploitation. Manual upgrade coordination across distributed users delays critical security fixes and reliability improvements.

How FileCloud Sync Classic upgrades work

1. Evaluation phase: The Worklet queries HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall for entries matching FileCloudSync. It compares the DisplayVersion value against the $AppVersion variable you configure. If the installed version is lower than the target, the endpoint is flagged for remediation. If FileCloud Sync Classic is not installed, the endpoint exits as not applicable.

2. Remediation phase: The Worklet runs the uploaded installer EXE from the script directory with the arguments you specify in $InstallerArgs (default: /VERYSILENT /NORESTART). The installation runs synchronously using Start-Process -Wait. The Worklet verifies success by exit code and reports the upgrade result.

FileCloud Sync Classic upgrade requirements

• Windows 7 or later

• FileCloud Sync Classic already installed (Worklet only upgrades existing installations)

• Upload FileCloud Sync Classic EXE installer to the Automox console

• Configure $AppVersion with target version number (e.g., '21.1.1.5892')

• Configure $InstallerName with the exact filename of the uploaded installer

• Optional: customize $InstallerArgs for specific installation behavior

Outcomes after upgrading FileCloud Sync

FileCloud Sync Classic runs your specified version with full server compatibility restored. File synchronization completes successfully without conflicts, upload errors, or perpetual pending states. Users see the updated version in the system tray icon, confirming the registry DisplayVersion matches your target release.

Existing sync folders, server connections, and credentials persist unchanged through the upgrade. Users continue working immediately without reboots through the /NORESTART flag. Your fleet maintains consistent FileCloud client versions with security vulnerabilities patched and sync reliability improved across all endpoints.

Installation failures generate exception details in Activity Log identifying missing installers, incorrect $InstallerName values, or process file locks. Adding /CLOSEAPPLICATIONS to $InstallerArgs resolves file lock issues by automatically closing running instances before upgrade.

How to validate upgrade filecloud sync classic changes

1. Run this Worklet on a pilot Windows endpoint and review evaluation output for upgrade filecloud sync classic.

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 Get-ChildItem, Get-ItemProperty, Where-Object, then rerun evaluation for compliance.

Expected state after upgrade filecloud sync classic changes

After remediation, endpoints reflect the target upgrade filecloud sync classic configuration and report compliant status in Automox.

You can confirm results by correlating activity logs with evaluation checks (Get-ChildItem, Get-ItemProperty, Where-Object) and remediation actions (Get-ChildItem, Get-ItemProperty, Where-Object).