IT Audit Factory — evidence-first audit & compliance operations
Free • Professional • MSP
Documentation

Free 4.1.0 installation and operation

Obtain the approved Free installer, verify its identity, install safely and complete the first assessment.

Version 4.1.0

All documentation · Free 4.1.0

Before installation

Install only the approved Free 4.1.0 package supplied for your organization. Free is outside the beta program. Use Free downloads for public installers; no beta application is required. Contact Support if no public installer is listed. A downloaded source archive is not an installer.

Download and verify

On your private page, check the product name, platform, architecture and version. Compare the SHA-256 with the downloaded file and verify the publisher signature before opening it.

Get-FileHash .\ITAF-Free-Windows-x64-4.1.0.msi -Algorithm SHA256

Use the actual .exe, .msi or .zip extension shown on your download page. Do not change an old package name to make it appear to be 4.1.0.

Install and start

Back up existing application data, evidence, settings and protected keys before an upgrade. Run the package using an account authorized to install software. Follow the installer, retain its log, and launch IT Audit Factory Free. Confirm the installed version is 4.1.0 before continuing. Stop and contact Support if the identity does not match.

Free edition scope

Use the approved Free package for one administrator and one domain. Free is not eligible for the Professional/MSP beta offer. Do not substitute a Professional or MSP package or license key.

Configure a small pilot

Set the organization and assessment scope, configure only the required credentials and targets, and check the module prerequisites. Run a small authorized assessment. Review collected evidence, findings and output before expanding scope. Missing collection is not a passing result.

Upgrades and troubleshooting

Keep existing evidence and licensing material during an upgrade. Record the product version, installer filename and failing operation, and send a sanitized description to Support. Do not erase the existing data store to hide a migration error. Keep historical documentation separate from this guide.