ALERT: Datto Drive Cloud service will no longer be available as of July 1, 2019. For more information, see our end-of-life article. If you'd like to migrate your data to Datto Workplace, see our migration guide.
To learn how to download your Datto Drive Cloud data, please visit this article.

Datto RMM: How can I change the WinHTTP proxy settings?

Follow

Question

How can I change the WinHTTP proxy settings for my Datto RMM instance?

Environment

  • Datto RMM

Answer

Overview

If you configure Datto RMM to work with a proxy server, you may experience unpredictable behavior if you do not also configure the WinHTTP proxy settings on the managed endpoint.

Datto RMM interacts with the Windows Update Agent (WUA) API and relies on the WinHTTP proxy settings managed by Windows. These proxy settings are not enabled by default, as Windows Updates normally run within a user session, where the proxy settings are inherited from Internet Explorer. See Microsoft's How the Windows Update client determines which proxy server to use to connect to the Windows Update Web site (external link) article for more information.

When the Datto RMM Agent calls the Windows Updates utility, it does not have access to the user-specific proxy settings from Internet Explorer. As a result, the Windows Update program will not be able to access the Internet to update its list of missing or installed patches.

When this happens, you may notice that the list of missing and installed patches for the endpoint, as compiled by the Datto RMM Agent, do not match the local Windows Updates list. In some cases, there may be no patches listed by the agent at all.

To learn how to resolve this issue, proceed to the Configuring your proxy section of this article.

Configuring your proxy

This section explains how to change WinHTTP proxy settings manually by using the Windows Command Prompt. It also provides a walkthrough for deploying these actions through a ComStore component. Select a topic to continue:

Adding WinHTTP proxy settings via the Command Prompt

To manually set the WinHTTP proxy name and port, follow the steps that correspond with the operating system installed on your endpoint.

Select an operating system to continue:

Windows XP / 2003

1. Open an Administrator-level Windows Command Prompt session.

2. From the prompt, issue the following command. Substitute "proxyservername" with the name of the proxy, and "portnumber" with the communication port that your endpoint should use.

proxycfg -p {proxyservername}:{portnumber}

Windows Vista and Up

1. Open an Administrator-level Windows Command Prompt session.

2. From the prompt, issue the following command. Substitute "proxyservername" with the name of the proxy, and "portnumber" with the communication port that your endpoint should use.

netsh winhttp set proxy {proxyservername}:{portnumber}

Removing WinHTTP proxy settings via the Command Prompt

To manually remove a configured WinHTTP proxy, follow the steps that correspond with the operating system installed on your endpoint.

Select an operating system to continue:

Windows XP / 2003

1. Open an Administrator-level Windows Command Prompt session.

2. From the prompt, issue the following command to remove the proxy:

proxycfg -d

Windows Vista and Up

1. Open an Administrator-level Windows Command Prompt session.

2. From the prompt, issue the following command to remove the proxy:

netsh winhttp reset proxy

Using ComStore components to add or remove WinHTTP proxy settings

You can automate the process of adding and removing proxy settings by using components from the ComStore. To do so:

1. Log into the Web Portal and click the ComStore tab.

2. Search for WinHTTP proxy. You should see the following results:

  • WinHTTP Proxy (Add) - v2 [WIN]: This component will add a system-level proxy setting on the target device.
  • WinHTTP Proxy (Remove) - v2: This component will remove a system-level proxy setting on the target device.

3. Select the component matching the task you'd like to perform. Then, click Add to my Component Library to add it to the list of your components.

4. Deploy the component. Specify the {proxyservername} and {portnumber} as input variables at run time. The components will intelligently decide whether to use the PROXYCFG or the NETSH command to achieve the desired results in your environment.

For more information about deploying components, see our Job Scheduler article. To learn about component variables, see our Input Variables article.


Was this article helpful?

0 out of 0 found this helpful

You must sign in before voting on this article.

Want to talk about it? Have a feature request?

Head on over to our Community Forum or get live help.