Windows Agent | GUID Conflicts & Clean Reinstall Guidance (v5.3.0+)

Overview 💥

Starting with Liongard Agent version 5.3.0+, the Windows agent uses registry-based GUID identification to assign a unique and persistent Machine ID to each endpoint.

This improves agent stability and identity tracking — but in environments with cloned machines or improper reinstalls, it can lead to:

Agent overwrites or collisions
Duplicate or incorrect agent associations
Inspectors reporting from the wrong machine

This article explains:

How the GUID logic works
When a clean reinstall is required
How to safely handle cloned machines
How to prevent agent identity conflicts

How GUID Identification Works 🤔

From version v5.3.0+, the agent generates and stores a Machine ID in the Windows registry during installation.

📍 Registry Locations

HKEY_LOCAL_MACHINE\SOFTWARE\Liongard\LiongardAgent\MachineID
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Liongard\LiongardAgent\MachineID

🔍 Key Behavior

Machine ID is generated at install time
Persisted across:
- Reboots
- Service restarts
Used as the primary identity of the agent in Liongard

⚠️ Important Limitation

Registry-based GUID logic applies ONLY to fresh installs

❌ Upgrades → Do NOT generate a new Machine ID
❌ Repairs → Do NOT fix incorrect Machine IDs
✅ Fresh installs → Generate a new, correct Machine ID

When a Clean Reinstall is Required 🧐

You must perform a full uninstall + reinstall if any of the following occur:

Agent installation failure
Agent linked to the wrong environment
Incorrect agent name or identity
Duplicate agents appearing in Liongard
Suspected Machine ID conflict
Environment switching during setup

❌ What NOT to Do

Do NOT use Repair or Upgrade in these scenarios

Why?

Existing Machine ID remains unchanged
Conflict persists
Agent may continue overwriting another device

Clean Reinstall Steps 🧑‍🏫

Follow these steps to safely reset the agent identity:

1️⃣ — Uninstall Existing Agent

Use:

Add/Remove Programs & Feature on windows, or
Your RMM tool, or
Follow our guide

2️⃣ — Verify Complete Removal

Ensure:

Liongard Agent service is stopped
Installation directory is removed

3️⃣ — Install Latest Agent (v5.3.0+)

On Liongard, navigate to Admin → Agents → Download Agent Installer → Windows
Deploy using your preferred method
Ensure correct environment is selected

4️⃣ — Verify in Platform

In Liongard:

Confirm agent appears:
- Under correct environment
- As a unique device
- Without overwriting others

Post-Install: Remap Inspector Triggers (Optional) 🔄

If the old agent had inspectors assigned:

✔ Recommended Action

Reassign inspector triggers to the new agent

🧠 Why This Matters

Prevents inspection gaps
Ensures continuity of monitoring

🗑️ Cleanup

After verification:

Delete old agent record
Keep environment clean and accurate

Cloned Machine Warning 🚨 (Critical)

Cloning a machine with the Liongard agent already installed can result in multiple devices sharing the same Machine ID

This causes:

Agent overwrites
Data inconsistency
Inspectors reporting from the wrong device

How to Prevent GUID Conflicts on Cloned Machines 🤩

Before deploying the agent on cloned systems, follow ONE of the methods below:

Option A — Exclude Registry Keys (Best Practice)

During imaging or cloning, exclude the following registry paths:

HKEY_LOCAL_MACHINE\SOFTWARE\Liongard\LiongardAgent\MachineID
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Liongard\LiongardAgent\MachineID

✔ Ensures new Machine ID is generated on install

Option B — Delete Registry Keys After Cloning

On the cloned machine:

Open Registry Editor (regedit)
Navigate to the paths above
Delete both MachineID entries
Install the agent

What Happens If You Skip This?

Both machines will share the same Machine ID

Resulting in:

Agent identity collision
Devices overwriting each other
Incorrect inspection data
Manual cleanup required

Visual Flow 🧭

Clone Machine (Agent Installed)
        │
        ├─❌ No Action Taken
        │     ↓
        │  Same MachineID
        │     ↓
        │  Agent Collision / Overwrite
        │
        └─✅ Remove/Exclude Registry Key
              ↓
         New Agent Install
              ↓
         Unique MachineID
              ↓
         Stable Agent Identity ✅

When to Contact Support 🦁

Reach out to Liongard Support if:

Agents continue overwriting after reinstall
Duplicate Machine IDs persist
Multiple environments are affected
Registry cleanup did not resolve the issue

Provide:

Agent name(s)
Environment details
Confirmation of reinstall steps
Registry key status
Agent Version
Agent Logs

Key Takeaway 💡

Agent identity is now tied to a registry-based Machine ID — and must be handled carefully in cloned environments.

✔ Always use fresh installs when identity issues occur
✔ Never rely on repair/upgrade for GUID-related problems
✔ Clean registry handling is critical in imaging workflows

Summary 🚀

Liongard Agent v5.3.0+ uses registry-based Machine IDs
Only fresh installs generate new IDs
Cloned machines can cause GUID conflicts
Proper registry handling prevents agent overwrites
Clean reinstall is the only reliable fix for identity issues