Atria v12.11+ System Requirements

Overview 

The following article provides the prerequisites necessary for the deployment of Atria v12.11+ into your environment. 

System Requirements  

Environment 

Core servers for the platform should be domain joined. Before you can deploy Atria the Active Directory schema must be extended to include the standard Exchange attributes.  This is required to prepare the environment for multi-tenancy and is mandatory even if you do not intend to deploy Exchange.  

The commands referenced below are from the following Microsoft article -  Extend Active Directory Schema with Exchange Attributes. 

To extend the schema, use the schema prep tool from the Microsoft Exchange Installation Media and run the following commands from a Windows Command Prompt (example): 

E:\Setup.exe /IAcceptExchangeServerLicenseTerms /PrepareSchema 

E:\Setup.exe /IAcceptExchangeServerLicenseTerms /PrepareAD /OrganizationName:”A101” 

Core Component Environment 

For our latest supported Server, Database and Service versions please refer to the following article:  Supportability Matrix

The minimum recommended specifications for the core components are: 

# of Server	Server	vCPUs	RAM	Core Component Services
1	Provisioning Server	4	8 GB	Atria Config Service, Directory Web Service, Provisioning Engine
1	Database Server	4	8 GB	Atria Database, Atria Reporting
1	Web Server	4	8 GB	Atria Web

There is a high chance of extensive DIsk I/O during the installation. High-performance storage is recommended. 

Architecture

Windows OS Version 

The minimum recommended version for all core platform components is Windows Server 2012 R2 

Database - SQL Version 

The minimum recommended version of Microsoft SQL Server is 2012. The highest version currently support is SQL Server 2017.

Make sure that your SQL deployment is configured to have Mixed Mode Authentication. 

Make sure that the SQL configuration for the TCP/IP properties are enabled properly.

During installation include SQL Tools such as SQL Management Studio and SQL Profiler. 

Windows Domain Administrator Account 

It is a requirement that a Domain Administrator account is used to run the entire Atria deployment process. 

Firewall and Network Requirements

The following table outlines the required network protocols and ports for communication between the Atria components.

From	To	Protocol	Port	Notes
Internet	Web Server	TCP	443
AD Sync	Web Server	TCP	80, 443	Communicates with the API Service
Web Server	Provisioning Server	TCP	80, 8095
Web Server	SQL Server	TCP	1433 / Custom SQL Port
Web Server	Config Service	TCP	8095
Web Server	Reporting Server	TCP	1433, 80, 8095
Web Server	Remote AD Provisioning Server	TCP	80, 8095
Web Server	Web Services	TCP	8095	Web Services are deployed on servers such as Exchange and SharePoint
Web Server	Remote AD Web Services	TCP	8095
Web Services	Provisioning Server	TCP	8095
Provisioning Server	SQL Server	TCP	1433 / Custom SQL Port
Provisioning Server	Web Services	TCP	8095	Web Services are deployed on servers such as Exchange and SharePoint
Provisioning Server	Remote AD Provisioning Server	TCP	80, 443
Provisioning Server	SMTP Relay Service	TCP	25	SMTP Relay is required for system generated emails
Report Server	SQL Server	TCP	1433 / Custom SQL Port
Remote AD Provisioning Server	Provisioning Server	TCP	80, 443, 8095
Remote AD Provisioning Server	SQL Server	TCP	1433 / Custom SQL Port
Remote AD Provisioning Server	Remote AD Web Services	TCP	8095	Web Services are deployed on servers such as Exchange and SharePoint
DMZ Web Server	Provisioning Server	TCP	80, 443, 8095, 8098, 1433 / Custom SQL Port

If planning to setup the AtriaWeb on a DMZ environment, make sure that the firewall rules are open especially (HTTP/HTTPS). The installer will communicate with the AtriaConfigService to retrieve encryption keys to be set to this component. Make sure also to open the traffic from AtriaWeb going to AtriaSQL via the SQL port.

Enable WebSockets on Network Firewall/LoadBalancer

Coming into 12.11+, the platform now is running through websockets and it is a different protocol over the same ports as http and https, but if firewalls or loadbalancers are not correctly configured it will get denied. Check and enable to accept websockets but this depends on your firewall/loadbalancer that handles it.

For example: If using WebProxy going to external it looks like this:

Prerequisite tools for Atria v12.10+ deployment 

For each server that will have core components or web services installed, the below prerequisite items must be installed.  From version v12.11+ the database installation should be run from the Provisioning Server, so prerequisite items are not required on the SQL Server.

1. Powershell 5.1 (if on Windows 2012 R2), Otherwise this is the standard version on Windows Server 2016/2019
   
2. .NET Framework 4.8
   
Please check if Powershell and .NET server version are both supported by your services (i.e. Exchange, Virtual Apps & Desktops, etc.) If not, then the latest CU or software version of your services needs to be implemented. If not possible, then we can retain the CPSM web services as is until it is ready.

3. Add CNAME DNS records for Atria Core Components
   
1. AtriaConfigService
   
2. AtriaSQL
   
3. AtriaProvisioning
   
4. AtriaWeb
   
4. Create a Domain Admin account that will be used for Atria installation.

Request Access Token and Deployment Record ID from Automate101 Support

To add the Atria Installers Package Source, you'll first need to have an  Access Token. To obtain a token please log a support ticket with Automate101 Support and one will be provided to you.  You can contact support via the Support portal at http://support.automate101.com/ or email support@automate101.com

In addition to the Access Token, Automate101 Support will be providing a Deployment Record ID that will be used during the Install/Upgrade to Register Atria.

Export the existing provisioning rules from CPSM (Optional)

This step is usually handled during environment assessment being done by Automate101

When doing the Atria deployment, provisioning rules that were previously added/modified within the Main hive of the provisioning rules will be reverted to its original rules/structure. Any rules that were added/modified we suggest that it should be on the Before or After events of provisioning/de-provisioning. Otherwise, you need to manually add/modify the rules after the deployment. (The assessment of the exported rules will help identify the rules affected)

To export the provisioning rules, follow this procedure - How to Export Provisioning Rules

• Related Articles

• Atria v15+ System Requirements

  Overview  The following article provides the prerequisites necessary for the deployment of Atria v15+ into your environment.    System Requirements   Environment  Core servers for the platform should be domain joined. Before you can deploy Atria ...

• Atria Billing Setup User Guide

  Objective This article describes how to configure Atria to utilize the latest billing features. This document outlines the billing setup attributes that should be configured.    Applies to Introduced in Atria version 12.0.0 Billing Setup Overview To ...

• Billing Process Overview

  Objective This article outlines, at a high level, the billing features available in Atria.  The billing feature provides transparency of Atria billable services that have been consumed, down to the day.      Applies To Introduced in Atria version ...

• Billing Rules Engine User Guide

  Objective This article describes how to use the Atria billing rules engine to identify specific Atria entities as non-billable.   Applies to Introduced in Atria version 12.0.0 Billing Rule Feature Overview Many entities - customers, services, users, ...

• Atria API

  Atria API Purpose The Atria API is a new Rest-based integration point that over time will replace the functionality of the old API, (known as the CortexAPI). If you have developed against The CortexAPI, don’t worry, it’s still working and supported. ...