The Package Repository stores all the file needed for upgrade operation on the thin clients. It includes ThinOX firmware files, Windows CE Firmware files, Praim WES7 Service Pack or Hotfix files, TCe Virtual desktop Agent and TCe Workstation Client update files, Teradici Firmware files, Executable setup files (for Third Party Software installation), scripting files, and so on. It is a central repository that can be accessed from Local or Remote Console.
¶ Operations on Packages
There are several operations that can be executed on packages.
¶ Add a Package
Click on "Add" to add a file in the Package Repository.
Click then on "Browse".
Select from the file explorer windows the file that has to be imported in the Package Repository and click "Open".
Once imported the file is available on the Package Repository for all the firmware upgrade and software distribution operation (both manual or automatic, through activities, operation).
Note that these types of file will be imported into the Package Repository:
- "Praim Archive" is the format for all the new packages that will be provided by Praim. The files have the extension "PAR".
- "ThinOX Firmware" is the oldest firmware file used to upgrade a ThinOX Thin Client, typically the name of the file is "<modelname>_<version>.tar", e.g. "C9050_8.7.23.tar".
- Windows CE(WT) Firmware: is the firmware file used to upgrade a WinCE Thin Client, tipically the name of the file is "<modelname>_<version>.cmcefp", e.g. "WT9100-U_6017.cmcefp".
- Praim Service Pack: the oldest Service Pack that allows updating Windows devices from a version to the next one (remind that connections client like VMware Horizon View and Citrix Receiver are note contained in a Service Pack).
- Praim Hotfix: the oldest Hotfix allows to update only a part of the Windows firmware and does not upgrade the firmware version.
- Executable Setup: it is used to execute a *.exe file using (typically an installer) on a Windows device (see more on Contextual Menu - Device Update (Windows Devices only)).
- Windows Installer: it is used to execute a *.msi file using (typically an installer) on a Windows device (see more on Contextual Menu - Device Update (only for Windows Embedded devices ).
- Powershell script: it is used to execute a *.ps1 file using on a Windows device (see more on Contextual Menu - Device Update (Windows Devices only)).
- Batch Command: it is used to execute a *.bat file using on a Windows device (see more on Contextual Menu - Device Update (Windows Devices only)).
- Teradici Firmware: is the firmware file used to upgrade a Teradici Thin Client.
¶ Edit a Package
Clicking on "Details" allows inserting more information on the selected package.
"Notes" field collect generic information that will be visible for all the users using the Package Repository.
"Apply to min. version" field may be configured with a version number. ThinMan compares the version number with the one present on the thin clients, and the package is installed if the version on the device is at least the version inserted in the field. This check allows a more strict control over software installation and distribution.
"Apply to max. version" field may be configured with a version number. ThinMan compares the version number with the one present on the thin clients, and the package is installed if the versions on the device is up to the version inserted in the field. This check allows a more strict control over software installation and distribution.
The previous fields could be editable or not, depending on the type of package.
For packages of type "Third-Party Software" (e.g., "*.exe", "*.msi", "*.bat", or "*.ps1"), other fields are available on the bottom of the window.
Depending on the type of the file the values in the fields may vary (e.g., the screenshot above is about a "*.msi" package).
The "Default" button suggests the values that ThinMan will use, and reset the modified values.
Note that the inserted values are proposed when you update a device with the package above. This is valid in case of manual command (see Contextual Menu - Device Update (only for Windows Embedded devices) at chapter "Third-party Software Installation") or for Automatic operation (like Scheduled Activities or Event Activities).
¶ Remove a Package
Clicking on "Delete" will permanently delete the selected package from the Package Repository. Not only it is removed from the list but also the file system.
¶ Refresh a package
The newly inserted package have a status that indicates when they are ready to be used. Only packages with "Ready" status can be used to execute software upgrade or distribution. In case a package is not in the "Ready" status select it and click on the "Refresh" button to update its status.
¶ Export a Package
Click on "Export" will export the captured Image (e.g. Windows 10 IoT) in a file. Be aware this operation could take some time. This file could then be used to restore a device using the Praim Toolkit software (see Praim Toolkit User Guide).
¶ Replica Status
See the link Manage the ThinMan Gateway from the ThinMan Console to know more about Repository Replica.
¶ Package Repository and ThinMan Gateway
If ThinMan Gateways are available in the network (see ThinMan Gateway User Guide), please read the link Manage the ThinMan Gateway from the ThinMan Console to manage them properly.