A beginner’s guide to Praim’s Profiles and Policies

2020-06-24T10:04:41+02:00June 23rd, 2020|

Previous #Praim4Beginner’s guides have provided brief overviews of the technologies and products that Praim specialise in. With this article, the intention is to delve into how specific aspects of the Praim solution integrate with each other, specifically what Configuration Profiles and Device Policies are. The focus of the guide will concentrate mainly on how Praim’s management product, ThinMan, works with the Praim Thin Clients and software solutions.

Praim’s endpoint client firmware and software, either Agile or ThinOX, provides a fully configurable interface to access a service. From the Agile or ThinOX interface, a connection to a resource, local user and device security, certificates, network settings, device logon/logoff behaviour and personalisation is made. With this environment set, replicating to other Agile or ThinOX devices can now be achieved by using ThinMan’s Configuration Profiles and Device Policies.

Profiles and Policies, what is the difference?

Simply, a Configuration Profile is the configuration and settings for an endpoint. The Device Policy is the who, what and how it is to be applied.

Configuration Profile

Once the endpoint configuration has been setup to your satisfaction in Agile or ThinOX, the Configuration Profile is ready to be created in ThinMan. By simply highlighting the configured device in the ThinMan console, and selecting Offline Configuration – Receive from Device, the device is interrogated with all the settings made in Agile and ThinOX being retrieved into ThinMan. The Configuration Profile can now be created from this data. Praim simplify the profile and policy creation process to a single task by using the Add Policy – Device Policy feature from the Offline Configuration menu.

Device Policy

The Add Policy – Device Policy steps have now created both a Configuration Profile and a Device Policy. The Device Policy still requires some specific setup to make it ready to deploy the configuration to other devices. Within the newly created policy Propertiesoptional user authentication can be enabled and defined, how the policy behaves is applied, and finally which devices or groups of devices are to receive the Configuration Profile. The Device Policy settings will now deploy the original Configuration Profile automatically to all the intended devices.

Policies and Profiles – good to know….

All the Praim Profiles are categorised into a Family group. Currently there are 3 different family groups which are based on ThinOX 32-bit (10.x.x), ThinOX 64-bit (11.x.x) and Agile. What this means is that a configuration profile that was created for a Praim Thin Client with version 11.0.9 firmware for example, will work with earlier and newer versions of firmware, as well as on different devices which are running the same family of the firmware. The same is also true for the Agile family, so providing a common interface and configuration for Windows, Raspberry Pi and soon, Linux.

It is also possible to modify the Configuration Profile properties for ThinOX clients, so allowing centralised modification of the Configuration Profile. Other than making changes to the settings, this is beneficial if expired certificates need renewing, or if the connection to the remote service changes.

Conclusion

By using Configuration Profiles and Device Policies it provides a rapid, manageable and dependable method to administer an endpoint estate. These features are available throughout the whole range of Praim hardware and software solutions.

Downloading the trial software for ThinManThinOX4PC and Agile4PC will enable anyone to experience the benefits that the Praim solution offers.