To rename a target you will need to unlink the agent and then relink with the correct hostname.
Unlink command
Windows (Run as Administrator)
"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:
Windows: (Run as Administrator)
"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 resolve this issue, you will need to replace the value in the /etc/tenable_tag file with a valid UUIDv4 value or delete the file. The value stored in the file specified below matches that of a linked device:
Linux : /etc/tenable_tag
Windows: HKLM/Software/Tenable/TAG
macOS: /private/etc/tenable_tag
To begin,
Delete the tag file using the OS-specific instructions below
For Windows
Open regedit
Delete the following registry entry:
HKEY_LOCAL_MACHINE/Software/Tenable/TAG
For Linux
SSH into the target as root (Using sudo will work as well)
Run the following command:
rm /etc/tenable_tag
For macOS
SSH into the target as root (using sudo will work as well)
Run the following command:
rm /private/etc/tenable_tag
Relink the machine