Introduction

The System Frontier architecture consists of three main components:

• Database (Microsoft SQL Server 2019 or newer)
• Execution host service (Windows service)
• Web application (Blazor Server application on IIS)

These components can be installed on a single Windows server or across multiple servers for redundancy and scalability.

While the application components run on Windows servers, System Frontier can manage Linux and other operating systems, network devices, Active Directory, cloud and on-premises, with the right credentials and connectivity, using custom tools.

Getting ready

For the best experience, ensure the following are configured and in place before beginning the install process.

• Active Directory domain
• One or more virtual or physical Windows servers
  • The latest OS is recommended but we support versions that are currently supported by Microsoft.
• An empty SQL Server database named SystemFrontierV2 (for example)
  • The latest Microsoft SQL Server version is recommended but we support versions that Microsoft supports.
  • Use the default collation of SQL_Latin1_General_CP1_CI_AS.
• A SQL login with db_owner role to the database.
• A privileged domain service account.
  • This account will be used to execute scripts and admin tasks on the execution host server(s) and will need administrative rights on target systems or at least enough rights to perform the tasks being delegated with System Frontier.
    _{Note: It is recommended that you do not use an account with Domain Admin rights.}
• (Optional) A second domain service account with limited rights to be used for Active Directory queries and backend tasks.
• You can download the latest latest version from your account page.

Installation order

For the best results, install each component in the following order.

1. Database
2. Execution host
3. Web

Post-install configuration

Follow the post-install configuration guide to ensure everything is ready to start using System Frontier.