Windows Proxy Settings

The Windows Proxy Settings panel lets you specify a managed Windows^* device in your zone to perform discovery and deployment tasks in place of a ZENworks® Server. This is designed primarily to enable ZENworks Servers running on Linux^* to off load discovery tasks that use Windows-specific discovery technologies such as WMI and WinAPI and deployment tasks that involve Windows managed devices.

In order to protect information, such as a discovery credential, that is passed between the ZENworks Server and the Windows Proxy, the connection is secured through SSL.

Use Windows Proxy for Windows Primary Server

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

Windows Proxy can be used for:

Linux Primary Servers that cannot perform Windows-specific discovery and deployment tasks
Windows Servers if the devices to be discovered or deployed are in a different subnet than the Primary Server

NOTE:This option is displayed only if a Windows Primary Server is selected on the Select Primary Server page.

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.

Windows Proxy

Select the managed Windows device (server or workstation) that you want to perform discovery and deployment tasks in behalf of Linux-based ZENworks Servers.

Windows Proxy Timeout

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.