Renaming an internal target

Made a mistake, don't like the name anymore? No worries, this articles explains how you can rename an internal target

Naomi Purvis avatar
Written by Naomi Purvis
Updated over a week ago

To rename a target you will need to unlink the agent and then relink with the correct hostname.

Unlink command

"C:\Program Files\Tenable\Nessus Agent\nessuscli.exe" agent unlink

Linux

sudo /opt/nessus_agent/sbin/nessuscli agent unlink

MacOS

sudo /Library/NessusAgent/run/sbin/nessuscli agent unlink




Relink command:

"C:\Program Files\Tenable\Nessus Agent\nessuscli" agent link --host="cloud.tenable.com" --port="443" --key=[KEY] --name=[Prefix_DeviceName]

Linux

/opt/nessus_agent/sbin/nessuscli agent link --host="cloud.tenable.com" --port="443" --key=[KEY] --name=[Prefix_DeviceName]

MacOS

/Library/NessusAgent/run/sbin/nessuscli agent link --host="cloud.tenable.com" --port="443" --key=[KEY] --name=[Prefix_DeviceName]


Once you've done that, it should take a couple of minutes for the internal system to show up.


Error message

It's not very common, but sometimes these things happen.

[error] [agent] Link fail: [409] Agent with uuid agentUuid=<> attempt to link, but another agent in container containerUuid=<> with different token already exists.

This message 👇 can pop up if the agent hasn't unlinked properly. To remedy the situation, please click through and follow the steps in this article:

If that doesn't work, you will have to:


Did this answer your question?