Added tasks management

Node discovery

Complex scan tasks (i.e. network scan, IP-address scan or Windows workgroup scan) work with previously discovered nodes. The discovery will be performed automatically, but it also can be done manually before scanning starts.

To perform the network discovery, just expand a complex task. The subtasks corresponding to discovered nodes will gradually show up.

      • Repeating the search deletes all subtasks and performs a new node discovery;
      • The Padlock icon shows the way the complex task will be saved.
        • When the padlock is opened, the task is saved without subtasks, and after reloading the search will be performed again. To save the task along with the customized subtasks exactly as they were before saving, click the padlock and it will “close”. About saving scan tasks.

Setting logins

To access a remote node, the TSD scanner requires a login (username and password).

Logins for each task can be set in the Windows column.

Click on an arrow in one of the Windows cells, and the login menu will show up.

This list contains all logins created by the user and the standard login (the current user of the system where the program is run).

To scan an asset, select one of the logins or create a new one by using the Add option.

Along with the username and password, its alias should also be specified when adding a new login. This alias is the unique identifier that will be used to address this login in TSD.

To change the username and password for previously created logins, use the Edit button (the pencil icon) located in front of every login in the list.

Select Ignore to skip the asset during the scan.

Logins for single tasks

Only one login for one of the protocols can be selected for any single task. If the login is not specified, the task will be ignored during scanning.

Logins for complex tasks

Complex tasks can have several logins for each protocol. In this case, access to every asset scanned within this task will be sequentially requested using all specified logins until one of them matches.

tilde (~) in a login cell means that the task uses the logins of a parent task, but another login can be assigned to the task, and it will be used for scanning.

During the first scan of a remote asset, the login that successfully provided access is automatically assigned to it.

Setting a login for a task created with Quick Add

A new task automatically acquires a login entered with additional semicolon-separated login command:

<task creating command>; login <login alias>

For instance:; login Homer

You can also enter several logins separated by commas:; login Homer, Marge

Setting the destination folder

By default, all new assets are placed in the root folder of the Storage.

You can select a folder in the Storage for every task, and the scanned assets will be placed there.

The Destination folder column serves this purpose. Clicking on an arrow in this column will show a menu with the list of all Storage folders.

It’s not possible to create a new folder from this menu. If assets should be placed in a new folder, create it manually beforehand.

You can use an additional “to” command when creating a new task with Quick Add:

<task creating command>; to <path to folder>

EARTH; to Planets; login Homer; to New devices

PLUTO; to Planets\Dwarf planets

Deleting and disabling tasks, exceptions

Deleting tasks

To delete a task, use the Delete button in front of its title in the Task column or select multiple tasks and press Delete on the keyboard.

Disabling tasks

To disable a task without deleting it, tick off the checkbox in front of its title. This can also be done by selecting multiple tasks and pressing the Space bar. To enable or disable all tasks, use the checkbox in the Task column header.

You can create a new task as disabled through Quick Add by using an additional disable command:

<task creating command>; disable

HALLEY; to Comets; disable


You can create an exception task using Quick Add. Just enter a network name or an IP-address with prefix “-” (minus). If the exception task is enabled, the scanner will ignore the specified asset.

Exceptions are convenient to use for scanning networks and ranges. For instance, if one or several assets in the network should not be scanned, you can do the following:

  1. Create a task, expand

    it and wait for all subnodes to be discovered, then delete the unnecessary ones;

  2. Create a task and several exception tasks.

Option 2 is sometimes faster and more handy.