Windows Proxy Settings

Select this option if you want to use a Windows Proxy instead of the Windows Primary Server to perform discovery and deployment tasks.

Discovery through WMI, WinAPI and SNMP requires certain ports to be reachable on the target devices, so the Primary Server can send Remote Registry, WMI, or SNMP requests to the target devices. Ports are opened by adding them as an exception in the Windows Firewall configuration settings. By default, the scope of the exception applies only to the local subnet. If the target device is in a different subnet than the Primary Server from which the discovery is run, you need to add IP address of the Primary Server as an exception. However, if you use a Windows Proxy in the same subnet as a target device, you do not need to change the scope of the Windows Firewall exception.

For deployment, you need to add File and Printer Sharing as an exception in the Windows Firewall configuration settings. By default, the scope of the exception applies only to a local subnet. If the target device is in a different subnet than the Primary Server from which the deployment is run, you also need to add the IP address of the Primary Server as an exception. However, if you use a Windows Proxy in the same subnet as a target device, you do not need to change the scope of the Windows Firewall exception.

Select the managed Windows device (server or workstation) on which you want to perform discovery and deployment tasks on behalf of Linux Primary Servers or Windows Servers.

Specify the number of seconds you want the ZENworks Server to wait for a response from the Windows Proxy. Any responses received after the specified timeout period are discarded.