Cloned Machines (Windows/Linux) Not Reporting in Saner CVEM Viser

Product Version: Saner CVEM 6.5.0.0

Overview

When cloned virtual machines are created from a parent system with an already activated Saner CVEM Agent, the cloned instances may fail to appear in the Saner CVEM Viser dashboard. This occurs due to activation conflicts arising from identical system identifiers.

Important: If a machine is cloned after the Saner Agent has already been activated on the parent machine, the clone will not report to Saner CVEM Viser.

Resolution

To ensure that both the parent and cloned machines are uniquely identified and properly report to Saner CVEM Viser, follow the platform-specific steps outlined below:

Instructions for Windows Machines

Step 1: Uninstall Agent on the Parent Machine

Uninstall the Saner Agent to avoid activation conflicts after cloning.

Step 2: Reinstall the Agent Without Activating

1. Extract the downloaded .zip file. The folder will be named:

Saner_<AccountName>_Windows_x86_<Version>

2. Open Command Prompt as Administrator and navigate to the extracted folder.

cd Saner_<AccountName>_Windows_x86_<Version>

3. Install the agent without activation using the following command:

Saner_Windows_x86_<version>.exe /S /ACTIVATION_TOKEN=<"Path of spsaneractivation.conf">

Step 3: Shut Down the Parent Machine

Ensure the machine is completely powered off before proceeding.

Step 4: Clone the Machine

Create the cloned VM with a unique hostname.

Step 5: Power On and Activate the Clone

Once booted, the Saner Agent on the clone will activate automatically and report to the Saner CVEM Viser dashboard.

Step 6: Restart Agent on Parent Machine

After cloning, restart the agent on the parent machine.

net stop "SecPod Saner Agent"
net start "SecPod Saner Agent

Instructions for Linux Machines

Step 1: Disable Activation on the Parent Machine

Create a temporary file to disable auto-activation:

touch /tmp/SanerActivationDisable

Step 2: Install the Agent

Proceed with the usual agent installation steps. Refer to the installation guide below:
Saner CVEM Agent Installation Guide (Linux)

Step 3: Shut Down the Parent Machine

Ensure the parent machine is completely powered off.

Step 4: Clone the Machine

Clone the Linux system and assign a unique hostname to the new instance.

Step 5: Power On and Activate the Clone

The cloned system will auto-activate and appear in Saner CVEM Viser.

Step 6: Restart Agent on Parent Machine

Once cloning is complete, restart the agent on the parent system.

sudo systemctl restart spsaner

Outcome

By following the above steps, each machine—whether parent or clone—will have a unique identity and will report correctly to the Saner CVEM Viser dashboard. This prevents duplication or activation conflicts and ensures accurate tracking and reporting of all assets.