VM Clone and Carbon Black Cloud Workload

When you manually clone your virtual machine on which the Carbon Black Cloud Workload is enabled, you might see some inconsistent behavior. The parent and the clone VM might appear under both Enabled and Not Enabled tabs. You might observe a similar behavior in the Carbon Black Cloud console. The problem occurs as the Carbon Black sensors use the same ID to identify both the VMs to the back end. To resolve the problem, you must perform manual steps and reregister the cloned VM with the Carbon Black Cloud.

Windows VMs

Correct problem on the existing clones as follows:

1. Log in to the clone VM. For example,WIN10_X64_VDI.
2. Run the repcli reregister command as follows.

   repcli reregister now
   

   The clone VM is reregistered and the problem is remediated.

You must correct the problem on the golden image, so that further clones created from the golden image are reregistered correctly. Correct the problem as follows:

1. Log in to the parent VM where the Carbon Black sensors are installed. For example,WIN10_X64_GOLDEN.
2. Access the RepCLI Utility.
3. Complete the background scan and verify that the policy is updated with the RepCLI Status command.

   C:\Program Files\Confer> repcli status
   

4. Schedule the reregistration for the clone VM. Use the following repcli reregister command. Change MASTER with the computer name of the parent VM.

   if /i %computername% == MASTER (echo Skipping reregistration) ELSE ("C:\Program Files\Confer\RepCLI.exe" reregister now) > C:\Temp\CB_reregister.txt

   For example:

   if /i %computername% == WIN10_X64_GOLDEN (echo Skipping reregistration) ELSE ("C:\Program Files\Confer\RepCLI.exe" reregister now) 

5. Create clones from the golden image now.

   When you log in to the clone VM next time, the scheduled command runs and registers the cloned VM.

6. Log in to the clone VM. For example, WIN10_X64_VDI. The clone VM is registered as separate device and is assigned a new device ID.

   For more details, refer Knowledge Base (KB). For more details, refer Installing Sensors in a VDI Environment of the Carbon Black Cloud Sensor Installation Guide.

Linux VMs

Perform the steps for registering a clone Linux VM with the Carbon Black Cloud back end:

1. Log in to the clone VM. For example, LIN_CENTOS_VDI.
2. Stop the cbagentd using the following command. Run the command with the root privilege based on the Linux distribution.
   • For CentOS/RHEL/Oracle 6, use the following command.

     $ sudo service cbagentd stop

   • For all other distributions, use the following command.

     $ sudo systemctl stop cbagentd

3. Register the clone VM using the following command.

   $ sudo /opt/carbonblack/psc/bin/cbagentd -R

   The clone VM is registered as separate device and is assigned a new device ID and registration ID.

4. Start the cbagentd using the following command. Run the command with the root privilege based on the Linux distribution.
   • For CentOS/RHEL/Oracle 6, use the following command.

     $ sudo service cbagentd start

   • For all other distributions, use the following command.

     $ sudo systemctl start cbagentd