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

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

Whenever MetaAccess is started it will look at the registry or file system to see if a MetaAccess unique ID exists already. If one exists it will be used when reporting to the MetaAccess servers. If multiple devices report to MetaAccess servers using the same ID then they will overwrite each other based on which reported most recently. Alternatively if no ID is found, the MetaAccess 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.

Windows devices

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

  1. Install MetaAccess 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 MetaAccess device ID on new device(s) per instructions below

  6. (Optional) Start the source device

Option 2 - Preparing an Image: Remove device ID before cloning

  1. Install MetaAccess on source device

  2. Stop MetaAccess service(s) on source device

  3. Remove MetaAccess device ID on source device per instructions below

  4. (Optional) Delete the source device in the MetaAccess Management console

  5. Image the source device

  6. Create new device(s) from the source image

  7. Start the new device(s)


Device ID Removal Instructions

Windows

Automatically:

  1. Run the Remove Gears UID.exe

Manually:

Windows 32-bit

  1. Open a command prompt as administrator and run:

  1. sc stop opswatgearshelper

  2. sc stop waondemand

  • 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

  • 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

Option 1: Clone image before device ID is created

  1. Install MetaAccess 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)

Option 2: Remove device ID after deployment

  1. Stop the MetaAccess 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\":\"\"}"


macOS/Android/iOS

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


This article was last updated on 2017-09-27

(This article was changed to reflect the new name of MetaAccess on 2017-09-27)

AW, TT