AdminTool with User Interface
Admin Tool
- Allows for changing parameters set on installation
- Located in Start -> EgoSecure product group.
Database Settings
Specifying a database
- Select a database type.
- Enter the name of the database server.
- Specify the user data of an authorized database user. To log on to the database with a valid Windows user account, leave the User and Password fields empty and enable the Windows authentication check box.
- If you use Microsoft SQL Server and Always On availability groups are set up, you can enable MultiSubnetFailover option. For details about MultiSubnetFailover, see the Microsoft article.
Creating a new database
- Select a database type (SQL Server or Azure SQL).
- Enter the name of the database server.
- Enter the name for a new database.
- Specify the user data of an authorized database user.
- Click Test.
- If no database with such a name exists on the server, the new dialog that prompts to create a database appears.
- Click Yes.
- New database is created.
Enabling Windows authentication
To use Windows Authentication, EgoSecure Server and SQL Server must be in the same domain.
- Log in to the EgoSecure Server computer as a domain user.
- Enable the Windows Authentication checkbox in the Database Settings section. If you have already specified a local account to log in to the EgoSecure Server service, a warning message appears, because you must specify a user account for Windows Authentication. In this case, enter a user account (step 3).
- Specify the domain user account in the Server service login as field in Admin Tool.
- Click Save. Click Yes to restart the server.
Log Level
|
Option |
Description |
|---|---|
|
Normal |
Only error events are stored in the log file. |
|
Administration |
Detailed log file. |
|
Debug |
Very detailed log file. When the mode is enabled, log files take a lot of space. But this mode is used to analyze errors by the EgoSecure support. |
Server Settings
For the communication between the EgoSecure Server and the EgoSecure Agents various ports are used.
|
Port |
Usage |
|---|---|
|
Agent port |
Port on the Server for incoming connections used by Agents. |
|
Console port |
Port on the Server for incoming connections used by the Console. By default, the same port for transferring changes to the Server is used by the Agents. To increase the performance of Console-to-Server transfers, specify a different port here. |
|
HTTPS port |
Port for incoming connections on the Server via HTTPS. |
|
Agent notification port |
Port on the Agents for incoming connections. In the Normal mode, this port is used by the Server to send notifications about permission changes to the Agents. In the Polling mode, this port is NOT used, because notifications about permission changes are saved to the database and the Agents take them from the database during one of their intervals. |
If the default ports are already used by another application, change the values of the Agent Port and Agent Notification Port to make communication between Agent and Server possible.
- Use FQDN for client connections. This option is disabled by default. In the FQDN mode, no IPs are used for communicating, only the full Agent computer name (e.g.: username.domain.local). Enable this option only if the default way of connection (IP + short domain name) is not possible.
- Enable IPV6 support. By default, IPV4 protocol is used for the communication between Agent and Server. To use IPV6, enable the check box.
Receiving data from Agents – options
- Accept audit data. This option is enabled by default. If disabled, the EgoSecure Server doesn’t receive audit data from Agents.
- Accept shadowcopy data. This option is enabled by default. If disabled, EgoSecure Server doesn’t receive shadowcopy data from Agents and, therefore, it is not available to download a shadow copy of a file from Console.
- Accept data for devices DB. This option is enabled by default. If disabled, the information about devices is not saved to the devices database, which can be used in Console under Permitted devices | Individual device permissions, Permitted device models, Bluetooth devices, Devices list for encryption.
Service Bus configuration
Service Bus is used to transfer changes from the EgoSecure database (used for the desktop version of Console - the EgoSecure Data Protection Console) to the UUX platform database (used for the browser version of the Console – the EgoSecure Data Protection UUX Console).
- Enabling and configuring Service Bus
- Set the Enable Service Bus check box.
- Near Service Bus system, select which system you use.
- Fill in the Connection string, Topic name and Pipeline name fields, with the data from the Service Bus system you already have.
- Click Save.
If you have already setup other components, the synchronization starts. If not, use the Resynchronize button when all elements are set up.
- For details, about using Service Bus, see Service Bus Integration.