RemoteApp does not show window logon banner about freerdp

[awakecoding]

@westtexan: there is no check for what windows are, if the server was indeed sending messages to display a window other than the application passed as a parameter, you'd see it.

What is the command you are using to launch RemoteApp? Maybe you got it wrong.

Is it known to work with mstsc.exe in RemoteApp mode?

[westtexan]

I am using the following command:

westtexan@mc-debian:/usr/lib/freerdp$ xfreerdp -u westtexan --app --plugin rail --data '||Activity' -- terminalserver1
loading plugin rail
connected to terminalserver1:3389
Password:
.... There was a 120 second pause where I am guessing it is waiting for me to click OK on a window I cannot see ...
rdp_client_connect_demand_active failed
SSL_read: I/O error
SSL_read: I/O error
Failed to check FreeRDP file descriptor
westtexan@mc-debian:/usr/lib/freerdp$

It works fine using mstsc.exe on Windows 7. I have a screen capture of the logon banner that mstsc.exe shows - http://i51.tinypic.com/6pq5wo.png. Notice that it includes an extra message at the top, "Waiting for RemoteApp programs to start...Please review any messages that appear." This makes me think that the window is presented differently to the client so that mstsc.exe know that the actual application has not started yet. Has any confirmed that FreeRDP can work with logon banners? I think that forcing RDP authentication instead of NLA would cause the same issue, since it would present the full-screen logon window before the single-window RemoteApp.

[awakecoding]

@westtexan: I tried setting the "Message text for user attempting to log on" group policy, but I am not getting the banner on logon in both desktop and RemoteApp modes. Is there anything else I should configure to replicate your settings?

[westtexan]

@awakecoding: According to www.ultimatewindowssecurity.com, "enabling this setting without also enabling 'Interactive logon: Message title for users attempting to log on' will fail to display this message. Both settings must be configured."

[nfedera]

@westtexan: May I ask you to evaluate my fix/workaround:
nfedera@465c5e8
If it works I'll send a pull request.

[westtexan]

I just tested it and it works as expected for my environment. I am able to
click "OK" to the logon banner, and can login interactively with our
alternate authentication provider. I don't know the technical changes
involved with this fix, but the behavior is consistent with Microsoft's
implementation. Thank you!!

On Fri, Dec 30, 2011 at 11:42 AM, Norbert Federa <
[email protected]

wrote:

@westtexan: May I ask you to evaluate my fix/workaround:

nfedera@465c5e8
If it works I'll send a pull request.

---

Reply to this email directly or view it on GitHub:
#143 (comment)

[nfedera]

@westtexan: Thanks for testing. It is merged into master already.
Please close the issue if it works for you.