Location Best Practices

Use the following best practices when you configure Locations in Tenable Patch Management.

Network Topology

  • Plan for worst-case distribution, such as a major Windows OS update that reaches every device.

  • Keep each Location within a single physical network boundary.

  • Connect or route child offices to their parent.

  • Set subnets with mixed connectivity, or devices that do not support broadcasts (such as Azure Cloud Services), to WiFi so that they use unicast.

  • Minimize the number of Locations between child offices and the Location with internet access.

  • Follow these parent capacity guidelines:

    • Each server can efficiently handle at least 25 child offices.

    • Each workstation can efficiently handle at least 10 child offices.

    • Each client in a VPN office counts as a separate child office.

WiFi Offices

  • Do not use subnets larger than /24. Create one Location for each /24 range.

  • Enable Send Office Range only when you split a large subnet into /24 ranges.

Downloading Content from the Internet

  • Enable Allow Direct CDN Download on child offices that have direct internet access when parent-based sharing is inefficient.

  • Ensure that devices in the Central Office, or in Locations with direct CDN download enabled, can access the URLs listed under Internet URLs - Clients.

  • In non-VPN Locations, ensure that every device can reach every other device for peer-to-peer sharing.

SaaS Server and On-Premises Client Detection

This section applies to SaaS servers only.

  • Without On-Premises Client Detection, the server treats each unique public IP address as a hidden WiFi office.

  • The default behavior is usually sufficient for small and mid-sized organizations with fewer than 254 devices on the physical network.

  • To create Locations based on physical subnets, enable On-Premises Client Detection. If possible, specify a domain controller as a DNS target.

  • Add at least three devices to the Central Office, and ensure that they have internet access to the URLs listed under Internet URLs - Clients.

Auto Office Creation

  • In SaaS, configure On-Premises Client Detection before you enable Auto Location Creation. On-premises servers enable Auto Location Creation by default.

  • Auto-created Locations default to children of the Central Office with the Default type. Change the type to WiFi.

  • If you expect many auto-created Locations, choose a parent Location that can support content distribution efficiently.

  • Use auto creation to identify new subnets that you were not aware of.

  • On-premises, use Show No Office Clients to troubleshoot devices that are not assigned to an office.