# Installation server

## **Installation server**

The installation server enables remote installation and uninstallation of applications in MSI and EXE formats on end-user computers via the eAgent service. The feature supports both IT administrators and end users (feature in development), allowing application installation without the need to elevate administrative privileges. The system offers two application repositories:

* **Public** – managed by the system provider, containing verified installers.
* **Private** – managed by the user, with the ability to add custom applications.

### **Detailed view**

The interface **Installation server** is divided into four main sections, visible in the top menu:

1. **Remote Application Manager**
2. **Application Catalogs**
3. **Current Operations**
4. **Logs**

<figure><img src="/files/093790c12980770ec5ee9679d2ef862960cd9575" alt="" width="375"><figcaption></figcaption></figure>

## **Remote installation**

### **View features**

1. **Public application repository**
   1. Contains installers provided and managed by the system vendor.
2. **Private application repository**
   1. Allows users to add their own applications.

### **Data presentation**

The switch is located in the upper right corner.&#x20;

<figure><img src="/files/1ed73165b30121734a9bb7a1596c0aaa32c976c0" alt="" width="375"><figcaption></figcaption></figure>

Applications in the repository can be displayed as:

* **Table**

<figure><img src="/files/4247eb247dc76f722a870477eda73ff9f254475d" alt="" width="375"><figcaption></figcaption></figure>

* **Tiles**

<figure><img src="/files/093790c12980770ec5ee9679d2ef862960cd9575" alt="" width="375"><figcaption></figcaption></figure>

Both views present the same information:

* **Category** – Allows filtering applications by category.
  * Predefined categories: Antivirus, Archivers, Office Suites, Developer Tools, Browsers, and others.
  * For private applications there is an option to add a new category.
* **Application** – Application name with icon.
* **Version** – Application version number.
* **Vendor** – Name of the application vendor (e.g., Microsoft, Adobe).
* **Date of last update** – Information about the last modification of the installer.
* **Actions**:
  * **Install** **App** – Initiates installation on selected computers.
  * **Uninstall** **App** – Option available only if an uninstall command is defined in the application configuration.
  * **Edit** – Edits the existing entry.
  * **Duplicate** – Creates a copy of the entry in the private repository.
  * **Delete** – Deletes the entry (applies to the private repository only).

### **Adding an application**

Clicking **+Add new application** opens a form with the following fields:

<figure><img src="/files/f45efe18538ccad06b1a46bbb4e62fba4a569229" alt="" width="375"><figcaption></figcaption></figure>

1. **Upload installer file**, supported formats are \*.exe and \*.iso.
2. **Application name** – Required field. If empty, the system will automatically populate the name based on the installer file.
3. **Upload icon** – Optional, PNG format, up to 10 MB.
4. **Category** – Selection from a dropdown list or adding a new category.
5. **Vendor** – Optional, dropdown list with the ability to add a new vendor.
6. **Application version** – Text field for the version number, e.g., "1.2.0".
7. **Description** – Optional application description.
8. **Installation command** – Command used for silent installation of the application, e.g.:

```
chrome_installer.exe /silent /install.
```

9. **Uninstallation command** – Optional field for the uninstall command.
10. **Post-installation verification** – Optional fields to verify installation success:
    1. Process to check.
    2. Program in registry.
    3. Path to file.

{% hint style="info" %}
Fill in the fields to check the installation process, registry entries and the application file path after installation to confirm its correctness
{% endhint %}

<img src="/files/e57dc8424069aabba94b653274c9e573d472ed95" alt="" width="375">

### **Installation and uninstallation**

After clicking **Install** or **Uninstall** a window opens with the following options:

1. **Selection of computers** – List of devices or groups on which the task will be executed.
2. **Installation/uninstallation command** – Field populated with the command defined in the repository (editable).
3. **Permissions** – By default the service runs with system privileges, however the user can change the privilege level.
4. **Schedule installation/uninstallation date** – Select a date from the calendar or run now.
5. **Add scripts**:
   1. Pre-installation/pre-uninstallation script.
   2. Post-installation/post-uninstallation script.
6. **Add auxiliary files** – Up to 10 MB.

<img src="/files/ce5764926feb26e389c5a8617bcc575157409c2a" alt="" width="375">

## **Application catalog (feature in preparation)**

The **Application catalog** allows employees to install IT-approved applications from the employee portal.

### **Application kiosk schemes**

* **Scheme name** – Unique name of the scheme.
* **Creation date** – Information about the date the scheme was added.
* **Assigned employees** – List of users assigned to the scheme.
* **Application list** – Presented as tiles. If the number of applications exceeds the view limit, a "+\[number]" tile appears.
* **Activity switch** – Enables/disables the scheme.

<figure><img src="/files/e3eea1ce576f6567e8356a14eba9240f0e8733b5" alt="" width="375"><figcaption></figcaption></figure>

### **New scheme**

Clicking **Add new catalog** opens the form:

1. **Scheme name** – Required field.
2. **Description** – Optional description of the scheme.
3. **Scheme activation** – Enable or disable the scheme.
4. **Assign applications** – Selection of applications from the public or private repository.

<figure><img src="/files/4548dc37f59f8eef660876597f931835d2cbb1e3" alt="" width="375"><figcaption></figcaption></figure>

## **Ongoing operations**

The view presents active operations related to application installation and uninstallation.

* **Delete record** – Removes the entry.

<figure><img src="/files/614259acd65dfbeafcd1503c9c9fd74803131bb0" alt="" width="375"><figcaption></figcaption></figure>

## **Logs**

Tab **Logs** allows monitoring the history of installation operations.

**Log table columns**

* **Log date** – Date of the log entry.
* **Application** – Name of the application being installed.
* **Category** – Application category.
* **Operation** – Status information: Installed, Uninstalled.
* **Operation date** – Date the operation was requested.
* **Status** – Operation result: Installed / Error / In progress.
* **Computer** – Device name.
* **User** – Who initiated the operation.
* **More information** – Clickable button allowing inspection of operation details.

<figure><img src="/files/69f192f2c9e385411f10050529393aab6954e31d" alt="" width="375"><figcaption></figcaption></figure>

{% hint style="info" %}

### **Installation error**

The most common reason for an error is the message: ***The script failed to install because the file \[xyz.exe or xyz.msi] could not be found at the specified path \[path].***\
In such a case check:

* whether the file path is correct,
* whether the file actually exists on the disk; the file may have been accidentally deleted,
* the installer has not been updated to a newer version. In that case verify the installer configuration in the system.&#x20;
  {% endhint %}

## **Summary**

The installation server in the eAuditor system is a comprehensive application management tool that enables:

* Centralized management of software installation and uninstallation.
* Allowing users to install approved applications.
* Monitoring and automating installation operations within the organization.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://eaclouddoc.eauditor.eu/eacloud-docs-en/features/it-management/installation-server.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.