2020.1

Table Of Contents
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
Mapped drives (for example, drive X: leading to \\server\public\) are always user-specific and
are created at logon. This means that mapped drives are typically not available by 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 Workflow Tools map the drive using a Run Script action inside a Startup Process.
Page 22