13.5 Software Distribution

Through the AnySecura console, administrators can automatically distribute and install software on client machines, or copy specific files or applications to clients. Using the software distribution feature, administrators can quickly deploy software and business applications across the entire network, significantly reducing their workload.

To create a distribution task, go to Assets Management → Software Distribution. The distribution process involves two steps: creating a distribution package and creating a distribution task. The task will then deploy the prepared package to the specified client machines.

13.5.1 Distribution Package

Administrators must first create a distribution package. The package defines the parameters required for distribution, is stored on the server, and can be reused multiple times.

Click the New button "add icon" to create a distribution package. The information required when creating a package includes: General Information, File Information, Detection Conditions, and Prerequisites.

Set General Information

First, configure the general information, including:

Field Name Description
Package Name Default is "New Package." Administrators can modify the name, but it cannot be empty.
Creation Time / Modification Time Automatically generated by the system; cannot be edited. Initially empty when creating a new package. After creation or later editing, the creation time and administrator name are displayed. Modification time updates whenever the package is modified.
Operating System Select the OS versions applicable for this package. Multiple selections are allowed; all are selected by default.
System Language Select the system language applicable for this package. Default is "All."

Set File Information

Switch to the File Information tab on the left to configure the package's files, including:

Field Name Description
General Includes package size, computer name, and original path.
Package Size Size of the package after creation (read-only).
Computer Name Name of the computer where the console is running when creating the package (read-only).
Original Path Original path of the package file (read-only).
Distribution Mode Three options: Install Software, Execute Program, and Distribute File.
Install Software Distribute an application installer to the client and install it.
Execute Program Execute a specified program on the client only once.
Distribute File Distribute specified files to the client.
Command Line Required when Install Software or Execute Program is selected. Typically the core installer or program file name. Can be entered manually or extracted from the file list by right-clicking and selecting Use File Name as Command Line.
Target Path Required when Distribute File is selected. Specifies the path on the client machine. Default: {desktop}\deploy files.
Run Mode Run as current logged-in user uses the client's logged-in user permissions. If unchecked, the program runs under the system (SYSTEM) account.
File List Displays all files and directories in the package. Columns include File Name, Size, Modified Time, and Version. Use the Add button "add icon"to select files/folders. Multiple files/folders can be added simultaneously but must be under the same parent folder. Each time you click Add, a new file list is created, automatically replacing the previous list.

Set Detection Conditions and Prerequisites

Detection Conditions: These define the criteria for determining whether the software has been successfully installed. The client automatically checks these conditions; if met, the installation is considered successful. If not, the client will continue attempting installation. Detection conditions are mandatory for "Install Software" mode, but not required for other distribution modes.

Prerequisite Conditions: These specify the conditions that must be satisfied for the package to be executed. Before distributing the package, the client checks these conditions: if satisfied, the package is deployed; otherwise, deployment is skipped. Prerequisites are optional.

For different system and software environments, detection and prerequisite conditions can be set in five types:

Detection Condition Description
File Checks whether a specific file exists; requires full file path input.
File Version Checks a file along with its version; requires full file path input.
Registry Key Checks whether a specific registry key exists.
Registry Value Checks a specific registry key and its value for more precise validation.
Installed Software Generally refers to programs listed in "Control Panel → Add/Remove Programs."

Example of Detection Conditions:

The following are the detection conditions for creating a Microsoft Office 2003 installation package.

Condition Type Logic Content
File Exists {pf}\Microsoft Office\OFFICE11\EXCEL.EXE
File Version >= 11.0.5612.0
Registry Key Exists SOFTWARE\Microsoft\Office\11.0\Access\InstallRoot
Registry Value Exists SOFTWARE\Microsoft\Office\11.0\Access\InstallRoot – Path
Installed Software Contains Microsoft Office Professional Edition 2003

Note:

  • The specified file path in a condition can include predefined macros, such as:
    • "tmp" temp folder(c:\windows\temp)
    • "win" windows directory(c:\windows)
    • "sys" system directory(c:\windows\system32)
    • "sys32" system directory (32-bit: c:\windows\system32; 64-bit: C:\Windows\Syswow64)
    • "pf" program files(c:\program files)
    • "pf32" Program Files (32-bit: c:\program files; 64-bit: C:\Program Files (x86))
    • "sd" system drive(c:\)
    • "cf" common files(c:\program files\common files)
    • "cf32" common Files (32-bit: c:\program files\common files; 64-bit: C:\Program Files (x86)\common files)

Package Deletion and Modification

Deletion removes the package, while editing allows modification of its parameters, conditions, and other settings. A package can only be deleted or edited when its status is "Ready". A package is considered Ready if no distribution tasks are currently using it.

13.5.2 Distribution Tasks

After creating a distribution package, you need to create a distribution task to assign it to target computers. In the Distribution Task view, click the New button "add icon" in the top-right corner to create a task.

Settings for a distribution task include:

Field Name Description
Task Name Default name is "New Task"; administrators can modify it. The name cannot be empty.
Package Name Click the "…" button to select the distribution package to use.
Maximum Retry Attempts Specifies how many times the task will retry if distribution fails. Default is 10; can be changed to any other integer. Entering 0 means the task will keep retrying indefinitely until successful, unless manually stopped.
Status Displays the current status of the task. Click the Settings button to configure execution mode and schedule.
Execution Mode Continuous Execution: The task will run repeatedly according to the specified schedule. If "Stop execution after successful distribution" is checked, the task will cease on the client once the distribution succeeds. Execute Once: The task will run only a single time. Regardless of success or failure, it will not run again after completion.
Execution Schedule: Execute immediately: The distribution task runs as soon as it is created. If the client is offline, it will execute the next time the client starts. Execute at computer startup: The task runs when the client computer starts. If the client is online, a restart is required for execution. Execute at a specified time: The task runs at the set time according to the schedule.
Target Computers: Click the "select icon" button to select the client computers that will receive the distribution task.

After configuring the task properties, click OK to start the distribution task immediately. You can monitor the task status in the task list.

The available information includes:

Field Name Description
Task Name The name assigned when the task was created.
Package Name The name of the distribution package selected at creation.
Task Status The current status of the task.
Successful Count Number of target computers where the task was successfully distributed.
Failed Count Number of target computers where the task distribution failed.
In Progress Count Number of target computers where the task is still in progress.
Other Count Number of tasks in other statuses, calculated as total tasks minus the sum of successful, failed, and in-progress counts.
Planned Install Count Number of installations planned for this task, i.e., the number of target computers selected at creation.
Total Tasks Total number of tasks; each selected target computer counts as one task.
Installation Success Rate The success rate of task distribution, calculated as the ratio of successful count to planned install count.

Distribution tasks can also be deleted or edited. During the task distribution process, deletion and editing are not allowed. You must first stop the task (by right-clicking the task and selecting Stop) before performing delete or edit operations.

Copying a Distribution Task

In the distribution task list, right-click the selected task and choose Copy this Distribution Task. A new task creation dialog will appear, allowing you to create a new task based on the selected one. In the new dialog, the Package Name is empty, while all other settings are carried over from the original task.

Note

  • If the package used by a task in the distribution list is marked as Package in Use, it cannot be deleted or modified. Only after deleting the distribution task will the corresponding package status return to Ready.