Skip to main content
All CollectionsTroubleshooting
Resolve Endpoint Conflicts in Level
Resolve Endpoint Conflicts in Level

Resolving UUID Conflicts in Level After Device Cloning

Updated over a week ago

Level generates a random UUID for each device during installation, ensuring there are no conflicts. The system retains this UUID even after agent reinstallation, preventing duplicate entries for the same endpoint.

However, if a device is cloned after Level has been installed, a UUID collision may occur, causing two devices to compete for the same entry in Level. To resolve this issue, you need to manually modify the UUID.

Windows

  • Path: HKEY_LOCAL_MACHINE\SOFTWARE\Level

  • Key name: AgentID

This PowerShell script will automate the process on Windows.

# Get the current UUID from the registry
$CurrentUUID = Get-ItemProperty -Path "HKLM:\SOFTWARE\Level" -Name "AgentID"
# Display the current UUID
$CurrentUUID.AgentID

# Create a new UUID with PowerShell's "New-Guid"
$NewUUID = [guid]::NewGuid().ToString()
# Set the new UUID in the registry
Set-ItemProperty -Path "HKLM:\SOFTWARE\Level" -Name "AgentID" -Value $NewUUID
# Display the new UUID
$NewUUID

# Restart the Level service
Restart-Service -Name "Level"

macOS

  • Path: /Library/Application Support/Level/config.yaml

  • Key name: agent-id

Linux

  • Path: /etc/level/config.yaml

  • Key name: agent-id

After changing the UUID, restart Level to apply the changes.

Did this answer your question?