Earlier topics in the #Praim4Beginner’s guides have touched on some of the basic topics for thin clients and how Praim provides the software and hardware to implement a managed solution to connect to a VDI environment. This article will look at the post deployment and implementation phase and address some questions regarding updates.
What can be upgraded, how are updates managed and is it necessary to update at all?
All updates and software are downloadable from MyPraim. From the dashboard, the Products>Download section will list all the available updates. The updates will be deployed through ThinMan, so having a working and active ThinMan environment is essential.
Praim are constantly developing and releasing new features for both their software and firmware products. This can include updates from Praim’s technology partners as well as customer led improvements. To determine if these updates are of relevance, the release notes are available on the Wiki for all versions. With an understanding of what has been included in an update a decision can be made on applying any updates. Often, a thin client estate will follow the “if it’s not broke, don’t fix it” ethos. However, service upgrades often provide improvements or newer functionality which can only be experienced with an upgraded client.
How to update
As mentioned previously, ThinMan is the way that updates are applied for Praim products. ThinMan also checks for updates for itself and will advise when a newer version of ThinMan is available to install.
If endpoint devices require an update to be applied, the firmware is downloaded from MyPraim based on the device type (in the case of ThinOX) or application (Agile). These files have a file extension of PAR. The downloaded files then are imported into ThinMan’s Package Repository.
With updates installed and available in ThinMan, devices then can be updated. This can be done on a device-by-device basis, by selecting multiple devices or through using ThinMan Event Activities or Scheduled Activities. For Windows Embedded devices (Windows 10 IoT), ThinMan will automatically manage the devices Write Filter status to apply the newer version of Agile.
With all updates, a device reboot will be required, so using a Power On/Off/Reboot event or using the Scheduler to apply any update out of hours will reduce any disruption for the users to a minimum.
Praim have recently released a series of Getting Started guides and videos at to help configure ThinMan. These are constantly being added to.