At the heart of the functionality are registry keys that our applications use to enforce the restrictions. You can set these registry keys manually and protect them using permissions, but the best way to deploy them is surely using a Group Policy at the domain level.
Administrative Templates will facilitate the management of registry-based policy settings that are applied on both the computer and the user configuration.
This hierarchy is created when the Group Policy Editor reads XML-based Administrative Template files (.admx), the ADM file is a text file with a specific syntax which describes both the interface and the registry values which will be changed if the policy is enabled or disabled. Since they contain the registry keys that are used, you could actually consult the ADM files to get the list of registry keys that you must use if you intend on doing this manually.
- Disable the application automatic update check
- Disable the x64 edition of the application
- Disable the x86 of the application
- Force the user to always be prompted for the passphrase while connecting to data source.
- Force the user to always be prompted for his credentials while connecting to data source.
- Disable the add-on creation and the Add-on Manager.
- Disable the custom image edition in the session configuration.
- Disable the reveal password for this machine.
- Disable all the local application tools like the Event Viewer or IIS
- Disable the Devolutions Cloud usage
- Disable the menu File - Data Sources on the machine
- Disable the menu File - Options on the machine