Cloned Machines (Windows/Linux) are not reporting in SanerNow Viser

Overview:

When one or more cloned machines are created from a parent machine, they may not appear in SanerNow Viser, even though the SanerNow agent is activated.

Note: If a clone is created from a parent machine on which the SanerNow agent is already activated, the cloned machine will not report in SanerNow Viser.

Solution:

Follow these steps to ensure cloned machines are correctly reported in SanerNow Viser:

Instructions for Reporting Cloned Machines in SanerNow Viser

Windows Machines:

1. Uninstall the SanerNow Agent from the Parent Machine:
   • This is crucial to avoid conflicts during activation after cloning.
2. Install the Agent Without Activation on the Parent Machine:
   • Download the agent zip file from SanerNow Viser and extract it.
   • Open an Elevated Command Prompt (run as Administrator).
   • Navigate to the extracted folder:
      cd SanerNow_<Account Name>_Windows_x86_<version>
   • Run the installation command with the flag to disable activation:
      SanerNow_Windows_x86_<version>.exe /S /ACTIVATION_TOKEN=<"Path of spsaneractivation.conf"> /SANER_ACTIVATE_OFF=TRUE
3. Shutdown the Parent Machine:
   • Ensure the parent machine is completely powered off before creating the clone.
4. Clone the Parent Machine:
   • Create a clone of the parent machine with a unique hostname.
5. Activate the Cloned Machine:
   • After cloning, the agent will activate automatically on the cloned machine and it will start reporting to Viser.
6. Restart the Agent on the Parent Machine:
   • Run the following command to restart the agent on the parent machine:
      net stop "SecPod Saner Agent" net start "SecPod Saner Agent" 

Linux Machines:

1. Disable Activation on the Parent Machine:
   • Create a file in tmp location with name “SanerActivationDisable” to disable activation: Run the below link to disable the activation.
      touch /tmp/SanerActivationDisable
2. Install the Agent:
   • Follow the usual installation steps for the SanerNow agent on Linux. Please go through the below link for details:
     https://saner.secpod.com/Platform/CVEM/docs/Agent-Installation-Help-Guide.html?activeTab=Agent%20Installers

3. Shutdown the Parent Machine:
   • Please ensure the parent machine is powered off before cloning.
4. Clone the Parent Machine:
   • Clone the device with a unique hostname.
5. Activate the Cloned Machine:
   • The agent on the cloned machine will activate automatically and report to Viser.
6. Restart the Agent on the Parent Machine:
   • To restart the agent on the parent machine, run:
      systemctl restart spsaner

Outcome:

Following these steps will ensure that both the cloned and parent machines report correctly to SanerNow Viser without activation conflicts. Each device will have its unique identity and will show up in the Viser dashboard.