Terminal servers are made for an average work load and are dependent on applications to release their resources as fast as possible when disconnecting from the RDP session. A client in normal configuration would stay in the memory and prevent the session from being closed completely, since the client is also serving as a server for the add-ins.

The setting ShutdownOnDisconnect in OneOffixx.exe instructs the client to shut down automatically as soon as Session Disconnect reaches it. This may be noticed by the user when OneOffixx starts again in the background after every Session Start.

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

New since 3.0 This setting can be adjusted in the Setup through the UI or a parameter.

It must be assured that every OneOffixx client has its own exclusive access to the cache in the Load Balanced Terminal Server environment. This can be ensured through the correct supply of the cache folder.

Another option is to exclude the OneOffixx client from Active State monitoring in the terminal server.

Citrix XenApp and Terminal Server

Further information can be found in the following articles:

Example registry: Citrix

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Citrix\wfshell\TWI
   Value Name:LogoffCheckSysModules
   Type:REG_SZ
   String:OneOffixx.exe

Microsoft Terminal Server

Further information can be found in the following article:

Example registry: Terminal Server

   HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Control\Terminal Server\Sysprocs
   Value name: OneOffixx.exe
   Data type: REG_DWORD 
   Base: Hex

Caution! The terminal server needs to be restarted after this setting.