Installing Zeta Test Management

Use this guide to choose and deploy the current Zeta Test Management desktop package. Current desktop releases are self-contained Windows x64 applications based on .NET 10; they do not require a separate .NET Framework installation.

Before rollout, review the system requirements for Zeta Test Management 5.2 and confirm release-specific operating-system, server and database support for the target environment.

Choose the package that matches your operating model:

  • zetatest-setup.exe: normal installation for the current Windows user.
  • zetatest-setup.msi: managed software deployment with your organization's standard MSI tooling.
  • zetatest-deployment-setup.exe: central LAN deployment with shared application files and a client setup on each workstation.

Obtain the package from the official Zeta Test Management download or your support contact and verify its digital signature before rollout. Keep project data and backups separate from replaceable application files.

Zeta Test Management Web is deployed separately; a desktop or LAN installation does not create a production web server.

Single-user installation

  1. On an existing installation, back up all projects and close Zeta Test Management.
  2. Download the current zetatest-setup.exe and check that the file is digitally signed by Zeta Software GmbH.
  3. Run the setup wizard. The normal EXE setup installs for the current user and usually does not require administrator rights.
  4. Start Zeta Test Management from the Start menu or desktop shortcut.
  5. Create a test project or open an existing one. Confirm that the user has write access to the selected project folder and, when applicable, the database.
  6. Open the licensing dialog if you need to enter or verify a purchased license.

A locally installed client can also open approved projects on a file server. Project sharing, permissions, database choice, backup, and concurrent use must still be planned independently of the application setup.

Managed LAN deployment

Use the LAN deployment package when several workstations should run one centrally maintained application version.

  1. Create a dedicated application folder on a file server and publish it through a stable UNC path. Keep shared projects in a separate data location.
  2. Grant users read and execute access to the application share. Grant update rights only to the administrators responsible for deployment.
  3. Run zetatest-deployment-setup.exe with an account that can write to the destination and select the central application folder.
  4. On each workstation, run ClientSetup\ztcs.exe from the central deployment. Pilot this step on one workstation before using login scripts, software distribution, or Group Policy.
  5. Grant the intended users the required rights to project folders and databases. For larger or centrally operated environments, plan a suitable database server and backup strategy.
  6. Start Zeta Test Management from a pilot workstation, open a representative project, and verify version, read/write access, attachments, reports, and licensing.

The obsolete .NET Framework 2.0, Internet Explorer security-zone, and .NET Code Access Security instructions no longer apply to the current self-contained Windows x64 deployment.

Update, verify, and troubleshoot

Update safely

  1. Back up projects and databases, record the installed version, and make sure all users have closed the application.
  2. Verify the signature of the new package. For a local installation, run the current setup. For a LAN deployment, stage the new central folder or use your approved maintenance procedure.
  3. Test the update with one workstation and one representative project before broad rollout. If the release contains a new client setup, include ClientSetup\ztcs.exe in the rollout.
  4. Keep the previous application package and project backup until the acceptance window has ended.

Verification checklist

  • The displayed Zeta Test Management version is the intended release.
  • A project can be opened and changed with the intended account.
  • Shared paths, database access, attachments, reports, and licensing work as expected.

If setup or startup fails

  • Check whether Windows has blocked the downloaded file and whether the digital signature is valid.
  • Check free disk space, antivirus or application-control messages, and the user's rights to local and shared folders.
  • For LAN deployments, verify that the UNC path is reachable and that the client setup was run from the current central deployment.
  • Collect the exact error, product version, setup/application logs, and the affected path before contacting support.

For the separate central web deployment, follow Install and configure Zeta Test Management Web; do not treat the local web EXE setup as an IIS production deployment.