Overview
Each NetBeez agent is uniquely identified by a UUID, which is displayed on the agent’s detail page (upper-left corner) within the NetBeez dashboard.
When replacing an existing agent (e.g., swapping out hardware), it is critical to preserve the original UUID to maintain dashboard continuity, and historical data for the specific agent.
This guide explains how to update the new agent's configuration to use the same UUID and UI thumbnail as the original agent.
Prerequisites & Warnings
You must have shell access to the new agent via ssh or console.
Editing the UUID incorrectly can cause data reporting issues or break links to historical data.
Always back up the original configuration file before making changes.
Ensure your edited JSON is valid and syntactically correct.
DON'T perform this step for wired or WiFi hardware agents procured by NetBeez without contacting support@netbeez.net first.
Steps to Change the Agent UUID
1. Retrieve the Existing UUID
Log into the NetBeez dashboard and navigate to the original agent’s detail page.
In the upper-left corner (see screenshot above), note the agent's UUID. You’ll need this to update the new agent.
2. Locate the Agent Configuration File
On the new agent, open a terminal session. Depending on your installation type, locate one of the following files:
/etc/netbeez/netbeez-agent.conf/usr/local/netbeez/nbagent_info_prod.txt
3. Edit the Configuration
Open the file in your preferred text editor, for example:
sudo nano /etc/netbeez/netbeez-agent.conf
In the JSON structure either add or modify the agent_uuid field to match the UUID from the dashboard.
Example:
{"code": 100,"message":"agent found","agent_uuid":"EXISTING_UUID"}Replace "EXISTING_UUID" with the UUID copied from the UI.
Make sure:
The JSON is valid (e.g., correct commas, brackets).
The
agent_uuidis placed inside the root object or appropriate section.
4. Restart the Agent
Once the change is saved, apply it by restarting the agent service.
Depending on your environment, run one of the following:
sudo systemctl restart netbeez-agent
or
sudo systemctl restart nbagent_prod
Alternatively, you can reboot the agent.
Verification
After restart, check the NetBeez dashboard to confirm that:
The new agent appears under the original UI thumbnail
Status and data reporting resumes correctly
Notes
This method is useful when migrating agents or replacing hardware while retaining configuration and historical context.
Always ensure UUIDs are not duplicated unintentionally across active agents.