1 Citrix XenApp / Terminal Server
2 Option: ShutdownOnDisconnect
3 Option: TrySyncOnLogOff
4 Option: UseLazyLoadingCache
5 primedocs Cache
6 Settings for Outlook
- 6.1 Via Registry/GPP
- 6.2 Via GPO
7 Citrix XenApp and Terminal Server
- 7.1 Registry example: Citrix
8 Microsoft Terminal Server
- 8.1 Registry example: Terminal Server

Citrix XenApp / Terminal Server

Terminal servers are designed for an average workload and rely on the applications to release their resources as quickly as possible when the RDP session is disconnected. Since the client also serves as a server for the add-ins, it would remain in memory with normal configuration and prevent the session from being completely terminated.

NOTE
The following options also work on a "desktop" PC, but the option is more useful for Citrix or terminal server deployments.

Option: ShutdownOnDisconnect

By setting ShutdownOnDisconnect in the "primedocs.exe.config"-file the client will be shutdown automatically as soon as it receives the Session Disconnect from the terminal server. This setting can be adjusted via a parameter in the Setup.

<configuration>
  [...]
  <appSettings>
    [...]
    <!-- Allows to configure primedocs to shutdown 
          when a disconnect happens (such as disconnecting from an RDP Session) -->
    <add key="ShutdownOnDisconnect" value="true" />
    [...]
  </appSettings>
  [...]
</configuration>

Option: TrySyncOnLogOff

By setting TrySyncOnLogOff in the "primedocs.exe.config" file the client tries to synchronize the last state to the server before the Session Logoff. This can be useful if the cache is not stored permanently, for example, and if data loss is to be avoided.

WARNING
If the user does not log out correctly or exits primedocs early, data loss may occur despite the setting.

This setting can be adjusted via a parameter in the Setup.

<configuration>
  [...]
  <appSettings>
    [...]
    <!-- Before a Windows Session logoff the client can try to sync its latest changes to the server. A user might "kill" the application, so this is "Best Effort" and might not work depending on the user action. -->
    <add key="TrySyncOnLogOff" value="true" />
    [...]
  </appSettings>
  [...]
</configuration>

Option: UseLazyLoadingCache

The UseLazyLoadingCache setting in the "primedocs.exe.config" file puts the client in an alternative mode so that binary data from templates and snippets are only loaded when they are used. This option can be particularly useful in terminal server environments to enable a quick initial start.

WARNING
This option can cause delays when using a template or snippets for the first time. If the service is not available during this time, an error is displayed.

This setting can be adjusted in the Setup via a parameter. The advantages and disadvantages are explained in more detail here: Synchronization

primedocs Cache

In a Load Balanced terminal server environment, it must be ensured that each primedocs client has exclusive access to the cache. This can be ensured by properly deploying the cache folder. Optionally, the primedocs client can be excluded from Active State monitoring in the terminal server.

Settings for Outlook

Outlook's security model assumes by default that up-to-date antivirus software is installed. However, in Terminal Server or Citrix environments, Outlook cannot retrieve this status. This results in the user having to constantly confirm primedocs access to the Outlook address book.

To suppress these messages, the following settings must be made either via Registry/GPP or via GPO:

Via Registry/GPP

[HKEY_CURRENT_USER\software\policies\microsoft\office\16.0\outlook\security]

"PromptOOMAddressBookAccess"=dword:00000002
"PromptOOMAddressInformationAccess"=dword:00000002
"AdminSecurityMode"=dword:00000003

Via GPO

Further Outlook configuration options are described here.

Citrix XenApp and Terminal Server

For more information, see the following articles:

Registry example: Citrix

Microsoft Terminal Server