Release status
Archived — earlier candidate. RC9 is an earlier archived Free release candidate. Use RC12 for a new deployment. This guide supports identification, safe configuration review and upgrade/recovery; it does not assert modern MSP feature parity.
This is a version-specific website guide based on the recorded release status and the shared Free operations documentation. It is not an original manual recovered from an exact v2.3.0-RC9 source archive, and it does not certify features added in later product lines.
Installation
Do not use this archived candidate for a new beta deployment. Identify the version from the installed application, installer metadata or retained release files. Preserve its settings, assessment outputs and evidence before an upgrade. Obtain the approved RC12 package through the Free downloads page. If the archived application cannot start, do not erase its data to make the installer succeed.
RC11's recorded startup regression was corrected in RC12. Prefer the corrected package rather than manual edits to program files. Retain the original failure and installer logs for a recovery review.
Configuration
Free is the single-user, one-seat, one-domain edition. Select the intended organization/domain and keep testing data separate from real assessment evidence. Configure only authorized targets and the supported collectors that are in scope. Use the application's settings and dependency checks rather than editing internal storage locations by hand.
Check access and permissions before a pilot. Save a harmless setting, restart the app and confirm it remains saved. Keep the version's local configuration/evidence with its corresponding recovery copy. Free is not a multi-auditor MSP server deployment, and the MSP R68 coverage catalog must not be treated as Free's verified control coverage.
First assessment
Start with a small known scope. Resolve required preflight or connector failures and leave unrelated modules disabled. During the run, monitor target/module progress where supported. After completion, review raw evidence and findings rather than relying on an overall score. Separate denied access, unreachable targets, unsupported checks and missing data from an observed control failure.
Generate the available HTML report/auditor export. Check evidence links and whether the output can be reviewed in its intended offline location. Manual ISO/IEC 27001 governance, policy and approval evidence remains necessary; a technical result cannot certify the organization.
Troubleshooting
The app does not start: capture the exact version and error, verify the approved package, and prefer RC12 over the known RC11 regression. Settings do not persist: confirm the configured application data is writable for the intended account and retain the save error. A collector fails: check the specific endpoint, scope, credentials and dependency, not every module at once. Reports lack evidence: inspect whether collection actually completed and whether the relevant manual evidence was supplied.
Upgrade and recovery
Back up the existing application-managed settings and evidence before replacing software. Retain any matching protected key/configuration material supplied by the edition. Verify the recovered data in an isolated test before deleting an older recovery copy. Do not turn the current product into a blank installation simply to hide a failed migration.
Request help
Email Support@ITAuditFactory.com with the version, operating system, action, error and time. Use a sanitized support bundle or log excerpt after checking it for sensitive material. Do not include passwords, API keys, full client evidence or unrelated company data. Request an approved package from Sales@ITAuditFactory.com through the edition's download page.
Guide basis
Shared master operations guide (2026-09-17), Free section; owner-confirmed RC12 baseline and recorded RC11/RC9 archive statuses
Published as a website guide on 1 October 2026. Where a bundled reference is older, the version-specific guide and installed interface take precedence.