Delay when exiting a RemoteApp about freerdp

[awakecoding]

@meosborne: how long of a delay? as the description says, it's a message sent by the server. in this case, the server sends it when no application is running. I don't know if the client really is at fault here.

[awakecoding]

@meosborne: please provide more insight regarding this "bug", since I'm not even sure this is a client side bug. I'd like to close this issue if it turns out not to be a real issue.

[awakecoding]

I am closing this issue due to the lack of additional information. Feel free to re-open it if you feel like this is a bug to be fixed in FreeRDP.

[meosborne]

I've done some further investigating on this and it appears to not be a freerdp bug. Here's some info for others seeing this issue:

http://support.microsoft.com/?kbid=2513330.

This is what was causing my issue. I have a 32-bit app on 2008R2. The app starts the splwow64 process so it can print. It turns out that that process has a 3-minute timeout before it exits. That leaves the user session on the server active until it quits. You can tell the server that this process is ok to terminate immediately by adding the following registry key:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\Sysprocs]

Value name: splwow64.exe
Data type: REG_DWORD
Base: Hex
Value data: 0

Of course, you must have admin access to the server to do this.