Objective
To explain how dynamic IP addressing (DHCP or rotating IP networks) affects Automox device identification, UUID generation, and license consumption.
Overview
The Automox Agent relies on hardware and network attributes to generate a unique device fingerprint (UUID). In environments with frequently rotating IP addresses or short DHCP leases, changes to network identifiers can cause the agent to regenerate the device fingerprint, resulting in duplicate device entries and additional license usage.
Impact of Dynamic IP Addresses
When a device's IP address changes frequently:
UUID Regeneration: The Automox Agent may interpret the network attribute shift as a new system fingerprint.
Duplicate Device Records: A new device entry with a new Device ID will be created in the Automox console for the same physical endpoint.
Licensing Consumption: Each newly generated device record consumes an available Automox license until inactive duplicates are removed.
Resolution & Mitigation
To prevent duplicate device creation in DHCP or rotating IP environments:
Review Identification Criteria: Refer to the Automox UUID Generation Guide to understand the full set of hardware and network parameters used for endpoint identification.
Standardize Network Interfaces: Ensure primary network adapters remain persistent on endpoints rather than frequently binding to new virtual or secondary adapters.
Configure Automatic Cleanup: Use the Device Cleanup Rules feature in the Automox console to automatically archive or delete inactive duplicate devices after a designated period.