Command Distribution Tasks

Introduction

The Command Distribution Tasks feature allows the remote execution of commands on Windows devices through a centralized ITAM interface.

Commands are sent as standard Command Prompt (CMD) instructions, similar to prompts executed in cmd.exe.

Important limitations:

• PowerShell commands are not supported
• Commands are executed remotely without returning execution output to the console
• The system only reports whether the task was successfully delivered to the target device

This feature is typically used for lightweight automation, diagnostics, and administrative tasks across multiple endpoints.

---

Requirements

The prerequisites are the same as those defined for Agent Distribution Tasks:

• Compatible agent version with remote distribution modules installed (Auto Update 3.3.3 or higher)
• Proper firewall rules allowing communication:
  • lad1-smartcenter.almaden.app
  • lad2-smartcenter.almaden.app
  • Port 443
• Supported OS: Microsoft Windows only

---

Access Path

Navigate to:

Menu > Remote Management > Wan Distribution > Command Distribution Tasks

---

Task Configuration

Status

Define the initial state of the task:

• Active
  The task is immediately executed upon saving.
• Inactive
  The task is saved but will not be executed until manually activated.

---

Task Name

Define a clear and identifiable name for the command distribution task.

Example:

• Collect system information
• Network diagnostics script
• Disk usage validation

---

Description

Provide a detailed description of the purpose of the command execution.

This should help administrators understand:

• Why the command is being executed
• What the expected outcome is
• Which devices or departments are targeted

---

Command

The command field defines the instruction that will be executed remotely on the target devices.

Behavior

• Commands are executed as batch-compatible CMD instructions
• Execution is performed remotely
• No execution output is returned to the ITAM interface
• The system only confirms delivery status (success/failure of task distribution)

---

Example Use Case

A common usage pattern is to execute a batch-style command that collects system information and saves logs locally on the device.

Example: Collect system information and save to C:\Temp

@echo off
setlocal

if not exist C:\Temp mkdir C:\Temp

systeminfo > C:\Temp\system_info.txt
ipconfig /all > C:\Temp\network_info.txt
whoami /all > C:\Temp\user_info.txt

Description of the example:

• Creates the folder C:\Temp if it does not exist
• Collects system information using systeminfo
• Collects network configuration using ipconfig /all
• Collects user context information using whoami /all
• Saves all outputs locally on the device for later analysis

---

Important Notes

• Commands must be written in CMD-compatible syntax
• PowerShell scripts or commands are not supported
• There is no real-time output or response returned to the console
• Validation must be done by checking generated files or device-side logs