Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The wechoid.exe is a window-based utility to determine a locking code for a given machine. It is essentially a window-based version of the echoid.exe command line utility, with enhanced options for selecting the locking criteria.

On this page:

Table of Contents

Usage

The wechoid.exe utility is located in the installation directory of any CSI program or in its "License Manager" subdirectory.

To use the utility, simply run it As Administrator (this is very important!) on the target machine, for conventional licensing  check the check boxes for the applicable locking criteria and obtain the locking code as shown if Figure 1. The most common locking criteria are Disk ID and Computer ID (USB key). If a particular locking criterion checkbox is disabled, it would indicate that the locking criterion is not available. For example, the Computer ID (USB key) locking criterion may be disabled when the USB key is not plugged in or when the USB key driver has not been installed properly.

Figure 1: Screenshot of wechoid.exe

For web activated licenses based on activation keys, locking criteria  should be as indicated below for all cases, wechoid.exe  can be found under CSILicensing folder.  UNCHECK everything except (1) Ethernet Address, (2) CPU Info String and (3) UUID. As shown below:


                                                                                                                                                                 Image Added

Figure 2: Screenshot of wechoid.exe (web activated)

                                                                                                                                                                                         

Important considerations

  • If using this utility for a remote server, you must use a remote desktop session and run the utility within the remote session. Otherwise (if you, for example, run the utility on a network drive) the locking code will be incorrectly obtained for your local machine and not the server.

...