...
...
...
...
...
...
...
...
...
...
...
...
| Table of Contents |
|---|
...
Summary
Best practices for installing the Performer Suite (PS) to achieve the best work result.
There are multiple ways to use the PS:
Starting with the super simple local back-pocket solution to a centralized Citrix rollout for 100 users.
It all depends on your scale.
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
TLDR: Go for the instance on a server. |
Central PS instance on a server
📊 Advantage
Performance:
If this used the server is close to the Performer Suite your PS-database, then this should be the most powerful solution.Savings Time and Effort:
When updating the Performer Suite PS client software, the update only needs to be installed once on the server (and not on all local devices).
...
Initial setup:
All users must be given write permissions to the install folder, as the workspace happens by default in the install folder.Alternatively, if needed, redirect the working- and userpath via built-in command line arguments.
Maintenance:
A key user should have Windows administrator rights on this server to be able to perform updates and install bug and hotfixes on short notice to achieve the best working result.
Installation on local devices
📊 Advantage
Testing:
Bug- and hotfixes can be installed and tested faster locally than on a server because Windows permissions are (most of the time) less strict.Working Speed Client:
Local devices are (most of the time) more powerful than a server…
...
Working Speed database:
... but keep in mind, the further away the client-software client is from the Performer Suite database, the slower the application processing time will be, as the Performer Suite PS is constantly communicating with its database.e.g. home office, VPN, or WLAN instead of LAN already extends the latency to the database.