Key Inspector can provide remote inspection on other
machines via the Diag (DAG) file. First, you must instruct the user to run the
ElecKey agent (EKAG20NT.EXE or EKAG6420.EXE) command. See the usage and
examples below. You may also create a shortcut for the user to run the command.
The DAG file will be created and saved in the Documents\ folder.
|
Usage: EKAG20NT <Agent ID> 0 /diag /loc=<Key Location> |
|
EKAG6420 <Agent ID> 0 /diag /loc=<Key Location> |
|
Where |
|
Agent ID: The Agent ID is provided in the Integration Result dialog and the log file after ElecKey Integrator finishes protecting a program or creating an Initiate Code. |
|
|
|
Key Location: The location of the Key (where the Agent finds the Key on the machine). |
|
0 = The Key in the All Users Profile folder |
|
1 = The Key in the drive C: |
|
2 = The Key in the drive D: |
|
3 = The Key in the User Profile folder |
|
30 = The Key in the USB License Key (dongle) |
|
Examples |
|
To run the agent to find all Keys in the All Users Profile folder and create the DAG file: |
|
EKAG20NT 0102F53BF70A5A4B 0 /diag /loc=0 |
|
To run the agent to find all Keys in the USB License Key (dongle) and create the DAG file: |
|
EKAG20NT 0102F53BF70A5A4B 0 /diag /loc=30 |
To open the DAG file received from the user, start Key
Inspector. From the Main menu, select Open Diag File. The Keys
found on the user machine will be shown in the Detected Keys area,
listed by their Program IDs. By selecting a Program ID from the list, the Key
Properties are displayed.
To get Key diagnosis, click the Details button on the
toolbar. The Diagnosis tab displays information about the system and the state
of the Key. The diagnosis descriptions are listed in the table below.
|
Key
Diagnosis |
|
|
Diag File |
Shows
the date/time of the Diag file. |
|
System
Files |
Shows
the version of the system files. |
|
Machine
Information |
Shows
the OS and CPU information. |
|
Key
Detection |
Shows
the Key detection result with the returned message including error code. |
|
Key
Events |
Shows
the state of the Key. See the Key State table. |
|
Key
State |
|
|
First
made |
The
Key was created for the first time. |
|
Remade |
The
Key was remade by the user (e.g. using the Remake utility). See “Prior Key
Detection” result for possible reason. |
|
Auto
Remade |
The
Key was automatically remade by the system (e.g. error verifying hardware
signatures). See “Prior Key Detection” result for the cause of auto remake. |
See Also