There are several considerations for the Workbench Server Environment.
Microsoft Window Server Operating System
The supported Windows Server versions:
Windows Server 2008 R2(End of Life imminent)- Windows Server 2012
- Windows Server 2012 R2
- Windows Server 2016
- Windows Server 2019
.NET Framework 4.6.2 or higher will need to be installed on the server, which is a pre-requisite for SQL Server 2016 and later.
Network
It is required to install Workbench into a Windows Active Directory Domain. In this configuration, users are granted access to the Workbench Application Share and the Workbench databases via Active Directory user security groups. This allows users to log into Workbench and SQL Server using their Windows Domain credentials.
Workbench is not supported in a 'Workgroup', or peer-to-peer network (computers connected in a non-domain network).
Workbench can send email via SMTP, which is dependent on the emailing engine in WebWorkbench, or via Microsoft Outlook from the desktop MDE program.
Custom SMTP servers can be specified in WebWorkbench configurations.
Workbench Users (Active Directory Security) Group
The recommended configuration is to create a 'Workbench_Users' Active Directory (Global) Security group, which Workbench user (Active Directory) accounts are added too. The required system permissions are then assigned to the user group. The Workbench Users group is normally granted access to the Workbench Application Share, SQL Server, and other Workbench components.
Workbench Application Share
The Workbench server hosts the Workbench Application folder, which is shared on the network. This folder needs to be accessible to the all Workbench client PC's / users, and other Workbench components if they are hosted on different servers.
PowerShell
PowerShell v5.0 or higher should be available to the Workbench administrator.