This article describes vRx's "Read Only" agent operation mode, considerations and configuration methods.
Background:
Read Only operation mode can be used on sensitive assets, where the administrator wishes to ensure that no changes & updates can be applied via vRx dashboard. Asset reporting and risk assessment will continue to operate as usual.
Consider the pros & cons carefully since changing the asset back to normal operation mode cannot be executed automatically via vRx dashboard.
Read Only Affect:
When enabling "Read Only" mode on an asset, execution of the following actions will be blocked:
Action | Comments |
App Update | Include Auto Action execution |
OS Update | Include Auto Action execution |
Custom Script Execution | |
Patchless protection Enable | Monitor & protect |
Asset Configuration
To use "Read Only" operation mode, make sure your asset version is 4.1.1 and above.
Windows
To enable Read Only mode during Asset deployment, append the following parameter to the installation command:
MSI: OptionalFeatures=read_only_mode:true
Powershell & Topia.exe: /OptionalFeatures=read_only_mode:true
To change existing Asset behavior, Change vRx's "OptionalFeatures" in the configuration file (under "C:\Program Files\Vicarius\Topia\Topia.exe.config") to the following value:
<add key="OptionalFeatures" value="read_only_mode:true" />
Restart Topia service to apply the changes.
Linux
To enable Read Only mode during Asset deployment, append the following parameter to the installation command:
/OptionalFeatures=read_only_mode:true
To change existing Asset behavior, Change Topia "OptionalFeatures" in the configuration file (under "/usr/share/vicarius/args.txt") to the following value:
/OptionalFeatures=read_only_mode:true
Restart Topia daemon to apply the changes.
Disable Read Only Mode
To disable Read Only mode on an asset, reinstall the agent or remove the "OptionalFeatures" value