> 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/tasks.md).

# Tasks

## **Task Server**

The Task Server enables IT administrators to remotely manage PowerShell and CMD scripts on Windows computers. Through integration with advanced features such as a built-in repository of ready-made scripts and the ability to generate scripts using artificial intelligence, this function significantly streamlines administrative, security, and maintenance tasks.

**Main features:**

1. **Remote script execution** – Ability to run PowerShell and CMD scripts on one or multiple computers.
2. **Task management** – Creating, editing, scheduling, and deleting scripts from the interface.
3. **AI script generation** – Use of artificial intelligence (ChatGPT) to automatically generate scripts based on natural-language commands.
4. **Built-in repository** – Approximately 200 predefined scripts divided into categories, e.g., Administration, Network, Security.

### **Main view**

Interface **Task Server** has been divided into three main sections:

1. **Scripts**
2. **Script schedule**
3. **Logs**

<div data-full-width="true"><img src="/files/4c4ab72881f20676d099a5f5a081b51c05672cf6" alt="" width="375"></div>

## **Scripts**

This section provides an overview of all available scripts, both predefined and added by the administrator.

**Table columns:**

* **Script name** – Unique script name.
* **Created** – Date the script was added.
* **Modified** – Date of the script's last modification.
* **Description** – Optional brief description of the script's purpose.
* **Script type** – Icon indicating the script type: PowerShell or CMD.
* **Command -** Command content, code executed by the script.
* **Group -** The category to which the script is assigned.
* **User tasks** - Indicates that the script was created by a system user and does not come from the public script repository.

Widgets display information about the number of scripts executed over the last 7, 30, or 365 days. They let you quickly check **how many scripts were run and whether errors occurred during execution.**

If any script ends with an error, the appropriate icon indicating a problem will be displayed next to the widget. Detailed error information is available in the Logs tab.

The second widget presents **the number of executed PowerShell scripts**which makes it possible to quickly assess the scale of usage of this script type in the environment.

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

## **New script**

Clicking the button **+Add new script** opens the side configuration menu.

* **Script name** – Required field.
* **Script group** – Select from the list of existing categories or add a new one.
* **Language** – PowerShell or CMD.
* **Description** – Optional brief description of the script.
* **Script content** – Field for entering the full script code.
* **eA Inteligence** - Enables script generation with AI assistance.

<figure><img src="/files/6cb284da8f6a457b66fbf74f223c493245b75df5" alt="" width="235"><figcaption></figcaption></figure>

### **Script groups**

Above the table is a view filter by category. The categories include:

* Active Directory
* Administration
* Teams / .NET libraries
* Computer
* Files and folders
* Firewall
* Hardware
* System patches
* Logs
* Maintenance
* Network
* Paging file
* Processes
* Security
* Services
* System
* System Restore
* System Registry

**Script group** – Ability to add new categories or remove existing ones (confirmation required).

<img src="/files/5df6f74b9064e1888c53aed37c60282e27dacd24" alt="" width="375">

### **AI script generation**

At the bottom of the menu is the section "**Need more clarification? - Use eA Inteligence".**

<figure><img src="/files/e44cb120c09ffb74a7ad7d893cb0fe58d45d2c69" alt="" width="234"><figcaption></figcaption></figure>

It enables generating scripts using artificial intelligence.

After clicking “**Use eA Intelligence**” the AI integration panel opens. The administrator describes the expected outcome, e.g., “Create a script that restarts the xyz service.” The system generates a ready script that can be edited before saving.

Artificial intelligence remembers the conversation context, making it possible to continue improving and extending the script without having to describe the entire task again.

After clicking “**Copy code**” the script content is automatically pasted into the section where it should be entered.

The function also allows starting a new conversation with AI at any time by restarting.

<img src="/files/7fa9bfe33be58fa55e23f1627a1d9ffe6ac70d75" alt="" width="375">

## **Script execution**

### **Script execution procedure**

1. **Launching the script** – Clicking Run for the selected script opens the menu with execution parameters.

<img src="/files/48374426dea0ddbd150ca517c9653ae6cd2c3edf" alt="" width="375">

2. In the next step, we choose **Configure the execution command**

<figure><img src="/files/0dac2a622ecd785b90662aade73ca28f53484de6" alt="" width="239"><figcaption></figcaption></figure>

2. **The next step is parameter configuration**
   1. **Add devices** – Select computers or groups on which the script is to be run.
   2. **Date range** – defines the time period during which the script remains active (If the script is not executed, it expires automatically. For tasks without a schedule, the default active period is 30 days.)
   3. **Permissions** – By default, scripts run with system privileges; however, the user can change the privilege level.
3. **Script execution requires confirmation of the privilege scope**

<img src="/files/7aab410dcb7746ff090e590a51f1935ab7f3a01a" alt="" width="375">

## Script schedule

This section contains information about all script schedules, with the ability to edit, disable, or delete them.

**Table columns:**

* **Script name** – Script assigned to the schedule.
* **Run on**– Computers on which the script runs.
* **Trigger** – Launch source (schedule, automation, DLP).
* **Start** – Start date.
* **End** – End date (or none, if "no end date" is set).
* **Last run** – Date of the last run.
* **User** – Administrator responsible for the configuration.
* **Status** – Current state (active, completed, failed).
* **Task** - The specific command executed as part of the task, e.g., PowerShell “Get-NetIPConfiguration”.
* **Script type** - The script type, e.g., CMD or PowerShell.
* **Category** - The functional category to which the script is assigned.

### **New schedule**

Clicking the button **+Add to schedule** opens the configuration window:

1. **Script selection** – List of available scripts.
2. **Run on**– Adding computers/groups on which the script is to be run.
3. **Date range** – Ability to set a start and end date (or no end date).
4. **Interval** – Option to set recurring execution.

<img src="/files/f8f39c61b2a48d93285523259d7d05de4aa2b0c3" alt="" width="235">

{% hint style="info" %}
**Additional information**&#x20;

The task can be run without a time limit and will continue until it is manually disabled by the administrator. It is also possible to set a maximum number of occurrences after which the task will end automatically, e.g., after 5 executions.
{% endhint %}

The schedule can be disabled by using the trash icon to remove it from the list, or by clicking the pencil icon and editing the settings that define when and how it should run.

## **Logs**

The Logs section enables monitoring of executed tasks and their results.

**Log table columns:**

* **Date** – Log entry date.
* **Computer** – Computer on which the script was executed.
* **Logged-in user** – User logged on to the computer at the time the script was executed.
* **Created by** – Who initiated the task (administrator or user).
* **Run date** – Script execution date (with an icon indicating success or error).
* **Created** – Task creation date.
* **More information** – Clickable button **Read the full log**, allowing access to execution details. This is a detailed technical log. The log may contain percentage progress messages, intermediate statuses (DONE, STOPPED, OK, NONE), and the final operation identifier, e.g., nodeid.
* **Error -** The error message returned during script execution if the operation failed.
* **Description -** A brief description of the task or its execution context.
* **Command -** The command content or script code that was executed.
* **Result date -** The date and time when the script execution result was returned.
* **Group -** The group to which the task was assigned.
* **Host ID -** Unique device identifier in the system.
* **Task log ID -** Unique identifier of the task log entry.
* **Script type -** The type of script executed, e.g., CMD or PowerShell.

<img src="/files/0286be9a398b1b53223375d81c6c8e564548ae1f" alt="" width="375">

Option “**Read the full log**” enables viewing the detailed execution flow of the task.&#x20;

This view also includes integration with **eA Intelligence**. Artificial intelligence can analyze the log content, explain the meaning of messages, indicate the potential cause of the error, and suggest a solution. If needed, AI can also generate a corrected version of the script or propose a new one tailored to the situation.

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

## **Summary**

The Task Server in the eAuditor system is a versatile tool that streamlines remote script management across the organization. With AI integration, a built-in script repository, and an advanced schedule, administrators can efficiently carry out administrative tasks while minimizing time and the risk of errors.


---

# 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/tasks.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.