Configuring and installing Extended Device Discovery ... - Community

Understanding XDD IP address filteringIt is not recommended to install the XDD agent on notebook computers, sincethey may connect to other networks that should not be monitored, such ashotel or airport networks. To help prevent discovery of devices that aren't onyour network, the Core Server ignores IP addresses where the first and secondIP address octets are plus or minus 10 from that of the core server. Forexample, if the Core Server's IP address is 192.168.20.17, XDD on the CoreServer will ignore addresses above 203.179.0.0 and addresses below181.157.0.0. This feature can be disabled by adding the following DWORDregistry key to the core server and setting its value to 0:• HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\ManagementSuite\XDD\FilterSet the Filter value to 1 to enable filtering again.The first and second octet monitoring ranges can be adjusted by adding thefollowing DWORD registry keys to the Core Server and setting their values tothe numeric range to be monitored (the default is 10 for the first and secondoctets):• HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\ManagementSuite\XDD\FilterThreshold1• HKEY_LOCAL_MACHINE\SOFTWARE\LANDesk\ManagementSuite\XDD\FilterThreshold2FilterThreshold1 contains the range for the first octet and FilterThreshold2contains the range for the second octet.Deploying the XDD AgentThe XDD agent can be deployed to every managed device, although it is notnecessary and not recommended. Deploying the agent to several devices oneach subnet should be sufficient to discover unmanaged nodes on the subnet.9