2022.2

Preferences button under the PReS Workflow (W) button, or via the key combination
Ctrl+Alt+P .
Network considerations
While PReS Workflow is typically installed on a server machine that is only accessed by one single user
such as an IT person, multiple users logging on to that machine is a possibility (except with terminal
servers, see "Environment considerations" on page18). Because each user may have different local
and network rights, it may be important to consider the implications in regards to PReS Workflow. To
change the service log on information, see "Workflow Services" on page285.
Local and network rights
Programs, such as PReS Workflow and all its services, must identify themselves in order to be granted
permission to perform operations on the computer on which they run as well as on other computers
accessible via a network connection. On a given workstation, you can configure your PReS Workflow to
use either the local system account or any specific user account. When you do this, you grant PReS
Workflow and all its services the same rights associated with the selected account.
When you are running PReS Workflow Configuration program on a workstation, if it is associated with
an account that is different from your account, the following icon is displayed in the lower right corner of
PReS Workflow Configuration program: . The icon reminds you that the logon information is different
for the PReS Workflow services, and that some network resources may not be accessibly by PReS
Workflow when running a live configuration.
Account requirements
PReS Workflow and its services require administrator rights to run on any given computer and must
therefore be associated with an account that has such rights.
We recommend creating a network or domain account specifically for the PReS Workflow services,
which has administrator credentials on the machine where it is installed, and is given proper rights for
any network resources your configuration may request.
Mapped drives
It is strongly recommended to use local folders instead of mapped drives whenever possible.
Mapped drives (for example, drive X: leading to \\server\public\) are always user-specific and are cre-
ated at logon. This means that mapped drives are typically not available to the PReS Workflow services
when running a live configuration.
Furthermore, while the mapped drives are not shared, they are still limited to one map per computer,
meaning if one user maps the X: drive, a different user (or a service) will not be able to map it again.
This creates a limitation in PReS Workflow: if you create a mapped drive as a user, you will not have
access to this mapped drive while running as a service unless you log off, and then have PReS Work-
flow Tools map the drive using a Run Script action inside a Startup Process.
Page 25