Documentation

Professional 4.1.0 installation and operation

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

Version 4.1.0

Before installation

Install only the approved Professional 4.1.0 package supplied for your organization. Follow your private download link after your email, application and signed agreement have been verified. 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-Professional-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 Professional. Confirm the installed version is 4.1.0 before continuing. Stop and contact Support if the identity does not match.

Installation ID and activation

In Professional, open Configuration → Licensing and copy the complete Installation ID from the computer that will be licensed. Send the ID with your random request reference to Support@ITAuditFactory.com. Support provides the installation-bound key after the signed agreement and ID have been verified. Never send passwords or private signing keys.

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.