Preferences

    The Preferences tab contains the settings that govern ManageEngine SecureAI itself, rather than the agents and gateways it protects. It covers the alerts SecureAI raises about its own licensing and availability, how the product behaves on the server that hosts it, and the branding its interface carries.

    When those alerts stop being useful or start arriving too often, when the host server is rebuilt, and when your organization applies its own branding across the products it runs, check the preferences. You can switch alerts on and off here. You can change who receives them in email server settings.

    How it works

    SecureAI sends License Expiry Notification 10 days before the license expires, and Product Startup and Downtime Notification every time the product starts and every time it shuts down. SecureAI raises both on its own, so neither depends on a notification template. Both go out as email to the addresses saved in Administrator's Email Address field in email server settings, using the mail connection set up there, so neither arrives until that configuration is complete.

    Automatic startup applies where SecureAI has been installed as a Windows service. The operating system then starts the product along with the server, and the client launch setting opens the SecureAI client once startup has finished. Rebranding stores an image and a URL. SecureAI shows the image in place of its own logo, and clicking the logo opens the URL. There is one set of preferences for the whole of SecureAI, so nothing here differs from one technician to another.

    Prerequisites

    Complete the following before you configure the preferences:

    • Log in with a role that includes the Server Settings permission under Administration. Of the roles supplied with SecureAI, Super Admin and Governance Manager include it.
    • Configure email server settings and enter at least one address in the Administrator's Email Address field. Preferences has no recipient field of its own, and both License Expiry Notification and Product Startup and Downtime Notification go to the addresses in that field, so leaving it empty means the alerts have nowhere to go.
    • Send a test email from email server settings and confirm that it arrives. A product alert is raised at the point the product stops or the license lapses, so the delivery path should be proven in advance rather than at that moment.
    • Install SecureAI as a Windows service on the host server if you intend to have it start automatically.
    • Produce the logo at the size SecureAI accepts, which is 150 x 30 pixels, and save it as a GIF, JPEG, or PNG file of 2MB or less.
    • Obtain the full URL the logo should point to, including http:// or https://, if the logo is to open a destination when it is clicked.
    Note:
    • The alerts offered here are for license expiration, product startup, and downtime. No other event in the product's own operation can be turned into an alert from preferences.
    • Recipients are not chosen here. Both alerts reach the addresses held in email server settings, and a separate recipient list for either one is not available.
    • The license expiration alert is sent 10 days before the expiration date. SecureAI offers no control over that lead time and no way to repeat the alert on a schedule of your own.
    • Automatic startup is offered for a Windows service installation. A host that runs SecureAI another way is outside what this setting covers.
    • Clearing Start the product automatically at Windows Startup does not clear Launch the SecureAI client upon successful startup beneath it. The second setting stays selected and can still be changed, so the saved values can show a client launch waiting on a startup that will not happen.
    • Rebranding takes one logo, in GIF, JPEG, or PNG at 150 x 30 pixels and no more than 2MB. Artwork of another size or format has to be converted before it can be used.
    • A bare domain name is not accepted as the logo URL. The full URL is required.
    • Preferences does not check email server settings before saving. An alert can be selected and saved while the email configuration is incomplete, and no warning is given that SecureAI has no way to send it.

    Configuration instructions

    1. Navigate to Settings > General Settings > Server Settings.
    2. Click the Preferences tab.
    3. Select the alerts SecureAI should raise about itself. Both are selected when the product is installed, and both are sent to the addresses held in Administrator's Email Address in email server settings.
      • License Expiry Notification: An email 10 days before the SecureAI license expires.
      • Product Startup and Downtime Notification: An email each time the product starts or shuts down.
    4. Enable Start the product automatically at Windows Startup setting for SecureAI to start with the host server. This applies where the product is installed as a Windows service.
    5. Enable the Launch the SecureAI client upon successful startup setting which sits under Start the product automatically at Windows Startup, for the client to open once SecureAI has started.
    6. Click Browse beside the Change Logo field under the Rebranding section and select the image that replaces the product logo. The image must be a GIF, JPEG, or PNG file, 150 x 30 pixels, and 2MB or less.
    7. Enter the URL the logo should point to in the Custom Logo URL field, including http:// or https://.
    8. Click Save Changes.

    Tips

    • Send the product alerts to a distribution list that a team reads rather than to one administrator's mailbox. These messages arrive when the product is down or the license has lapsed, so a single recipient who is away leaves them unanswered until they return.
    • Treat the license expiration alert as a last check rather than a first warning. Ten days is short notice for a purchase order, so track the renewal date alongside your other contract dates as well.
    • Use the startup and downtime alerts to identify restarts that were not planned. Tell the recipients when the server's maintenance window falls, so that the expected messages are recognized as routine and the unplanned ones stand out.
    • Keep automatic startup selected on a production server. Without it, SecureAI has to be started manually after every reboot, and it is not doing its work until someone does. A shutdown alert with no startup alert following it is the sign to look for.
    • Point the logo URL at an internal service desk or governance site rather than the corporate home page. The people who click it are already logged in and are usually looking for help with the product.
    • Check email server settings first when an alert stops arriving. Preferences decides whether an alert is raised, and everything about delivering it is configured elsewhere.