Technical Requirements: PowerSchool ERP 25.7
25.7 Production Environment
Hardware Specs
This document contains the hardware and software requirements for implementing the PowerSchool ERP 25.7.x. The equipment and resources listed herein are required to ensure proper system usability and the highest quality user experience possible.
PowerSchool ERP 25.7.x requires 64-bit, server-class hardware using a 64-bit Windows operating system running Windows Server 2022. Cognos 11 version 11.2.4+ with SQL Server 2022.
Recommended Hardware Specifications
For new customers purchasing new hardware, or existing customers seeking to refresh their hardware, the following recommended specifications will provide better than acceptable performance without requiring excessive resources. The recommended specifications allow room for growth as your district needs to grow and as new PowerSchool ERP versions and features become available in the next few years.
Enrollment < 15K
OS version: Windows Server 2022
DB Version: SQL Server 2022
Server | Number of Servers | Applications Hosted | Minimum # of Cores | Recommended # of Cores | RAM(GB) | Notes |
|---|---|---|---|---|---|---|
Application Server | 1 | Dashboard App, eFinancePlus Web, Gas 4GL App, Windows Services, Notification Plugin & Viewer, Background Services, Workflow API, ERP-UI, ERP HR API, PSERP Core | 8 | 10 | 16 | Genero version: 3.2x Background Service must be setup only on one app server. |
Edge Server | 1 | Dashboard App, eFinancePlus Web, EAC, VAC, ETS, VPO, Workflow API | 8 | 10 | 16 | EMA, Mobile Connector Admin must be external facing. VPO is a single-tenant application and should not be deployed behind a load balancer distributing traffic across multiple server instances doing so can it can also increase the complexity of managing the application across multiple servers. |
Workflow Server | 1 | eFinancePlus Web, Windows Services, Document Service, Shared Service, Compliance App and Compliance Service, Background Services, Notification Services & POD Services, Workflow API | 8 | 10 | 16 | It is required to have an Edge Server and Workflow Server. The Edge Server hosts Employee Facing applications, while the Workflow Server hosts the background services and Document Services. |
API Server | 1 | OIDC API, API, Workflow API, EMA, Mobile Connector Admin. | 6 | 8 | 16 | API must be external facing. API Server is recommended if the customer is using Advanced Workflows. Otherwise the API OIDC Services can be provisioned on the Edge Server. When district need to have one external facing server the EMA, Mobile Connector Admin can be installed on a single API server. |
SQL Data Base Server | 1 | SQL Server | 14 | 16 | 34 | SQL Edition - Standard |
Print Server | 1 | Optio | 4 | 6 | 8 | Print Server & 4js License Manager can merge with SQL server |
Enrollment 15K - 25K
OS version: Windows Server 2022
DB Version: SQL Server 2022
Server | Number of Servers | Applications Hosted | Minimum # of Cores | Recommended # of Cores | RAM(GB) | Notes |
Application Server | 2 | Dashboard App, eFinancePlus Web, Gas 4GL App, Windows Services, Notification Plugin & Viewer, Background Services, Workflow API, ERP-UI, ERP HR API, PSERP Core | 8 | 10 | 16 | Genero version: 3.2x. Background Service must be setup only on one app server. |
Edge Server | 1 | Dashboard App, eFinancePlus Web, EAC, VAC, ETS, VPO, Workflow API | 8 | 10 | 16 | EMA, Mobile Connector Admin must be external facing. VPO is a single-tenant application and should not be deployed behind a load balancer distributing traffic across multiple server instances doing so can it can also increase the complexity of managing the application across multiple servers. |
Workflow Server | 1 | eFinancePlus Web, Windows Services, Document Service, Shared Service, Compliance App and Compliance Service, Background Services, Notification Services & POD Services, Workflow API | 8 | 10 | 18 | It is required to have an Edge Server and Workflow Server. The Edge Server hosts Employee Facing applications, while the Workflow Server hosts the background services and Document Services. The Workflow server does not support multiple instances due to its server dependencies. If needed, its capacity can only be increased by scaling vertically. |
API Server | 1 | OIDC API, API, Workflow API, EMA, Mobile Connector Admin. | 8 | 10 | 12 | API must be external facing. API Server is recommended if the customer is using Advanced Workflows. Otherwise the API OIDC Services can be provisioned on the Edge Server. When district need to have one external facing server the EMA, Mobile Connector Admin can be installed on a single API server. |
SQL Data Base Server | 1 | SQL Server | 14 | 16 | 34 | SQL Edition - Standard |
Print Server | 1 | Optio | 4 | 6 | 8 | Print Server & 4js License Manager can merge with SQL server |
Enrollment 26K - 50K
OS version: Windows Server 2022
DB Version: SQL Server 2022
Server | Number of Servers | Applications Hosted | Minimum # of Cores | Recommended # of Cores | RAM(GB) | Notes |
|---|---|---|---|---|---|---|
Application Server | 2 | Dashboard App, eFinancePlus Web, Gas 4GL App, Notification Plugin & Viewer, Workflow API, ERP-UI, ERP HR API, PSERP Core | 8 | 10 | 16 | Genero version: 3.2x Background Service must be setup only on one app server. |
Edge Server | 1 | Dashboard App, EAC, VAC, ETS, VPO, Workflow API | 8 | 10 | 16 | EMA, Mobile Connector Admin must be external facing. VPO is a single-tenant application and should not be deployed behind a load balancer distributing traffic across multiple server instances doing so can it can also increase the complexity of managing the application across multiple servers. |
Workflow Server | 1 | eFinancePlus Web, Workflow Services, Document Service, Shared Service, Compliance App and Compliance Service, Background Services, Notification Services & POD Services, Workflow API, Workflow Configuration | 8 | 10 | 18 | It is required to have an Edge Server and Workflow Server. The Edge Server hosts Employee Facing applications, while the Workflow Server hosts the background services and Document Services. The Workflow server does not support multiple instances due to its server dependencies. If needed, its capacity can only be increased by scaling vertically. |
API Server | 1 | OIDC API, API, Workflow API, EMA, Mobile Connector Admin. | 8 | 10 | 12 | API must be external facing. API Server is recommended if the customer is using Advanced Workflows. Otherwise the API OIDC Services can be provisioned on the Edge Server. When district need to have one external facing server the EMA, Mobile Connector Admin can be installed on a single API server. |
SQL Data Base Server | 1 | SQL Server | 22 | 24 | 38 | SQL Edition - Standard |
Print Server | 1 | Optio | 4 | 6 | 8 | Print Server & 4js License Manager can merge with SQL server |
Enrollment 51K - 75K
OS version: Windows Server 2022
DB Version: SQL Server 2022
Server | Number of Servers | Applications Hosted | Minimum # of Cores | Recommended # of Cores | RAM(GB) | Notes |
|---|---|---|---|---|---|---|
Application Server | 3 | Dashboard App, eFinancePlus Web, Gas 4GL App, Notification Plugin, Workflow API, UI-UX, ERP-UI, ERP HR API, PSERP Core | 8 | 10 | 16 | Genero version: 3.2x Background Services must be setup only on one app server. |
Edge Server | 2 | Dashboard App, eFinancePlus Web, EAC, ETS, VAC, Workflow API | 8 | 10 | 16 | EMA, Mobile Connector Admin must be external facing. |
Workflow Server | 1 | eFinancePlus Web, Workflow Services, Document Service, Shared Service, Compliance App and Compliance Service, Background Services, Notification Services & POD Services, Workflow API, VPO | 10 | 12 | 18 | VPO is a single-tenant application and should not be deployed behind a load balancer distributing traffic across multiple server instances doing so can it can also increase the complexity of managing the application across multiple servers. The Workflow server does not support multiple instances due to its server dependencies. If needed, its capacity can only be increased by scaling vertically. |
API Server | 1 | OIDC API, API, Workflow API, EMA, Mobile Connector Admin. | 8 | 10 | 16 | API must be external facing. API Server is required if the customer is using Advanced Workflows. Otherwise the API OIDC Services can be provisioned on the Edge Server. When district need to have one external facing server the EMA, Mobile Connector Admin can be installed on a single API server. |
SQL Data Base Server | 1 | SQL Server | 26 | 32 | 64 | SQL Edition - Standard |
Print Server | 1 | Optio | 4 | 6 | 8 | Print Server & 4js License Manager can merge with SQL server |
Enrollment 76K - 100K
OS version: Windows Server 2022
DB Version: SQL Server 2022
Server | Number of Servers | Applications Hosted | Minimum # of Cores | Recommended # of Cores | RAM(GB) | Notes |
|---|---|---|---|---|---|---|
Application Server | 4 | Dashboard App, eFinancePlus Web, Gas 4GL App, Notification Plugin, Workflow API, ERP-UI, ERP HR API, PSERP Core | 8 | 10 | 16 | Genero version: 3.2x Background Services must be setup only on one app server. |
Edge Server | 2 | Dashboard App, eFinancePlus Web, EAC, ETS, VAC, Workflow API | 10 | 12 | 24 | EMA, Mobile Connector Admin must be external facing. |
Workflow Server | 1 | eFinancePlus Web, Workflow Services, Document Service, Shared Service, Compliance App and Compliance Service, Background Services, Notification Services & POD Services, Workflow API, VPO | 10 | 12 | 28 | VPO is a single-tenant application and should not be deployed behind a load balancer distributing traffic across multiple server instances doing so can it can also increase the complexity of managing the application across multiple servers. The Workflow server does not support multiple instances due to its server dependencies. If needed, its capacity can only be increased by scaling vertically. |
API Server | 1 | OIDC API, API, Workflow API, EMA, Mobile Connector Admin. | 8 | 10 | 16 | API must be external facing. API Server is recommended if the customer is using Advanced Workflows. Otherwise the API OIDC Services can be provisioned on the Edge Server. When district need to have one external facing server the EMA, Mobile Connector Admin can be installed on a single API server. |
SQL Data Base Server | 1 | SQL Server | 38 | 40 | 72 | SQL Edition - Enterprise |
Print Server | 1 | Optio | 4 | 6 | 8 | Print Server & 4js License Manager can merge with SQL server |
Enrollment 101K - 125K
OS version: Windows Server 2022
DB Version: SQL Server 2022
Server | Number of Servers | Applications Hosted | Minimum # of Cores | Recommended # of Cores | RAM(GB) | Notes |
|---|---|---|---|---|---|---|
Application Server | 5 | Dashboard App, eFinancePlus Web, Gas 4GL App, Notification Plugin & Viewer, Workflow API, ERP-UI, ERP HR API, PSERP Core | 8 | 10 | 16 | Genero version: 3.2x Background Services must be setup only on one app server. |
Edge Server | 2-3 | Dashboard App, eFinancePlus Web, EAC, ETS, VAC, Workflow API | 8 | 12 | 24 | EMA, Mobile Connector Admin must be external facing. |
Workflow Server | 1 | eFinancePlus Web, Workflow Services, Document Service, Shared Service, Compliance App and Compliance Service, Background Services, VPO, Workflow API. | 10 | 12 | 28 | Background Services must be setup only on one workflow server. VPO is a single-tenant application and should not be deployed behind a load balancer distributing traffic across multiple server instances doing so can it can also increase the complexity of managing the application across multiple servers. The Workflow server does not support multiple instances due to its server dependencies. If needed, its capacity can only be increased by scaling vertically. |
Notification Server | 1 | Notification Services, POD Services | 4 | 8 | 8 | Only required if districts using Notification services. |
API Server | 1 | OIDC API, API, Workflow API, EMA, Mobile Connector Admin. | 8 | 10 | 16 | API must be external facing. API Server is required if the customer is using Advanced Workflows. Otherwise the API OIDC Services can be provisioned on the Edge Server. When district need to have one external facing server the EMA, Mobile Connector Admin can be installed on a single API server. |
SQL Data Base Server | 1 | SQL Server | 42 | 44 | 86 | SQL Edition - Enterprise |
Print Server | 1 | Optio | 4 | 6 | 8 | Print Server & 4js License Manager can merge with SQL server |
Enrollment 126K - 150K
OS version: Windows Server 2022
DB Version: SQL Server 2022
Server | Number of Servers | Applications Hosted | Minimum # of Cores | Recommended # of Cores | RAM(GB) | Notes |
|---|---|---|---|---|---|---|
Application Server | 6 | Dashboard App, eFinancePlus Web, Gas 4GL App, Notification Plugin & Viewer, Workflow Services, Background Services, Workflow API, ERP-UI, ERP HR API, PSERP Core | 8 | 10 | 16 | Genero version: 3.2x Background Services must be setup only on one app server. |
Edge Server | 2-3 | Dashboard App, Dashboard, eFinancePlus Web, EAC, ETS, VAC, Workflow API | 8 | 12 | 24 | EMA, Mobile Connector Admin must be external facing. |
Workflow Server | 1 | eFinancePlus Web, Workflow Services, Document Service, Shared Service, Compliance App and Compliance Service, Background Services, Workflow API. | 10 | 12 | 32 | Background Services must be setup only on one workflow server. The Workflow server does not support multiple instances due to its server dependencies. If needed, its capacity can only be increased by scaling vertically. |
Notification Server | 1 | Notification Services, POD Services | 6 | 8 | 8 | Only required if districts using Notification services. |
API Server | 1 | OIDC API, API, Workflow API, EMA, Mobile Connector Admin. | 10 | 12 | 16 | API must be external facing. API Server is required if the customer is using Advanced Workflows. Otherwise the API OIDC Services can be provisioned on the Edge Server. When district need to have one external facing server the EMA, Mobile Connector Admin can be installed on a single API server. |
SQL Data Base Server | 2 | SQL Server | 28 | 32 | 60 | SQL Edition - Enterprise |
Print Server | 1 | Optio | 4 | 6 | 8 | Print Server & 4js License Manager can merge with SQL server |
Vendor Portal Server | 1 | VPO | 6 | 8 | 12 | Only required if districts are using VPO. VPO is a single-tenant application and should not be deployed behind a load balancer distributing traffic across multiple server instances doing so can it can also increase the complexity of managing the application across multiple servers. If we have considerable number of districts using VPO it is recommend that we use a separate server to install VPO per district or else we can install the VPO on Workflow server. |
Enrollment > 150K
OS version: Windows Server 2022
DB Version: SQL Server 2022
Server Name | Servers | Applications | Minimum # of Cores | Recommended # of Cores | RAM(GB) | Notes |
|---|---|---|---|---|---|---|
Application Server | 8 | Dashboard App, eFinancePlus Web, Gas 4GL App, Workflow Services, Background Services (in on Application Server), Notification Plugin, Workflow API, ERP-UI, ERP HR API, PSERP Core | 10 | 12 | 16 | Genero version: 3.2x Background Services needs to be setup only on one app server. |
Edge Server | 3-4 | Dashboard App, eFinancePlus Web API, EAC, ETS, VAC, Workflow API | 8 | 12 | 24 | EMA, Mobile Connector Admin must be external facing. |
Workflow Server | 1 | eFinancePlus Web API, Workflow Services, Document Service, Shared Service, Background Services. Compliance App and Compliance Service, Workflow Configuration, Shared Services, Workflow API. | 12 | 14 | 32 | Background Services needs to be setup only on one workflow server. The Workflow server does not support multiple instances due to its server dependencies. If needed, its capacity can only be increased by scaling vertically. |
API Server | 2 | OIDC API, API, Workflow API, EMA, Mobile Connector Admin. | 8 | 12 | 16 | API must be external facing. API Server is required if the customer is using Advanced Workflows. Otherwise the API OIDC Services can be provisioned on the Edge Server. When district need to have one external facing server the EMA, Mobile Connector Admin can be installed on a single API server. |
Notification Server | 1 | Notification Services, POD Services | 6 | 8 | 12 | Only required id district using Notification services. |
SQL Data Base Server | 2 | SQL Database | 30 | 32 | 60 | SQL Edition - Enterprise |
File Server | 1 | File Server | 4 | 6 | 8 | |
Print Server | 1 | Optio | 4 | 6 | 8 | |
Vendor Portal Server | 1 | VPO | 6 | 8 | 12 | Only required if districts are using VPO. VPO is a single-tenant application and should not be deployed behind a load balancer distributing traffic across multiple server instances doing so can it can also increase the complexity of managing the application across multiple servers. If we have considerable number of districts using VPO it is recommend that we use a separate server to install VPO per district or else we can install the VPO on Workflow server. |
Print Server
It is recommended that print services should be installed on a separate server, as it requires the opening of print services ports on the server.
The print server should not be shared with the previous versions of the application. If two or more versions of the PowerSchool ERP application are installed for a site, then use a different print server for PSERP 25.7.
SFTP Server
The import and export data files are stored on a SFTP server.
Hosting Customers:
AWS Family Transfer is used as a SFTP service
On-Prem Customers:
On-prem customers can bring in their own managed SFTP servers.
Cognos
For organizations larger than 100,000 enrolled students, a more tailored configuration may be warranted.
Vendor Punchout
VPO is a single-tenant application and must not be placed behind a load balancer with multiple server instances. It is not compatible with deployment behind a load balancer distributing traffic across multiple server instances.
Storage Requirements - Application, Workflow, EDGE, API, Print
Drive Letter | Purpose | Size GB |
C | Operating System | 100 |
D | Application | 80 |
Storage Requirements - Database Server
Drive Letter | Purpose | <= 25K | <= 50K | <= 75K | <= 100K | <= 125K | <= 150K | > 150K | Notes |
C | Operating System | 225 | 225 | 225 | 225 | 225 | 225 | By Consult |
|
D | Application (SQL) | 100 | 100 | 100 | 100 | 100 | 100 | By Consult |
|
E | SQL_MDF | 400 | 500 | 600 | 700 | 800 | 900 | By Consult | |
F | SQL_LDF | 400 | 500 | 600 | 700 | 800 | 900 | By Consult | |
G | SQL_TMP | 150 | 200 | 250 | 300 | 350 | 400 | By Consult | |
H | SQL_BKP | 1500 | 1800 | 2000 | 2200 | 2500 | 3000 | By Consult |
Note: All sizes in GB
* Tier 1 Storage (SSD or 15 Raid 0+1)
** Tier 2 Storage – Size will vary based on how many online backups are required
Software Specs
Client Desktop Requirements
Other than the browsers listed below, the following are required on the client’s desktop:
Adobe Acrobat Reader
Mobile Device Requirements
The following OS systems are required to run the Employee Application
Android – current release plus 1 prior version
IOS – current release plus one prior version
Laptops and Personal Computers
PowerSchool ERP 25.7 supports the following browsers. The older browser and operating system combinations may continue to operate properly but are no longer supported.
Windows Browsers |
Microsoft Edge |
Firefox – current release plus 4 prior versions. |
Chrome – current release plus 4 prior versions. ** |
Mac Browsers |
Firefox – current release plus 4 prior versions. |
Safari – current release plus 1 prior version |
Chrome – current release plus 4 prior versions. |
Application Network
Specific network ports must be open and accessible on the operating system and open on any network-based firewalls to enable PowerSchool ERP applications to communicate.
The external traffic connects to the application servers on ports 443 and this port must be open on both the internal and external firewalls.
Note: The web application and API communications require port 443 externally to operate on. The other ports enabled are used internally for the application to function.
The tables in this section explain the need for the ports:
Port | Protocol | Service | Used For |
80/443 | TCP | HTTP/HTTPS | Browser-based UI access to PowerSchool ERP Applications. API-based communication between applications and External third-party access. |
1433 | TCP | TCP | The default instance of the SQL Server Database Engine listens on TCP port 1433. |
25 | SMTP | SMTP | Port 25 is used as the default port for transmission of email from email server to email server. |
6399 | TCP | TCP | Four J’s license |
515 | LPD | LPD | The sender sends a print job to a queue on the recipient via the LPD protocol. The recipient is expected to receive print jobs on port 515. |
9000 | TCP | TCP | Print Server |
135 | TCP | RPC | Port 135 is needed in an active directory and server/client environment for many services to operate properly. |
137-139/445 | SMB | SMB | Facilitates file share between networked computers. Network file sharing protocol that requires an open port on a server to communicate with other servers. |
5985/5986 | TCP | HTTP/HTTPS | Port user with WinRM 2.0 (Microsoft Windows Remote Management). 5985/TCP for HTTP and 5986/TCP for HTTPS. |
1024 – 1034 | TCP | TCP | Dynamically assigned ports for WMI (Windows Management Instrumentation) |
9389/389 | TCP | TCP | Active directory web services. |
ICMP | IP | IP | The Internet Control Message Protocol is used by servers to send error messages and operational information indicating success or failure when communicating with another IP address. |
22 | TCP | SSH | OpenSSH 6.0 |
3389 | TCP | Terminal Service | Enables remote connection to other computers |
Main Application Server
Source | Destination | Port | Usage |
Application Server | All Hosts | ICMP | Installer ping requirements. |
Application Server | Email Server | 25 | Outbound Emails |
Application Server | Four J’s License Server | 6399 | Four J’s License |
Application Server | SQL Server | 1433 | SQL Server Database Communication. |
Application Server | Optio Server | 515 | Print Jobs |
Application Server | Edge Server / Workflow Server / Notification Server | 80/443 | API Communication |
Application Server | Domain Controller | 9389 | User Validation using Active Directory PowerShell module |
Application Server | File Server | 139/445 | File Share |
Browser Client | Application Server | 80/443 | Browser UI Access |
Jump Server | Application Server | 3389 | Terminal Service |
Edge Server
Source | Destination | Port | Usage |
Edge Servers | All Hosts | ICMP | Installer ping requirements. |
Edge Servers | Email Server | 25 | Outbound Emails |
Edge Servers | SQL Server | 1433 | SQL Server Database Communication. |
Edge Server | Application Server / Workflow Server / Document Server | 80/443 | API Communication |
Browser Client | Edge Server | 80/443 | Browser UI Access |
Jump Server | Edge Server | 3389 | Terminal Service |
API Server
Source | Destination | Port | Usage |
API Server | All Hosts | ICMP | Installer ping requirements |
API Server | SQL Server | 1433 | SQL Server Database Communication. |
API Server | Document Server / Workflow Server | 80/443 | API Communication |
Third-Party API Client | PowerSchool ERP API | 443 | Third Party API Communication |
Third-Party API Client | PowerSchool ERP OAuth API | 443 | Third Party API Authorization |
Jump Server | API Server | 3389 | Terminal Service |
Compliance Server
Source | Destination | Port | Usage |
Compliance Server | All Hosts | ICMP | Installer ping requirements |
Compliance Server | SQL Server | 1433 | SQL Server Database Communication. |
Compliance Server | File Server | 139/445 | File Share |
Browser Client | Compliance Server | 80/443 | Browser UI Access |
Jump Server | Compliance Server | 3389 | Terminal Service |
Workflow/Document Server
Source | Destination | Port | Usage |
Workflow Server | All Hosts | ICMP | Installer ping requirements |
Workflow Server | SQL Server | 1433 | SQL Server Database Communication |
Workflow Server | Email Server | 25 | Outbound Emails |
Browser Client | Workflow Server | 80/443 | Browser UI Access |
Jump Server | Workflow Server | 3389 | Terminal Service |
Notification Server
Source | Destination | Port | Usage |
Notification Server | All Hosts | ICMP | Installer ping requirements |
Notification Server | SQL Server | 1433 | SQL Server Database Communication. |
Notification Server | Email Server | 25 | Outbound Emails |
Browser Client | Notification Server | 80/443 | API Access |
Jump Server | Notification Server | 3389 | Terminal Service |
Print Server
Source | Destination | Port | Usage |
Print Server | All Hosts | ICMP | Installer ping requirements |
Application Server | Print Server | 9000 | Print Services |
Jump Server | Print Server | 3389 | Terminal Service |
External Site Dependencies
URL | Usage |
Dashboard PDS (PowerSchool Design System) | |
Microsoft Azure SSO | |
Google SSO | |
Google SSO | |
Talent Integration | |
FourJs Licensing |
Whitelist IP Addresses
Talent Integration (Ingress)
IP | Port | Usage |
52.71.17.106/32 | 443 | Ingress from Talent to PowerSchool ERP API Server |
Workflow Integration (Ingress)
IP | Port | Usage |
54.69.133.171 | 443 | Ingress from AWS Lambda to eFinancePlus API Server |
Dex