Application proxy setting for KACE Agent.
In my environment(s) we have developers who set HTTP_PROXY & HTTPS_PROXY as system environment variables so that they can run their applications. With these set, the KACE agent will not check in correctly.
I propose that we have application specific proxy settings available for the KACE agent application, whereby should no proxy settings be configured on the application, all other possible locations for setting a proxy (eg. IE, netsh, Env) are ignored and a direct connection is attempted unless otherwise specified.
We issued the same problem. You can use the "no_proxy" variables to exculde urls :