Proxy Server Configurations
Many organizations use a proxy server to manage and monitor internet traffic. A proxy server acts as an intermediary between a client and the external network. Popular proxy servers include ProxySG and Squid, among others.
There are two typical configurations: caching and transparent. The most common is a caching proxy. A caching proxy requires that the client is configured to use the proxy. This can be done through DHCP or manual configuration. As an example, the web proxy for a client is set to 10.0.0.2 with port 3128. The network is then configured to only allow traffic outbound from 10.0.0.2 and not directly from the client.
In a transparent proxy, the client does not need to know about the proxy server. It most often runs in line with the router. No client-side configuration is needed.
Proxy Evaluation Order
If the proxy is set, an attempt is made to use it. If it is unreachable, the next proxy is checked.
The order of proxy evaluation by Automox is as follows:
4. Windows Only: IE Proxy (Dynamic via PAC file)
5. Windows Only: IE Proxy (Static)
NOTE: The agent runs as a local system. The proxy settings must be configured at the system level, not the user level.
Follow the examples for configuring the environment variables.
Automox Client Configuration - Linux
The Automox client needs one of the previously mentioned proxy settings configured. For example, if you are using
HTTPS_PROXY, these can be set in your current session using
export HTTP_PROXY=http://10.0.0.1:3128 and
export HTTPS_PROXY=http://10.0.0.1:3128 replacing 10.0.0.1:3128 with your proxy server address and port. However, since the Automox agent will run automatically at startup, the best practice is to ensure that this is set globally in the file
Step 1. Begin by editing the file
Step 2. Append
export HTTP_PROXY=http://yourProxyServer:yourProxyPort and
export HTTPS_PROXY=http://yourProxyServer:yourProxyPort .
Step 3. To verify the setting, you can log out of your session, log in again, and run
echo $HTTP_PROXY or
echo $HTTPS_PROXY .
Automox Client Configuration – Windows
The Automox client requires that you set up PAC files via Windows Group Policy, and that a system environment variable is set. This is not a profile environment variable but rather a system environment variable. For Windows clients, Automox supports the use of PAC files for proxy deployments and will attempt to use your IE proxy settings.
Instructions for setting up PAC files via Group Policy.
Step 1. When using the "Automatically detect settings" option, ensure that the
wpad hostname resolves correctly in DNS to your PAC file server.
Step 2. When using a static configuration script, ensure that the URL is accessible from your devices.
Step 3. Ensure that the setting is applied at the machine level, and not the user level so that the LocalSystem user has access to the configuration... this is the "Make proxy settings per-machine (rather than per user)" GPO option.
Step 4. Troubleshoot by using the command
bitsadmin /util /getieproxy localsystem
Instruction for setting environment variable On Windows device
Step 1. In the Control Panel, click System and Security.
Step 2. Click System.
Step 3. Click Advanced System Settings.
Step 4. Click Environment Variables.
Step 5. Under System variables, click New.
Step 6. As an example, you can configure variables as follows:
- For Variable name enter:
- For Variable value enter: the IP/Name of your proxy server and port.
- Click OK.
Step 7. Click OK.
Step 8. In the example, you would complete the same steps for HTTPS_PROXY. Be sure to leave the protocol as http. leaving out the "s."
Your Automox Agent is now configured to use your proxy server.
You can automate setting the proxy by using a worklet. Refer to the Automox Community for examples of creating and applying worklets.