2020.1

Table Of Contents
l The Connect Designer module requires more RAM and fast disk access to provide a
responsive user-experience.
l The back-end database (MySQL by default) benefits from more RAM, speedy disk access
and fast networking as it will be solicited by all modules simultaneously.
Environment considerations
This page provides technical information about the environment in which PReS Workflow is
intended to run.
Terminal Services
PReS Workflow does not support Terminal Services environment as possible under Windows
2000, 2003 and 2008. This is to say, if Terminal Services is installed on the server where PReS
Workflow is located, unexpected behaviors may occur and will not be supported by our
company. Furthermore, using PReS Workflow in a Terminal Service environment is probably
an infringement of our End-User License Agreement.
Terminal Services may also be referred to as Terminal Server or Remote Administration Mode
(Windows Server 2003 and 2008).
Single-User Remote Desktop Protocol (RDP) (where only one person can use RDP at a time)
is supported for PReS Workflow version 6.2 and higher, however it is only supported in
Windows XP or Windows 2003. While later versions of Windows may not cause issues when
accessing PReS Workflow through RDP, these combinations are no longer tested and may not
be functional.
Virtual environments
PReS Workflow supports the following virtual environments:
l VMWare Environments. This includes VMWare Player, VMWare Workstation as well as
VMWare ESX Server.
l
VMWare VMotion. This means the virtual machine hosting PReS Workflow can be
automatically moved from one ESX server to another in a clustered installation.
Page 18