Download & Distribute NCSs

Download and distribute work orders and reservations using a parameter-driven API URL.

Overview

Work orders and reservations can be downloaded using a parameter-driven API URL:

https://yoururl.mcs.com/myspeed/dstl

This URL accepts parameters for downloading both standard work orders and reservations.

Work Orders

https://yoururl.mcs.com/myspeed/dstl?a=swo_name&u=result_id
KeyDescription
a Required. Exact name of the work order (e.g., voiptests).
u Optional. Session ID to use. If omitted, it is automatically generated from the hardware (typically the computer name).
t Optional. Target operating system or custom satellite. Default is Windows. Use t=mac for macOS, t=lin for Linux, or a numeric value (e.g., t=7) for a custom satellite binary.

Reservations

https://yoururl.mcs.com/myspeed/dstl?a=swo_name&k=ACDF5C2D
KeyDescription
a Required. Exact name of the work order (e.g., voiptests).
k Required. Exact reservation key (returned when the reservation is created).
u Optional. Session ID to use. If omitted, it is automatically generated from the hardware (typically the computer name).
t Optional. Target operating system or custom satellite. Default is Windows. Use t=mac for macOS, t=lin for Linux, or a numeric value (e.g., t=7) for a custom satellite binary.

Note: The work order name must match the one defined in the reservation, and the reservation key must exist. Mismatches will result in an error.

Custom Satellite Specification

This feature is intended for MCS deployments that require support for multiple satellite binaries, such as custom branding, specialized functionality, or market-specific deployments. Visualware can generate custom satellite binaries upon request.

Note: Server-level access is required to configure and enable this feature.

Within the MCS root directory, locate the configuration file named local.ini. Each custom satellite must be declared using the following syntax:

CustomSatelliteX=customsatellite.exe

Replace X with a numeric value greater than 6. Each key must be unique — duplicate key names are not supported.

The referenced satellite binary must be placed in the /MCS Root/www/ directory and referenced by its exact filename including the extension. For example:

CustomSatellite7=customsatellite.exe

Once defined, the custom satellite can be selected by supplying the t parameter with the same numeric value. For example: t=7