Menu:


AngeliaMail Configuration Main Form - click to see it full size.


AngeliaMailTM - On-Line Help - Remote Administration



In its default form, the AngeliaMail Configuration Utility must be run on the desktop of a licensed AngeliaMail system that is participating in the common configuration in order to access the shared configuration and update it.  However, the Configuration Utility can be configured to run from the desktop of a non-licensed system (ie – a system that does not have an AngeliaMail production license installed) and update the shared configuration.

To set up a non-licensed system to manage AngeliaMail configuration information follow these steps:

  • Copy AngeliaConfig.Exe into a folder on the non-licensed system or be sure it is in a network folder that is visible via high-speed connection from the non-licensed system.
  • Create a shortcut to AngeliaConfig.Exe on the system on whose desktop it will be run
  • Right click on the Configuration Utility shortcut just created and select “Properties”.
  • On the "Shortcut" tab – in the "Target" item – append the full path name of the shared AngeliaMail configuration file to the AngeliaConfig.Exe path. For example, if your configuration is located on a server name “MyServer” in a share named “AngeliaMail”, and assuming that you put your AngeliaMail files in an AngeliaMail folder under that share (see Sharing Configurations), and assuming that you have a local copy of AngeliaConfig.Exe in C:\Tools – "Target" should contain "C:\Tools\AngeliaConfig.Exe \\MyServer\AngeliaMail\AngeliaMail\AngeliaMail.SSA".

Note – when updating a configuration via Remote Administration, the "Select A Different AngeliaMail Configuration File" (in "Config Options" and "License Status"), "Relocate Configuration File" (in "Config Options"), and the "View AngeliaMail Log" (in "Help") will be disabled.  In addition, if a Password is applied to the configuration via Remote Administration, the License Key that will be associated with that password for possible password clearing purposes will be the License Key associated with the configuration that was originally "Relocated" to create the shared configuration.