General information

Use Cases

If you work with a terminal server, you have one (or more) servers on which several users can log in. The users then log in via a remote desktop connection with their own end device and work in parallel on one or more servers. The two use cases are described below:

• The user profile is persistent.
  When using persistent user profiles, no data stored in the user profile is deleted. If several users log in at the same time, the data for several user profiles must be synchronized at the same time when empower® is synchronized. This leads to a higher load.
• The user profile is not persistent.
  When using non-persistent user profiles, data stored in the user profile may be deleted. Each time the user logs in, the data must then be completely synchronized again by empower®. As a result, it may take longer for the user to log in.

Troubleshooting

For the cases mentioned above, empower has set up terminal server support. With terminal server support, empower® communicates directly with the backend and the database, so synchronization is no longer necessary. This reduces the load on the system and avoids synchronization altogether.

Technical Details

Functionality

There is no local cache in terminal server support. In this case, the client communicates live with the backend and the database, which means that synchronization is no longer necessary. All read and write operations in empower® work in this mode. The binary data - i.e. files such as images, presentations or other non-text-based content - continue to be cached locally. The data is not pre-synchronized. They are only downloaded when they are opened.

This has the following advantages for empower® in a terminal server environment:

• empower® is ready for immediate use without initial synchronization.
• As little as possible is stored locally. This means that local caches are bypassed.

Setting Up Terminal Server Support

Terminal Server Mode is always set up and tested together with empower® Support.