Knowledge Base

How to remove the CodeTwo Exchange Rules license from a user who does not need it anymore

Problem:

You want to take back the CodeTwo Exchange Rules license from a user who no longer needs it.

Solution:

Tip

Note that CodeTwo Exchange Rules licenses are assigned to every email address that benefits from the program. Consequently, if a user uses two email addresses, such a user will consume two licenses.

Removing an individual email address from the list of licensed addresses requires clearing the entire list. To do it, follow the instructions for your version of the program:

Resetting licenses in the newer versions of CodeTwo Exchange Rules

  1. If you want to make sure that a given email address is licensed, click the Server Monitor button located on the Administrator Panel’s toolbar. Learn more
  2. To clear the list of licensed email addresses, restart the CodeTwo Exchange Rules Service on each server. You can use the Exchange Rules restart services buttons buttons located in the Server Monitor window (Fig. 1.), or the Windows Services menu (services.msc).

Exchange Rules restart services
Fig. 1. Restarting the Exchange Rules Service from the Server Monitor window.

Resetting licenses in the older versions of CodeTwo Exchange Rules

  1. If you want to make sure that a given email address is licensed, open the file named either Licensing.log or LicensingInfo.log. The file is located in the following path (Windows Server 2008 and newer):

    %Windir%\ServiceProfiles\NetworkService\AppData\Roaming\CodeTwo\<name of the software>\

    If you cannot find the above path, check the location of your NetworkService user profile in Windows Registry. To do so, run regedit.exe and check the value of ProfileImagePath key in the following path:

    HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-5-20\
  1. To clear the list of licensed addresses, restart the Exchange server machine on which the CodeTwo Exchange Rules is installed. Do not attempt to edit or remove the Licensing.log or LicensingInfo.log files – this will not be effective.

See also: