Using a proxy between Target servers and beacon

[marcog]

Hi all,

We are trying to collect the inventory of servers where there are connection problems going from the target server to the beacon. In particular,

1. the beacon can access the target an execute ndtrack

2. ndtrack collects all the inventory

3. on FlexNet UI everything looks to be ok, we see in the log "Uploading inventory", but no info are found in "All Inventory" page

3. investigating on the targets the upload of the inventory fails due to network error (cannot find the beacon)

I found in the documentation some information about the proxy that can be configured between the beacon and the Flexnet application server, but I cannot find any info about a proxy between target and beacon. Are there any of you that have experience in this configuration using a proxy between target and beacon?

Thank you all

[mfranz]

Hi,

The mgssetup.ini has a proxy option:

; Uncomment to use (fixed) proxy server settings from Microsoft
; Internet Explorer (if they are configured at managed device
; installation time). By default (with this setting commented),
; downloads via HTTP will attempt to directly connect to distribution
; servers without going via a proxy.
;INSTALLTYPE = proxy

mgsft_rollout_response has something similar:

# The initial proxy configuration. Uncomment these to enable proxy configuration.
# Note that setting values of NONE disables this feature.
# MGSFT_HTTP_PROXY=http://webproxy.local:3128
# MGSFT_HTTPS_PROXY=https://webproxy.local:3129
# MGSFT_PROXY=socks:socks.socksproxy.local:19121,direct
# MGSFT_NO_PROXY=internal1.local,internal2.local

Haven't tested this before, not sure where these settings can be added to existing installations. Might be easier to redeploy the agent using the above options.

Best regards,

Markward