> For the complete documentation index, see [llms.txt](https://eaclouddoc.eauditor.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://eaclouddoc.eauditor.eu/eacloud-docs-en/features/it-management/remote-installation/installer-preparation.md).

# Installer preparation

Before deploying the application, prepare its configuration in the private repository. The installer specifies the file, the installation command, the optional uninstall command, and the method for verifying the result.

### Adding an application to the private repository

{% stepper %}
{% step %}
Go to **IT Management > Installation Server**.
{% endstep %}

{% step %}
Open the private repository and click **Add application**.

<div align="left"><figure><img src="https://3262380731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdzip3GyvGq5q5J3qckWN%2Fuploads%2FOfH29rL96NnlRLyEzO9A%2Fimage.png?alt=media&amp;token=e9b4f9be-c3a8-4cb3-9f04-6662d31a8891" alt="Dodaj aplikację" width="375"><figcaption><p><em>Add the application.</em></p></figcaption></figure></div>
{% endstep %}

{% step %}
Add the installation file `.exe` or `.msi`.

<div align="left"><figure><img src="https://3262380731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdzip3GyvGq5q5J3qckWN%2Fuploads%2FvwE0ZDPVj15NRH3Ocuwb%2Fimage.png?alt=media&amp;token=1e894808-9eb3-45fd-aadd-e004b6237890" alt="Dodaj plik instalacyjny .exe lub .msi." width="375"><figcaption><p><em>Add the installation file.</em></p></figcaption></figure></div>
{% endstep %}

{% step %}
Fill in the application name, category, vendor, and version.
{% endstep %}

{% step %}
Silent installation command.

The installation command should run the installer in silent mode, without requiring the user to confirm subsequent windows. This allows the application to be deployed remotely and without intervention on the endpoint computer.

The method for starting a silent installation depends on the application vendor and the installer used. eAuditor cloud passes the specified command for execution, but does not define its parameters.

Refer to the application vendor's or installer's documentation for the correct parameters.

Example commands:

```
chrome_installer.exe /silent /install
setup.exe /quiet /norestart
installer.exe /S
installer.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART
msiexec /i aplikacja.msi /qn /norestart
```

{% endstep %}

{% step %}
Optionally enable and fill in the uninstall command.
{% endstep %}

{% step %}
Specify the method for verifying the installation and save the application.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
Parameters such as `/silent`, `/quiet`, `/S`, `/VERYSILENT` or `/qn` are only examples. Each vendor may use different switches, so before deploying to a larger number of computers, test the command on one device.
{% endhint %}

### Installation verification

Verification checks whether the application was installed correctly and is available on the computer. The system can check a process, a Windows registry entry, or the presence of a file in a specified location.

Depending on the application, fill in the appropriate field or fields. For example:

| Method         | Example                                                      |
| -------------- | ------------------------------------------------------------ |
| Process        | `chrome.exe`                                                 |
| Registry entry | `HKEY_LOCAL_MACHINE\\SOFTWARE\\Google\\Chrome`               |
| File path      | `C:\\Program Files\\Google\\Chrome\\Application\\chrome.exe` |

For example, for Google Chrome you can verify installation through the running process `chrome.exe`, the vendor's registry entry, or the presence of the executable file in the installation directory.

<figure><img src="https://3262380731-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fdzip3GyvGq5q5J3qckWN%2Fuploads%2FoFKwVNFeWZerYSw5zoMh%2Fimage.png?alt=media&amp;token=5cae6355-d428-4d3b-a136-455da5033d12" alt="Weryfikacja instalacji na podstawie procesu, wpisu rejestru lub ścieżki do pliku."><figcaption><p><em>Verification of installation based on a process, registry entry, or file path.</em></p></figcaption></figure>

{% hint style="info" %}
Verification should refer to an item that actually exists after the application has been installed correctly. Do not copy sample values without checking them on a test computer.
{% endhint %}

### Uninstall command

The uninstall command is defined when adding or editing the application. This is the command the system will use later when remotely removing the program.

As with installation, the uninstall method depends on the application vendor and the installer used. eAuditor cloud passes the specified command for execution, but does not define its parameters.

Refer to the application vendor's or installer's documentation for the correct uninstall command.

Example commands:

```
"C:\Program Files\Google\Chrome\Application\setup.exe" --uninstall --force-uninstall --system-level
msiexec /x {PRODUCT-ID} /qn /norestart
uninstall.exe /silent
unins000.exe /VERYSILENT /SUPPRESSMSGBOXES /NORESTART
```

{% hint style="warning" %}
Before saving the installer, test the installation and uninstall commands on one computer. An incorrect parameter can cause the installation to fail or remove the program without fully cleaning up its files.
{% endhint %}

### FAQ

<details>

<summary><strong>Can one installer contain additional files?</strong></summary>

You can add an additional file when starting a task as an auxiliary file. The maximum size of an auxiliary file is 10 MB.

</details>

<details>

<summary><strong>Can I edit an application from the public repository?</strong></summary>

No. Applications from the public repository are prepared by the vendor and cannot be edited.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://eaclouddoc.eauditor.eu/eacloud-docs-en/features/it-management/remote-installation/installer-preparation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.