Use the approved 4.1.0 installer for your edition and confirm the version shown in the installed application. Published package availability is shown in Downloads & beta access.
Before installing
Use the approved 4.1.0 server and Windows client packages supplied for your environment. A source ZIP is not an end-user installer. Check the package identity and published hash before opening it. Keep the server and client release notes together. Install on the Windows hosts intended for the assessment platform, using an account authorized to install software.
For an upgrade, take a recoverable backup of the existing database, application-managed evidence, configuration, certificates and protected key material. Record the existing service account, database endpoint and network settings. A normal upgrade must not reinitialize a populated database or replace unrelated PostgreSQL installations.
1. Review the environment
Launch IT Audit Factory Server Setup on the intended server. On Review, check the discovered environment and whether this is a new install or an upgrade. The 4.1.0 wizard is divided into three pages rather than one long form. Use Back and Next to inspect the proposed values before starting installation.
2. Database & Network
On Database & Network, review the managed PostgreSQL selection and saved network values. Retain verified existing values during an upgrade. Confirm the server hostname, selected interface, port and certificate configuration; clients must use the reachable server endpoint, not their own localhost. Let the wizard validate required fields. Correct the specific failed check rather than weakening network or authentication controls.
3. Install & Validate
Review the final summary on Install & Validate, then start the installation. Keep the workflow open until both installation and service validation finish. Follow the stage/progress information; expand technical details or use the log action when a step fails. Do not treat an installer launch as proof that the API or database is healthy.
4. Connect the Windows client
Install the matching Windows assessor client. Open Configuration > Settings & Credentials, select the intended server and enter the authorized client/API credentials provided by your administrator. Run the connection diagnostics and resolve DNS, TCP, certificate/TLS and authentication failures in order. Use Configuration > Security & Experience for the current Secure Communication activation workflow described in the security guide.
5. First-run acceptance
Confirm the client connects to the intended server, opens the expected client/program records and can retain a harmless configuration change across restart. Select a small authorized assessment scope, check module dependencies and credentials, and run a pilot. Inspect the evidence and exported report before wider use. Missing or denied collection is not a passing control.
Recovery
Keep failed-stage logs and the backup set. Do not create a replacement blank database to hide an upgrade failure. Restore a matched application/data/key set when rolling back, following your approved recovery process. Send a sanitized failure summary and the build identity to Support@ITAuditFactory.com; never email passwords, API keys or private signing keys.