In order to upload a file to a thin client, it must be assigned to the thin client either directly or indirectly via a thin client directory or profile.

Via drag and drop, move the file to the thin client directory or integrate the file on the thin client itself in the Assigned objects window via the symbol as you would when assigning profiles.
If a file has been assigned to a profile, it will be transferred to the assigned clients along with the profile settings.

When the UMS settings are transferred, a file assigned in this way will be copied to the thin client, e.g. while the thin client is booting. As long as the file is assigned to the thin client, it will be synchronized with the file registered on the UMS server, for example if the file bookmarks.html is replaced by a new version. The MD5 checksum for the file assigned to the thin client is compared to the registered file. If the checksums differ from each other, the file will be transferred again.

Up until UMS Version 5.02.100, the thin client must be able to contact the UMS server with its fully qualified domain name (e.g. mytcserver.mydomain.tld). From UMS Version 5.02.100, the IP address of the UMS will be used when transferring the file. This ensures that the transfer works even in the event of DNS problems.

If a file was directly replaced in the file system in the ums_filetransfer directory, it must be updated in the UMS console using the command Update file version from the file's context menu. The UMS server will otherwise not recognize the change in the file version.