This guide outlines the system requirements, standard installation processes, and enterprise deployment guidelines for our Windows application. It also includes specific instructions for installing or upgrading to our latest 64-bit application.

System Requirements

• Operating System: For best results, we highly recommend Windows 10 or Windows 11 with the latest operating system updates installed. It’s important to note that we do provide legacy support for Windows 7 and Windows 8.
• Software Frameworks: Both .NET Framework 4.7.2 and .NET 6.0 are required. These are generally included with supported Windows versions, provided they are kept up to date via Windows Update.
• Hardware: While not strictly required for installation, if you plan to capture photos, ensure your hardware includes a camera (standard on most Windows laptops and Surface devices).

Standard Installation Overview

Our Windows app is designed for a frictionless setup:

• No Administrator Permissions: The installer does not require Admin rights and generates no User Account Control (UAC) prompts.
• Simple Setup: It provides a simple, wizard-less installation experience.
• Local Directory: The app installs directly into the currently logged-in user’s working directory (%LocalAppData%).
• Registry Access: The app requires write access to the current user’s registry – a standard permission for any user capable of installing applications.

Upgrading to the 64-bit Windows App

We recently released a new 64-bit version of the Windows app. If you are a new user or are upgrading from an older 32-bit version, please review the expected behaviors below.

Scenario A: New Installations

If you do not have a previous version of the app installed, the 64-bit installation will proceed normally with no extra steps required.

Scenario B: Upgrading from a Standard 32-bit Installation

If you currently use the standard 32-bit version of the app:

1. The installer will create a new folder for the 64-bit app in C:\Users\[UserName]\AppData\Local.
2. A brand-new appdata folder will be created inside this directory.
3. Data Migration: To continue where you left off without syncing from the cloud, you can manually copy your old appdata folder contents into this new 64-bit folder.
4. Your existing desktop shortcut will automatically update to point to the new 64-bit application.

Scenario C: Upgrading a 32-bit Install with a Registered userDataDir

If your current 32-bit installation utilizes a custom registered userDataDir:

1. The installer will create a new folder for the 64-bit app install in C:\Users\[UserName]\AppData\Local.
2. Data Migration: The app will honor your existing userDataDir registry item. You do not need to manually copy any data folders.
3. Your existing desktop shortcut will automatically update to point to the new 64-bit application.

Enterprise Deployments (SCCM & Group Policy)

For administrators utilizing tools like Microsoft System Center Configuration Manager (SCCM) or Group Policy, please note the following guidelines:

MSI Installer

We provide an MSI installer built specifically for deployment via Group Policy.

• Behavior: This MSI is not a general-purpose installer. Once the MSI is run, the actual application .exe file is executed and installed on the user’s next Windows login.
• Download: You can obtain the latest MSI by appending ?msi=true to the end of our standard Windows app download link.
  • Example: https://eforms.mobileform.net/Files/WinApp/eFormsMobile

Permissions Configuration

Because the app is designed to operate without UAC requests, it installs directly into the local logged-in user’s AppData directory (e.g., %LocalAppData%\<AppCode>).

• Requirement: Ensure your Windows policies and SCCM configurations allow the application to read/write data and folders within the %LocalAppData% directory and access the local user registry. Blocking these permissions will cause installations and subsequent automatic app updates to fail.

SCCM Deployment & Squirrel.Windows

Our underlying update functionality relies on the industry-standard Squirrel.Windows installer.

• For technical specifics regarding the updater, please review the documentation on the Squirrel.Windows GitHub Wiki.
• Deployment Resource: If you are using SCCM, we recommend reviewing this third-party guide for deploying Microsoft Teams. Because Teams uses the same Squirrel.Windows updater library, the principles are identical. Simply replace all mentions of “Teams” with our application name/code to configure your deployment.