For trial versions of ExpeDat, no license code is required, but you may only use the software for a limited time. If you are installing a purchased version of ExpeDat, you may be required to enter a license code when you first run each application on a new system.
To enter a license code on behalf of all users of a machine, make sure that you use Administrator privileges the first time you run or install a client on that machine. For example, the first time you run DropDat master on a Windows system, right click on it and "Run As Administrator" to authorize use by all users. Otherwise each user will need to enter the license code for themselves.
For Windows systems sharing domain authentication across multiple machines, it is best to avoid installing server software while logged into a domain account. Instead, log into a local Administrator account to perform server installation.
Administrators can download license codes from the same secure customer site where the software is downloaded. End users should obtain codes from their administrators.
For most configurations of purchased licenses, the MTPexpedat, movedat, and mtping applications will automatically register themselves on new systems without the need to enter their license code. This feature is optional and may be disabled by contacting Technical Support.
Do not rely on automatic registration when installing movedat or mtping for use in a restricted or read-only environment. Run "movedat -R" or "mtping -R" as the administrative user to ensure that all service, daemon, and scripting users can see a stored registration at run time. For example, if mtping will be run from a web CGI script, make sure to register its license code as root to avoid executation delays.
Depending on the terms of your software license, you may be provided with multiple codes for some applications. Different license codes may be configured to provide different default settings for your applications.
You only need to keep one copy of your software for each platform you use. Each executable contains all of your licenses.
For example, each servedat server may have a different license code, each tied to a specific CPU. You would copy the same executable to all of your servers, then enter a different license code for each one. See Tech Note 0007 for more information about license binding. Be sure to use the correct code as using the wrong code may cause the software to behave in unexpected ways.
The most common mistake when registering software is to enter a license code which does not match the software you are registering. Make sure that you have the latest license codes and are using the correct code for the software you are registering.
Server administrators must take special note of the host binding information listed in the license document and verify that it is correct. If you are sure this information is correct and this is a new software purchase, then verify that you have downloaded the latest software. Downloads which pre-date the license code you are using will not accept it.
For details about what various license related errors mean, see Tech Note 0027.
Saving the License
After validating your code the application will attempt to save a license token. Note that this token is specific to the CPU on which it was created and will not work if copied to other CPUs.
On unix systems, including Mac OS X, the license token will be saved in ~/.dei-mtp and copied into /etc/dei-mtp if this file is writeable. Placing the token in /etc/dei-mtp registers the application for all users of the system.
On Windows systems, the license token will be saved in the Current User class under dei\mtp\ and copied into the Local Machine class if that is writeable. A backup token will also be placed in the LocalAppData folder in the file dei\dei-mtp.dat.
Note that if you change your hardware configuration, you may be asked to re-enter your license code. For example, the first time you switch from an ethernet to a wireless network, you may need to re-enter your code.
If an application repeatedly asks for a license code, check the locations cited above, including the Windows registry if applicable. If tokens already exist in one or more of these places, delete the token for the affected application from each location and try entering your license code again. If your license includes multiple codes, make sure you are using the correct code for your location and the application you are registering. If the problem persists, delete all "dei-mtp" files and re-enter license codes for all installed MTP software.
Preinstalling the License
The license code can be explicitly set on the command line using the "R" option for servedat, movedat, and mtping. This is useful for automated deployment in scripted or embedded scenarios. MTPexpedat and DropDat will prompt for license codes when needed. DropDat embeds its license code in each droplet so that end-users should not be prompted for it.
About Your Privacy
Depending on your license and configuration, the application may send a registration message to one of DEI's servers when you first run an application or register a license code. This message contains only your license code and the public identification text that is available to any MTP application. See Tech Note 0001 for an example of what this looks like. No other data from you or your computer is sent.