Configuring proxy settings for Applixure Agent

In most network environments, Applixure Agent is able to communicate with the Applixure's platform on the Internet without need to specify any explicit proxy settings. However, in the environments where devices (typically end-user workstations) require all applications to use network proxy in order to establish HTTPS connection (TCP port 443) to the Internet, Applixure Agent may not be able to make connection with our backend services.

By not having a successful communication between Applixure Agent and Applixure's platform, Agent is not able to register itself or send any data, or perform self-update, resulting of those devices not being shown in the Applixure UI.

While in some such environments proxy settings are distributed automatically for all users using autoconfigure technologies, Applixure Agent is operating in the system context on the device and not in the user session and as a result may not see these automatic proxy configurations visible to the user's applications.

For these scenarios, you can define explicit manual proxy settings for Applixure Agent to use. When manually defined proxy settings are in use, Applixure Agent will always try to use them to connect to the Applixure platform.


Proxy address format

For Applixure Agent proxy settings, you will need to specify IP address or DNS name of the proxy server which will handle outbound HTTPS connections, and optionally a TCP port number after colon (:) unless the proxy being used is listening on the default TCP port 443.

Example of the proxy address using IP address: (proxy at address, listening on port 8080)

Example of the proxy address using DNS name: (proxy at address, listening on default port 443)


Distributing proxy settings via Group Policy

In environments where Microsoft Active Directory (AD) is being used, the easiest and managed way to set Applixure Agent proxy settings is via Group Policy template.

You can find and download necessary Group Policy ADM and ADMX templates from our article on Group Policy template.

After you have successfully installed Applixure Agent's ADMX template into your Active Directory environment (please see more information on installing ADMX files in the Microsoft documentation at, you should see Applixure Agent's settings in the list of Administrative Templates under Computer Configuration when adding new policy object or editing existing one:

Under Applixure Agent -folder, there is a Setting called Proxy settings, which configures the proxy settings for Applixure Agent. Double-click the setting open, select Enable and fill out the proxy address in the policy's option:

After confirming policy's settings by OK, and targeting the group policy object containing this policy setting, Applixure Agent should start using the proxy server after next time the Agent's service is restarted.


Distributing proxy settings manually

If the devices are not part of the Active Directory, or you wish to distribute necessary registry settings through other delivery mechanism, you can define necessary registry settings manually.

You can find and download necessary REG file and script as attachment at the end of this article (Applixure Agent

In the registry editor file (Applixure_proxysettings.reg) change the myproxy.localnetwork.local:8888 -part to appropriate proxy address in your own network and import the REG file to each Applixure Agent device wherein you want to have proxy settings in effect.

Alternatively, you can use command-line script file (Applixure_proxysettings.cmd) change the myproxy.localnetwork.local:8888 -part to appropriate proxy address in your own network and run the script file from the elevated command-prompt (started with Run as administator -option) on each target device wherein you want to have proxy settings in effect.

Please note:

If you have both manually distributed proxy settings, and Group Policy distributed proxy settings on the same machine, Group Policy -based settings always takes precedence.


Version applicability

In order to use proxy settings for Applixure Agent, make sure that you have downloaded Applixure Agent installer package(s) on or after 16th of January, 2017. Older installers did not contain Applixure Agent code capable of detecting manual proxy settings and if the connection could not be established, self-update may not have been run either.

If necessary, you can always re-download the latest installer from you Applixure environment, and deploy it to your devices and making sure initial startup code for Agent before self-update is as up-to-date as possible.

Have more questions? Submit a request


Please sign in to leave a comment.
Powered by Zendesk