FT4web
Ready to move on from FT4web?Upgrade to the current browser-based FastTrack platform—no installation or desktop data updates required.View upgrade options →

System Administrator Guide

🚀 Important: Future-Proof Your Organization

FastTrack (browser-based) is the recommended solution for IT environments.

FT4web was last updated in 2019. While we'll support it as long as Windows allows, Windows is becoming increasingly restrictive with older programs. It may be soon, it may be 5 years, or it may never happen - but eventually Windows will likely prevent these older-style programs from functioning on modern computers.

FastTrack eliminates IT concerns:

  • No installation or deployment needed
  • No permission or security policy conflicts
  • No desktop update management
  • Works on any OS with a modern browser (Windows, Mac, Linux, ChromeOS)
  • Zero maintenance overhead

Review the Migration Guide to plan your organization's transition.

Overview

This guide is for system administrators, IT professionals, and technical support staff responsible for deploying and maintaining FT4web in business environments.

FT4web is a Windows desktop application that requires specific permissions and configurations to function properly. Understanding these requirements will help you avoid common deployment issues.

Installation Requirements

Administrator Privileges

Initial Installation:

  • FT Comm requires administrator privileges to install
  • Installation registers OCX and DLL components with Windows
  • Installation creates desktop shortcuts and program files

Post-Installation:

  • FT Comm should not require administrator privileges after installation
  • Users run FT Comm and FT4web with standard user permissions
  • Exception: Users need read/write access to the FT folder (see below)

File System Permissions

FT Comm and FT4web require read/write access to the installation folder (typically C:\FT) and all subfolders.

Required permissions for users:

  • Read files
  • Write/modify files
  • Create files and folders
  • Delete files

Why these permissions are needed:

  • FT4web stores user preferences in INI files
  • Data updates modify database files
  • Backup operations create ZIP files
  • Chart and family configurations are saved locally

Installation Path Requirements

✅ DO use:

  • Root directory paths: C:\FT, D:\FT, E:\FT
  • Short paths without spaces
  • Local drives (not network drives)

❌ DO NOT use:

  • Windows "Program Files" or "Program Files (x86)"
    • Windows UAC and security policies often prevent write access
    • Results in constant permission errors
  • Paths with spaces: "C:\Fast Track\FT4web"
    • Older third-party programs can't handle long filenames with spaces
  • Network/mapped drives
    • Users can't modify files on restricted network shares
    • Performance issues with database operations

Windows User Account Requirements

Single User Account Rule

❌ DO NOT install as one Windows user account and expect to use FT4web when logged in as a different Windows user account

Why this fails:

  • FT4web stores user-specific settings in Windows registry and INI files
  • Settings are tied to the Windows user profile
  • Different users can't access each other's configurations

Correct approach:

  • Install FT Comm while logged in as the user who will use it
  • OR install for each user separately
  • OR use a shared/service account (not recommended)

INI File Handling

Understanding FT4web's INI Files

FT4web uses INI files for configuration (common practice before Windows Vista). Modern security software often restricts INI file modification.

Critical INI files:

  • ft4win.ini (main configuration)
  • Various user preference files in USERDEF folders

Security Software Conflicts

Problem: If you install security software that prevents FT programs from modifying their own INI files, users will get error messages on startup and shutdown of FT4web Charting and Ranking.

Solution:

  1. Add exceptions for the FT folder in your security software
  2. Allow FT4web.exe and FTComm.exe to modify INI files
  3. Test: User should be able to launch FT4web, change settings, close without errors

Firewall and Network Requirements

Outbound Connections

FT Comm requires outbound internet access to:

  • FastTrack update servers (wsftserver.fasttrack.net)
  • Data download servers (ftcloud.fasttrack.net)
  • Backup services

Firewall configuration:

  • Allow FTComm.exe outbound HTTPS (port 443)
  • Allow FT4web.exe outbound HTTPS (port 443)
  • Do not block ClickOnce deployment domains

Remote Support Access

FastTrack Support uses LogMeIn Rescue for remote assistance and training.

⚠️ If you block remote control services, FastTrack Support cannot provide effective assistance.

Recommendation: Allow LogMeIn Rescue for users who may need support, or have a procedure to temporarily allow it when needed.

Anti-Virus Considerations

False Positives

ClickOnce applications (like FT Comm) and programs that modify their own files (like FT4web) sometimes trigger anti-virus false positives.

Common triggers:

  • Self-modifying executable behavior
  • Writing to INI files
  • Creating/modifying database files
  • Downloading and executing updates

Recommended approach:

  1. Add FT folder (C:\FT) to anti-virus exceptions
  2. Add FTComm.exe and FT4web.exe to trusted programs
  3. Test thoroughly before deployment
  4. Document exceptions in your security policy

Ransomware Protection

Modern anti-virus includes ransomware protection that monitors file modifications. This can interfere with FT4web's normal operation.

Solution: Configure ransomware protection to allow FT4web to modify files in the FT folder.

Group Policy Considerations

Application Execution Policies

If using AppLocker or similar application whitelisting:

  • Whitelist FTComm.exe
  • Whitelist FT4web.exe
  • Whitelist any update executables

User Rights Assignment

Ensure users have:

  • Right to run programs from C:\FT
  • Right to modify files in C:\FT
  • Right to access internet for updates

Deployment Scenarios

Single User Installation

Simplest approach:

  1. User downloads and installs FT Comm with admin rights
  2. User runs updates and uses software with standard rights
  3. Minimal IT involvement needed

Multi-User Shared Computer

Not recommended due to user profile conflicts, but if necessary:

  1. Install FT Comm once as administrator
  2. Each user configures their own account credentials
  3. Each user has their own families, charts, and settings
  4. Significant configuration duplication

Enterprise Deployment

For deploying to multiple computers:

  1. Test installation on a reference machine
  2. Document exact installation path (use same path for all)
  3. Create installation script or package
  4. Document firewall and anti-virus exceptions needed
  5. Provide users with their account credentials
  6. Test on a pilot group before wide deployment
  7. Consider: FastTrack (browser) eliminates all these deployment concerns

Backup and Disaster Recovery

Cloud Backups

FT Comm includes cloud backup functionality:

  • Users can enable automatic backups during updates
  • Backups stored on FastTrack servers
  • Useful for disaster recovery or computer replacement

Local Backups

FT Comm also creates local backups:

  • Location: [FT root]\Backups
  • Format: ZIP files
  • Naming: backup-[yyyyMMdd] [hh-mm-ss-tt]-[uniqueid].zip

Recommendation: Include the FT\Backups folder in your standard backup procedures.

Critical Files to Backup

If backing up manually, prioritize:

  • [ftroot]\userdef (families and custom lists)
  • [ftroot]\ft4win\SPREADSHEETS\USERDEF
  • [ftroot]\ft4win\CHARTDEF\USERDEF
  • [ftroot]\ft4win\SIGNALS\USERDEF
  • [ftroot]\ft4win.ini

Troubleshooting for IT

User Reports "FT won't work"

Diagnostic checklist:

  1. Can user run FTComm.exe? (Check permissions, anti-virus)
  2. Can FTComm connect to internet? (Check firewall)
  3. Are credentials correct? (User may have forgotten)
  4. Is install folder writable? (Check NTFS permissions)
  5. Any anti-virus quarantine logs? (Check for false positives)

Installation Fails

Common causes:

  1. Installing in Program Files (use C:\FT instead)
  2. Insufficient admin rights during install
  3. Anti-virus blocking ClickOnce deployment
  4. Network drive selected as install path
  5. Firewall blocking initial download

Updates Fail

Common causes:

  1. Firewall blocking update servers
  2. Anti-virus quarantining update files
  3. Corrupted install (requires reinstall)
  4. Write permissions lost on FT folder
  5. User's subscription expired

Permission Errors on Startup/Shutdown

Root cause: FT4web cannot write to INI files or data files

Solutions:

  1. Verify NTFS permissions on FT folder
  2. Check security software isn't blocking writes
  3. Confirm user is logged in with same account that installed
  4. Move installation out of Program Files if needed

Complete Installation Test Procedure

The job is not complete until:

  1. User can run FTComm to update data ✓
  2. User can see charts in FT4web ✓
  3. User can modify chart settings ✓
  4. User can shut down without error messages ✓

Test procedure:

  1. Install FT Comm as admin
  2. Log in as standard user
  3. Run FTComm, click Connect, complete update
  4. Launch FT4web from desktop
  5. Display a chart
  6. Modify a chart setting (change colors, add indicator)
  7. Close FT4web - should close cleanly without errors
  8. Reopen FT4web - modified settings should persist
  9. If any step fails, diagnose and fix before considering installation complete

Migration Planning

When to Consider FastTrack (Browser)

FastTrack is strongly recommended if:

  • You support Mac users or mixed OS environment
  • You have strict security policies that conflict with FT4web requirements
  • You want to eliminate installation and update management
  • You're deploying to a large number of users
  • You want zero desktop IT overhead

Migration Benefits for IT

Elimination of IT concerns:

  • No software installation or updates to manage
  • No permission conflicts or security policy issues
  • No firewall or anti-virus exceptions needed
  • No desktop shortcuts or registry entries
  • No user-specific configurations to troubleshoot
  • No backup/restore procedures needed
  • Works on any modern browser, any OS

Support burden reduction:

  • Users access via URL, no installation help needed
  • No "it won't update" support tickets
  • No "lost my families" restoration requests
  • No Windows version compatibility issues

Read the Migration Guide to plan your organization's transition.

Final Notes

Critical Warning

There are dozens of ways that you, as a System Administrator configuring Windows, firewalls, spyware software, and virus software, can lock down a system so tight that FastTrack will die from lack of oxygen.

If you:

  • Block internet access
  • Prevent file writes
  • Block INI file modification
  • Quarantine executables
  • Block LogMeIn Rescue
  • Use restrictive Group Policies
  • Install in Program Files
  • Block ClickOnce deployment

Then FT4web will not function properly.

The software was designed in an era with fewer security restrictions. Modern security practices often conflict with its requirements. This is another strong reason to consider migrating to FastTrack (browser).

Support for System Administrators

Phone: 866-295-0166

  • Extension 2: Technical support

Business Hours: 8:00AM-5:00PM Central (market days)

Resources:

FastTrack Support staff are familiar with IT environments and can work with you to resolve deployment issues. However, remote assistance via LogMeIn Rescue is often necessary for effective troubleshooting.