An engineering example from TLI’s own environment

Context: an internal lab server

This example concerns Third Level IT’s own Windows Server 2025 environment in October 2026. It is not a customer case study, a production-client result or a performance benchmark. No client identity or private infrastructure detail is included.

The work

The internal project brought the server into management and monitoring, applied operating-system updates, and established an encrypted backup. A subsequent security review identified host controls requiring attention. The remediation work included SMB signing, removal of unneeded services, additional security logging and checks on endpoint protection.

What was checked

The engineering records show management and monitoring check-ins, post-reboot operating-system state, the selected host-control settings and successful encrypted backup jobs. Backup configuration could be retrieved and decrypted. A later remote-access check confirmed that the intended connection could negotiate.

What that evidence does not prove

A full restore of the virtual machine was not performed. Successful backup and configuration readback therefore do not establish complete disaster recovery. A successful remote-access negotiation does not by itself demonstrate every user’s sign-in path. Outstanding findings remained documented separately from completed changes.

The method we bring to engagements

1. Identify the target and the exact problem.
2. Capture the state needed to understand and recover the change.
3. Implement within a defined scope.
4. Check the effective result and preserve the evidence.
5. State any remaining gap precisely.

For a business engagement, we agree on the required checks before implementation. The final report should tell your team what changed and what they can rely on, including any dependency that still needs work.