Windows Client Pre-Requisites

All you need to do to enroll a Windows Client is to deploy a customized FileWave Client MSI to your machines. We typically recommend using an existing tool capable of deploying a MSI such as Group Policy. This customized MSI can also be "baked" into a Windows image that can be deployed via FileWave's Imaging Virtual Server (IVS) so that freshly imaged Windows machines will automatically enroll into FileWave. Lastly, the FileWave Client MSI can be manually distributed and installed on any Windows machine that has local Administrator privileges. 

If your organization uses Microsoft Entra ID and your users authenticate using Microsoft Entra ID credentials into their Windows machines, please consider enrolling your Windows machines into FileWave via Microsoft Entra ID. This will also allow for Windows MDM management within FileWave. Learn more on our Windows MDM article.

Generating a custom FileWave Client MSI

1. Open the FileWave Customer Installer Builder for Windows.
2. Fill out the settings accordingly.
3. Click the "Build" button and wait for the automatic download.
4. Extract ZIP and install the customized FileWave Client MSI.

Note: The default Server Port setting above is 20015. However, SSL is now required, and the system will automatically use port 20017 instead when 20015 is entered. Do not manually set the port to 20017. Always enter 20015, and the system will handle the SSL port change for you.

Deploying the FileWave Client with Group Policy (Startup Script)

If you have no other way to easily deploy the FileWave Client to Windows sytems, but they are all tied to an Active Directory then leveraging Group Policy (GPO) can allow you to rapidly deploy the client with very little effort. 

<#
.SYNOPSIS
    Deploys the FileWave agent via a Group Policy startup script, always logging output.
.DESCRIPTION
    Checks whether the FileWave process is running; if not, copies the MSI from the network share
    to a local temp directory and installs it in silent mode. All verbose, warning, and error output
    is logged to C:\temp\Deploy-FileWave.log, trimmed to the last 100 KB at each run.
.NOTES
    - [CmdletBinding()] and param() have been removed since the script no longer accepts parameters.
    - Verbose output is forced by setting $VerbosePreference = 'Continue'.
#>

# Force verbose output so all Write-Verbose messages appear in transcript
$VerbosePreference = 'Continue'

# Define directory and log file
$destDir = 'C:\temp'
$logFile = Join-Path -Path $destDir -ChildPath 'Deploy-FileWave.log'
$maxBytes = 100KB

# Ensure the log directory exists
if (-not (Test-Path -Path $destDir)) {
    try {
        New-Item -Path $destDir -ItemType Directory -Force | Out-Null
    } catch {
        Write-Error "Failed to create log directory '$destDir': $_"
        Exit 1
    }
}

# Trim existing log to last 100 KB
if (Test-Path -Path $logFile) {
    try {
        $fs = [System.IO.File]::Open($logFile, 'Open', 'ReadWrite')
        if ($fs.Length -gt $maxBytes) {
            $buffer = New-Object byte[] $maxBytes
            $fs.Seek(-$maxBytes, 'End') | Out-Null
            $fs.Read($buffer, 0, $maxBytes) | Out-Null
            $fs.SetLength(0)
            $fs.Write($buffer, 0, $maxBytes)
        }
        $fs.Close()
    } catch {
        Write-Warning "Failed to trim log file: $_"
    }
}

# Start transcript logging
Start-Transcript -Path $logFile -Append
Write-Verbose "Transcript started at '$logFile'."

$ProcessName = 'fwcld'
Write-Verbose "Checking for process '$ProcessName'..."

# Check if FileWave agent is running
try {
    Get-Process -Name $ProcessName -ErrorAction Stop | Out-Null
    Write-Verbose "Process '$ProcessName' is currently running."
    $isRunning = $true
} catch {
    Write-Verbose "Process '$ProcessName' not found. Proceeding with installation."
    $isRunning = $false
}

if (-not $isRunning) {
    Write-Verbose "Deploying FileWave agent..."

    # Ensure destination directory exists for MSI
    if (-not (Test-Path -Path $destDir)) {
        Write-Verbose "Directory '$destDir' does not exist. Creating directory..."
        try {
            New-Item -Path $destDir -ItemType Directory -Force | Out-Null
            Write-Verbose "Successfully created directory '$destDir'."
        } catch {
            Write-Error "Failed to create directory '$destDir': $_"
            Stop-Transcript
            Exit 1
        }
    } else {
        Write-Verbose "Directory '$destDir' already exists."
    }

    # Define installer paths
    $installerSharePath = '\\server\share\FileWaveCustom.msi'
    $installerLocalPath = Join-Path -Path $destDir -ChildPath 'FileWaveCustom.msi'
    Write-Verbose "Installer source: '$installerSharePath'."
    Write-Verbose "Installer destination: '$installerLocalPath'."

    # Copy the MSI installer
    Write-Verbose "Copying installer from network share to local directory..."
    try {
        Copy-Item -Path $installerSharePath -Destination $installerLocalPath -Force
        Write-Verbose "Successfully copied installer to '$installerLocalPath'."
    } catch {
        Write-Error "Failed to copy installer: $_"
        Stop-Transcript
        Exit 1
    }

    # Install MSI and capture logs
    $installLog = Join-Path -Path $env:TEMP -ChildPath 'FileWaveInstall.log'
    $msiArgs = "/i `"$installerLocalPath`" /qn /norestart /l*vx `"$installLog`""
    Write-Verbose "Starting MSI installation. Command: msiexec.exe $msiArgs"

    $process = Start-Process -FilePath 'msiexec.exe' -ArgumentList $msiArgs -Wait -PassThru
    if ($process.ExitCode -eq 0) {
        Write-Verbose "Installation completed successfully (exit code 0). Log: '$installLog'."
    } else {
        Write-Error "MSI installation failed (exit code $($process.ExitCode)). See '$installLog'."
        Stop-Transcript
        Exit $process.ExitCode
    }

    Write-Verbose 'FileWave installation process finished.'
} else {
    Write-Verbose "Skipping deployment; '$ProcessName' already running."
}

# Stop transcript logging
Stop-Transcript
Write-Verbose "Transcript stopped. Log written to '$logFile'."