Installer and SmartScreen warning

When a new version of the application is published, Windows may display a SmartScreen warning. This usually happens because the installer is a new executable file and has not yet been recognized by the system’s reputation mechanisms. It does not automatically mean there is a problem with the application, but before running it, you should always make sure the file comes from an official source.

The installation files we publish use fixed names:

  • ewida-setup.exe — Ewida Standard installer
  • eaudit-setup.exe — Ewida Audit installer

Download installers only from the Download page. We do not distribute them through external services, so we do not recommend using files from other sources.

Both applications are Windows desktop programs. They are not SaaS services running in a browser, so installation and configuration are performed directly on the user’s computer or in a Windows-based company environment.

Minimum requirements

  • Windows operating system,
  • permissions that allow application installation,
  • access to local computer resources or to company infrastructure if the application is to work on a network.

Where to install the applications

Ewida Audit and Ewida Standard should be installed on the computers where they will actually be used. This applies both to a single user and to company environments with a larger number of workstations.

We do not recommend installing these applications on a server only to run them through a remote terminal session. They are classic Windows desktop applications, and that model of work can lead to problems with performance, configuration, or access to local resources.

For Ewida Standard, in a multi-workstation setup, a client-server model is used. The program is installed on users’ workstations, while the MS SQL database server runs separately. This way, each user works locally in their own application, but on shared data.

For Ewida Audit, the console should be installed on the administrator’s computer or on the computer of the person performing the audit. Agents should be installed on the computers covered by scanning and monitoring, and Agent Server should ideally run on a stable computer or server operating within the company network.

Installing Ewida Standard

In a single-workstation installation, the program only needs to be installed on one computer. In a multi-workstation environment, the application should be installed on every workstation where a user is meant to use the system.

After the first launch, you need to decide where the data will be stored. In practice, the recommended solution for several users is an MS SQL server. The program lets you specify the server, login method, and database name, and then create a database for Ewida Standard.

If you plan to work with an SQL database, it is worth reviewing the Database in Ewida Standard guide beforehand. This makes it easier to prepare the target environment before production work begins.

What to prepare before configuring the connection

  • the SQL server address or name,
  • server login credentials,
  • the name of the database to be created or used,
  • permissions that allow a connection to the database from the user’s workstation.

Data migration in Ewida Standard

When changing the data source, the program may display the question: “Do you want to perform data migration now?”. This mechanism is used to copy data between different databases and makes it easier to move work between environments.

Migration may apply to scenarios such as:

  • from a file database to MS SQL,
  • from MS SQL to a file database,
  • between two MS SQL databases on the same server,
  • between MS SQL databases on different servers.

You need to be careful here. Migrating from an empty source database to a target database means overwriting the target database contents with empty data. That is why, before confirming the operation, it is worth making sure which source the data is being copied from and where it will end up.

This function can be useful when a user works partly in the office and partly elsewhere. In that case, data can be moved from the company SQL database to a local file database, and after returning, the changes can be synchronized back the other way.

However, if a new workstation is only meant to be connected to an existing company database, migration is usually not performed. In that case, the goal is to connect the program to current data, not to copy it between sources.

Network mode and local settings in Ewida Standard

When several users are working at the same time, it is worth enabling network mode in the database settings. Its purpose is to handle record saving more safely and refresh data more frequently in summaries, reports, and forms. If the program is used by only one person on one workstation, single-workstation mode is usually enough.

By default, Ewida Standard stores settings separately for each user and each computer. This is a practical solution when workstations differ in configuration or scope of work. In some deployments, however, sharing some settings and working folders is necessary. In that case, the way configuration and backups are stored should be planned carefully so that each user works with the correct files.

Before a multi-workstation deployment, it is a good idea to decide which elements should remain local to a given computer and which should be shared across the whole team. This reduces the risk of mistakes in printouts, exports, and work with attachments.

Installing Ewida Audit

Ewida Audit is installed as a console on the computer of the person responsible for the audit or administration. The program stores data in local encrypted files in the application directory, so it is not intended for multiple users working simultaneously on one shared instance.

If audit data is later meant to be analyzed or combined with hardware and software inventory, it can be exported to Ewida Standard. This is an important difference between the two applications: Ewida Audit is mainly used for scanning, monitoring, and analyzing the environment, while Ewida Standard is used for maintaining structured records in a database.

If the deployment includes scanning computers on the network, also review the guide for installing Agents and Agent Server. Without a properly prepared agent environment, some audit functions will not work as intended.

Moving the application to another computer

Ewida Standard and Ewida Audit licenses can be moved between computers, but each license is assigned to one workstation at a time. Before installing the program on a new computer, the license must first be deactivated on the current device.

Menu → Help → License → Deactivate

After deactivation, you can install the application on the new computer, move the necessary data, and activate the license again.

Menu → Help → License → Activate

The whole procedure is handled automatically within the program and usually does not require additional contact with technical support. Before moving the application, however, it is worth making sure a backup has been created and that all required folders have been copied.

Folders to move in Ewida Standard

If you are moving Ewida Standard to another computer, you can copy selected folders responsible for settings, data, and supporting materials. The scope of the files to be moved depends on whether you use a local file database or an external MS SQL server.

  • App — application configuration files.
  • Data — inventory data, but only if you are not using MS SQL.
  • Backup — backups.
  • Images — document images, for example invoices and warranty files.
  • Templates — print templates.

In an MS SQL-based environment, the most important items are local settings and additional materials, because the main data is stored in the database on the server.

Folders to move in Ewida Audit

When moving Ewida Audit, it is worth keeping not only the program settings, but also audit data, definitions, and supporting files related to agents and reports.

  • App — configuration files.
  • Audit — audit data and computer scan results.
  • Data — other application data.
  • Definitions — custom software definitions.
  • NET — network data used by Agents.
  • LOG — Ewida Audit console logs.
  • Backup — backups.
  • Images — document images.
  • Templates — print templates.

After moving the application, it is a good idea to check that paths are correct, communication with Agents works properly, and the latest audit data is available. In a Windows desktop application, such elements depend on the specific workstation and its configuration.