Downloads a file via http/https and Hash. Possible sources:
- Public web server. e.g. download software directly from the manufacturer's site.
- Private webserver which is located on the internet. Can be secured with http username/password.
- Internal web server. e.g., a NAS (Network attached Storage). If your company has multiple sites, variables can be used to refer to local servers per site.
- URL: A download is attempted in chronological order. This can be used to achieve a download fallback, for example.
- URL Internal server: is used by all devices that are in the internal network and saves the WAN line.
- URL external server: for all devices that are external this fallback is used.
- Filename after download: Often it happens that the filename contains the version number. In case of a version update, the following workflow would have to be adapted. With the Filename after download option, it is possible to always use the same name for the subsequent workflow.
- Download Directory: By default, the file is stored in the working directory of the XEOX agent. This directory will be cleaned up by the agent automatically after the job is finished. Alternatively, any directory can be specified. See: Working Directory (Please create your own KB article).
- Authentication: The download can be secured with a user/password.
- Proxy: A proxy server (optionally with authentication) can be specified. In case of multiple sites, variables can also be used here.
If the software consists of several files, you have to use either more than one download action (for legacy, you can alternatively use the other download, where you can enter multiple files) or pack the software into a ZIP file.
About URL and Paths
If a user doesn’t explicitly enter a destination path: An automation ran on a device will create a work folder C:\Program Files\XEOX . There, seperated by ID will be the data of the jobs. If no destination path is stated, files will be stored here.
You cannot enter path variables like %username% or %temp%.
It does not matter if a / is entered at the end of a path or not