Terminal Services Log

If you define 32bit app startup environment for the users, these users might experience a problem with slow log-off. This problem does not affect Full desktop and it does not happen if user has not printed something from an application.

In case you have Terminal Services Log installed on your server you can check processes being run for each user session. All 32bit sessions will have a process splwow64.exe running. By further investigating we found out the session will not end until this process does not end (in few minutes). This process is converting between 32 bit and 64 bit applications. Process remains in memory in order to increase system performance and unloads from memory after the last print job.

Adjusting Process TimeOuts

You can define how long process will stay in memory. Open regedit and find the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\
Create new 32bit DWORD SplWOW64TimeOut and set it to one minute (decimal 1). This will add one minute delay to unloading process from the memory.

If you want to unload process immediately and log off instantly after print job is finished we need to add one more registry value.
In regedit open:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\SysProcs
and add new  32bit DWORD called splwow64.exe and set it to decimal 0.

Now session with startup environment setup will log off immediately after print job is finished if that is requested by the user.

Additional Reports with Terminal Services Log

You can use Terminal Services Log to closely monitor processes on a Remote Desktop Server. Click here for more details about application reports in Terminal Services Log.

Application Report - Terminal Services Log