locked
WINHTTP context of NETSHell command on remote computer RRS feed

  • Question

  • Hi, scripting guru!

    I want to get system proxy settings from all my domain computers using winhttp context of netsh command in PowerShell.

    And when I type command on my local computer netsh ? I get

    The following sub-contexts are available:
     advfirewall branchcache bridge dhcp dhcpclient dnsclient firewall http interface ipsec ipsecdosprotection lan namespace
     nap netio nps ras routing rpc trace wfp winhttp wins winsock

    But when I am on a remote computer with command netsh -r RemoteComputer I get

    [RemoteComputer] netsh>?

    The following sub-contexts are available:
    advfirewall bridge dhcp dhcpclient dnsclient interface namespace netio ras routing wins winsock

    There is no WINHTTP sub-context available.

    Is thers any ways to get system proxy settings on a bunch of remote computers?

    Thanks!


    Monday, August 11, 2014 9:12 AM

Answers

  • WinHTTP is not available remotely.  Proxy is not normally set at machine level.  It is set by IE at the user level,

    These settings can all be managed via Group Policy.


    ¯\_(ツ)_/¯

    • Marked as answer by Anton Karlan Thursday, September 4, 2014 8:13 AM
    Monday, August 11, 2014 11:21 AM

All replies

  • is WinHTTP.dll present in your remote machine?

    Regards Chen V [MCTS SharePoint 2010]


    • Edited by Chen VMVP Monday, August 11, 2014 9:22 AM
    Monday, August 11, 2014 9:22 AM
  • is WinHTTP.dll present in your remote machine?

    Look, I tested all on my local machine. First I run netsh directly with command netsh. Then I run command netsh -r MyComputerName and get [MyComputerName] netsh> prompt. And when I run ? command, I get much less sub-contexsts.

    So, problem not it any paticular system. I think that winhttp sub-context unavailable for remote machine. But I couldn't find any info about that on microsoft web site.

    Monday, August 11, 2014 10:07 AM
  • WinHTTP is not available remotely.  Proxy is not normally set at machine level.  It is set by IE at the user level,

    These settings can all be managed via Group Policy.


    ¯\_(ツ)_/¯

    • Marked as answer by Anton Karlan Thursday, September 4, 2014 8:13 AM
    Monday, August 11, 2014 11:21 AM
  • WinHTTP is not available remotely.Proxy is not normally set at machine level. It is set by IE at the user level

    I totally agree with you. And the whole thing I'm trying to do is get all computers with that kind of system proxy settings to set direct access on a system level, and then set user proxy settings using GPO.

    These settings can all be managed via Group Policy.

    I know it, and that is actualy what I'm trying to do.

    Any advice about getting system level proxy settings?

    Tuesday, August 12, 2014 5:22 AM
  • Just set them in Group Policy.  You don't need to know how they are set. GP will set them as you need.  GP overwrites any current settings.

    ¯\_(ツ)_/¯

    Tuesday, August 12, 2014 7:40 AM