To be able to use the setup wizard, the Network connection must have been carried out correctly.
Introduction
The UMA setup wizard is intended to assist in the setup process and ensure that each step necessary to set up the UMA is completed successfully.
Of course, this can also be simply closed and the UMA configured manually, but it is recommended to set up the UMA via the wizard.
Login after network connection
After the Network Connection is set up, the Admin Interface of the UMA can be accessed (IP address with port 11115)
Fundamental settings
Depending on whether the UMA is being installed for the first time or whether a backup is to be restored after a new installation, various steps are required:
New installation with existing backup
As typeconfiguration file is selected. This must have been exported before on the old UMA under Adminsitration Tab Backup or from UMA NG v3 under Maintenance Tab Backup in the section Configuration Import/Export. With the button Complete among other things the data from step 1 of the setup wizard are taken over:
Network configuration
UMA IP address
Gateway, DNS
Host name, domain
Admin password and email address
Remote Smarthost settings
After the reboot, step two of the setup wizard is called directly.
Initial installation
As type is selected license. The license mandatory for operation can be downloaded reseller portal
Setup Wizard
Step
Description
Step 1
Network Connection Data:
UMA IP address:Permanent IP address of the UMA
The address set via CLI is temporary and will be replaced by the default IP or by the address specified here at the next boot.
default gateway, hostname, domain, DNS, NTP server
admin data:
password
Email address: Important system emails (status or error messages) are sent to this address.
Remote Smarthost Settings
Access data to a mail server for sending system mails. Continue with button Next
Sending test mail. Confirm sending with OK. If no mail arrives, please check the access data for the smarthost and the network connection
Step 2
Initialize storage hard drive
The hard drives for the archive must be initialized. This is done automatically with the archive hard drives recognized by the UMA.
If a hardware RAID controller has been installed in the UMA, only one drive is displayed in this view.
During this process, all data on the specified hard drives will be irretrievably deleted.
Continue with button Next Restart after the initialization of the storage Initialize storage
Step 3
Set up accounts: Depending on the type of authentication (Repository Type:)
Windows Active Directory
Other LDAP Server
Local Users
Azure AD
Windows Active Directory Windows domain: The corresponding domain in which the Active Directory resides.
workgroup: Must match the NetBIOS name of the domain IP or hostname of the DC: username: / password: A user with permission to perform an LDAP search.
Account selection
Account selection
When using an authentication service such as Active Directory, care should be taken to determine which email accounts really need to be archived.
In the section "Selection of individual accounts" there is the possibility to select the accounts to be archived exactly and thus to work much more "license-friendly". This is done by activating the field "Activate manual selection".
LDAP
For the use of another LDAP server, the following is entered in the fields:
base: The domain in the form dc=localdomain dc=local
IP or hostname of DC:
username: User name for the LDAP server in the form cn=admin
password: Password to the previously specified username
User Container: The organizational unit in the form ou=users
LDAP User Filter: In the form (objectClass=inetOrgPerson)
User Attribute(s) e.g. uid
Mail Attribute(s)
LDAP communication security To enable this, you must first create a CA Import
Local users If no authentication server is operated, the users can also be stored locally in a list.
For this purpose, there is the possibility to import a list in CSV format via the Import button.
The content of the *.csv file must have the following format:
Directory ID (tenant) from the app registry in Azure AD.
Client-ID:
•••••••
Application ID (Client) from the app registry in Azure AD.
Client-Secret:
•••••
Value of the client secret key from the Certificates & Secrets section of Azure AD.
Azure Cloud:
Azure Cloud Global
Azure Cloud USA
Azure Cloud Deutschland
Azure Cloud China
Selection of the Azure Cloud that hosts the AD.
Continue
Verify the credentials and go to the next step.
Azure AD credentials in step 3 of the setup wizard.
Step 4
Archive rules define the duration of archiving. The global rule applies if no other rule takes effect. The default is 6 years Continue with button Next
E-mails that have a header but no body (i.e. "empty e-mails") are retrieved by the UMA and stored in the user mailbox. However, these are not indexed and therefore do not appear in the DMS!
Step 5
Remote email accounts receive all journal emails from a mail server. This usually includes several individual user email accounts. The remote email accounts must be created in the Mail Server as journal accounts, so that all associated mails (outgoing and incoming mails of the mail server) can be received here.
Archiving only takes place if the following settings have been made under System Settings / email Accounts users with a corresponding email address can be created.
account details:
Caption
Value
Description
Name:
Journal Account
Freely selectable name
Servername:
imap.mailsever.anyideas.de
Mail server that hosts the journal address.
Protocol:
IMAP
used protocol
Username:
tttpointcloud
User name for the Journal-emai account
Password:
•••••
Password for the journal email account
Leave emails on the server
Should only be activated temporarily for testing purposes , otherwise the mailbox will sooner or later reach its capacity limit.
SSL:
Requires an SSL connection on activation
Max. email size
disabled
A size can be defined up to which the email is archived
email Header Evaluation:
Enable MS Journal-Envelope autodetection default
The recognition of the header entries "MS journal envelope" enables the UMA BCC recipient to recognize in the Exchange-own header and assign it to a user account.
BCC recipients are not in the original mail header
Disable MS Journal-Envelope autodetection
Uses the original header of the email to assign it to a user account
X-Envelope-To
Uses only the X-Envelope-To entry from the original header of the email to assign it to a user account
X-Original-To
Uses only the X-Original-To entry from the original header of the email to assign it to a user account
Delivered-To
Uses only the Delivered-To entry from the original header of the email to assign it to a user account
Custom Recipient Header
A custom defined header part to be evaluated. Example: envelope-from
