|Show/Hide Hidden Text|
By default the Agent attempts to connect to the Dashboard over HTTPS, although depending on the device and network configuration it may be necessary to force the Agent to use HTTP.
This can be achieved either pre-registration by editing the pak.xml file or post-registration in agentconfig.xml.
The following examples use the default vi text editor. Information on vi (visual editor) is available in the SS64 quick reference guide
Before registering the Agent on the Dashboard the option to force HTTP can be configured in pak.xml.
Navigate to the Agent install directory /usr/local/rmmagent then open pak.xml in an editor.
After the list of server URLs enter <secure>0</secure> to disable HTTP during the registration process and save changes once complete.
Save the changes to pak.xml - in vi press Esc to access the command interface then :wq to write the changes and quit. To view the file to ensure the changes were applied enter:
Note: amending the pak.xml file only affects the Agent pre-registration, once the Agent is reported on the Dashboard and any changes to this file are not applied.
The HTTPS communication settings can be changed after the Agent is registered on the Dashboard and this can be achieved by editing the agentconfig.xml file found in the Agent installation directory.
Navigate to the rmmagent folder /usr/local/rmmagent and open agentconfig.xml in an editor.
To disable HTTPS, change the secure setting <secure>1</secure> from enabled (1) to disabled (0) and save changes once complete.
Save the changes to agentconfig.xml - in vi press Esc to access the command interface then :wq to write the changes and quit. To view the file to ensure the changes were applied enter: