Novell ZENWORKS 10 CONFIGURATION MANAGEMENT SP3 - DISCOVERY-DEPLOYMENT-RETIREMENT REFERENCE 10.3 30-03-2010 Deployment Manual page 34

Wizard Page
Select Windows Proxy page
> Use Windows Proxy for
Windows Primary Server field
When you finish the wizard, the discovery task is added to the list in the Discovery Tasks panel.
You can use the panel to monitor the status of the task. As devices are discovered, they are
listed in the Deployable Devices panel. If you have specified IP addresses to be excluded from
a discovery task, then the discovery is not run for those IP addresses and the excluded IP
addresses are not included in the Results tab.
34 ZENworks 10 Configuration Management Discovery, Deployment, and Retirement Reference
Details
Select this option if you want to use a Windows Proxy instead of the
Windows Primary Server to perform the discovery 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 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) on which you want to perform discovery tasks on behalf
of Linux Primary Servers or Windows 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.