Knowledge Base

Can Metadefender Endpoint be distributed using a golden image, cloned VMs or AMIs?

Metadefender Endpoint can be distributed using a golden system image, but an additional step must be taken to avoid issues with devices reporting to Metadefender Endpoint Management servers.

Whenever Metadefender Endpoint is started it will look at the registry or file system to see if a Metadefender Endpoint Management issued unique ID exists already. If one exists it will be used when reporting to the Metadefender Endpoint Management servers. If multiple devices report to Metadefender Endpoint Management servers using the same ID then they will overwrite each other based on which reported most recently. Alternatively if no ID is found, the Metadefender Endpoint will generate a new one.

When creating a golden image, the ID must be removed on the new devices, either by removing it in the source image or removing it in the new devices. A third option is available on Linux that allows the image to be created before a device ID is assigned. 

Option 1a - Preparing an Image: Remove device ID after cloning

  1. Install Metadefender Endpoint on source device
  2. Stop and image the source device
  3. Create new device(s) from the source image
  4. Start the new device(s)
  5. Remove the Metadefender Endpoint device ID on new device(s) per instructions below
  6. (Optional) Start the source device

Option 1b - Preparing an Image: Remove device ID before cloning

  1. Install Metadefender Endpoint on source device
  2. Stop Metadefender Endpoint service(s) on source device
  3. Remove Metadefender Endpoint device ID on source device per instructions below
  4. Stop and image the source device
  5. Create new device(s) from the source image
  6. Start the new device(s)
  7. (Optional) Delete the source device in the Metadefender Endpoint Management console
  8. (Optional) Start the source device

Option 2 - After Install: Remove the duplicate ID after deployment

  1. Run the attached EXE  (Remove Gears UID.exe)

Option 3: Clone before device ID is created (Linux only)

  1. Install Metadefender Endpoint on the source device but do not start it (stop after the command "gearsd --setting...")
  2. Stop and image the source device
  3. Create new device(s) from the source image
  4. Start the new device(s)

Device ID Removal Instructions

Windows 32-bit

  1. Open a command prompt as administrator and run:
    1. sc stop opswatgearshelper
    2. sc stop waondemand
  2. Delete the ID from the registry
    1. Open regedit
    2. Browse to \HKEY_LOCAL_MACHINE\SOFTWARE\OPSWAT\Gears Client\Config
    3. Open key name "uuid" and delete the value
    4. Open key name "HWID" and delete the value

Windows 64-bit

  1. Open a command prompt as administrator and run:
    1. sc stop opswatgearshelper
    2. sc stop waondemand
  2. Delete the ID from the registry
    1. Browse to \HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\OPSWAT\Gears Client\Config
    2. Open key name "uuid" and delete the value
    3. Open key name "HWID" and delete the value

Linux

  1. Stop the Metadefender Endpoint service
    $ sudo service gearsd stop
    OR
    $ sudo systemctl stop gearsd
  2. Remove the access key and device id
    $ sudo gearsd --setting "{\"Gears-Access-Key\":\"\", \"device_id\":\"\"}"

Mac

No additional action is needed. A new ID is generated automatically.

Android

n/a

 

This article pertains to the Windows, Mac and Linux version of the Metadefender Endpoint
This article was last updated on 2015-11-09

(This article was changed to reflect the new name of Metadefender Endpoint on 2016-02-24)

AW, TT