{"id":14875,"date":"2023-05-17T15:30:15","date_gmt":"2023-05-17T13:30:15","guid":{"rendered":"https:\/\/www.praim.com\/?p=14875"},"modified":"2023-05-17T16:27:08","modified_gmt":"2023-05-17T14:27:08","slug":"a-beginners-guide-to-praims-profiles-and-policies","status":"publish","type":"post","link":"https:\/\/www.praim.com\/en\/news\/a-beginners-guide-to-praims-profiles-and-policies\/","title":{"rendered":"A beginner\u2019s guide to Praim\u2019s Profiles and Policies"},"content":{"rendered":"

After talking in general about Praim products and solutions and, above all, about the business needs and requirements they can satisfy, it’s time to go into more detail about some of the most important and interesting features of ThinMan<\/a><\/strong>, the centralized endpoint management console. In this article of the #Praim4Beginners<\/a> series we\u2019ll talk about what “Configuration Profiles” and “Device Policies” are<\/strong> and how these features can integrate with other Praim solutions.<\/p>\n

Therefore, a brief excursus is needed on what Praim’s client software can do: Agile (agent for Windows devices) and ThinOX (firmware). In fact, through the configuration interface of the two solutions, it\u2019s possible to modify numerous configurations: <\/strong>from the type of connection to remote resources (via VDI or via browser, for example), to the setting and personalization of security measures aimed at regulating the access of each individual user (or groups); from connecting different local devices to using and updating certificates; from network configuration and setup, to the Wake on LAN (or WOL), which manages the switching on and off of local and remote devices. After configuring and customizing the workstation, thanks to the Configuration Profiles <\/em>and Device Policies <\/em>functions of ThinMan, it will be possible to replicate everything quickly and easily on other devices.<\/strong><\/p>\n

Profiles and Policies, what’s the difference?<\/strong><\/h3>\n

Basically, Configuration profiles<\/em> represent the set of all the individual configurations <\/strong>(or settings) of a device; Device policies<\/em>, on the other hand, are the rules <\/strong>that establish which configurations (which profiles) must be considered and to which (other) devices these must be applied. In short, it could be said that Configuration Profiles represent the \u201cwhat\u201d and Device Policies the \u201chow\u201d.<\/p>\n

Configuration Profile<\/strong><\/h3>\n

The first step to use this feature in ThinMan is to create, using Agile or ThinOX, the desired configuration of the endpoint. <\/strong>Within the ThinMan console, simply select the device just configured and choose the menu item “Offline configuration – Receive from device<\/em>” to allow the configuration set in Agile (or ThinOX) to be imported directly into the console. It will later be possible, based on the imported configuration, to create a Configuration Profile and set the related Device Policies (from the “Add New Device Policy<\/em>” menu).<\/p>\n

Device Policy<\/strong><\/h3>\n

Once the steps described above have been performed, the Device Policy will require some further actions in order to be automatically distributed and used <\/strong>by other devices as well.<\/p>\n

In fact, further settings are possible within the policies:<\/p>\n