Forum Discussion
bbklogin
12 years agoOccasional Contributor
Hello :)
We did spend some time researching this, uninstalling the KB2592687 will eliminate this prompt by downgrading the RDP version from 8 to 6.1; however, our IT is not happy with that as this update is a security update from MS.
As you suggested Manual mode does not work for our setup.
I have spent several hours with Microsoft Support and asked for way to bypass this warning and was told it is by design. They have suggested contacting you and asking for RDP client to be signed as part of Test complete engine.
Below is the final email I received from MS support
To follow up our conversation on the phone, the behavior you are seeing with the warning prompt is by design.
From a Web Application, you can only use the scriptable version which always shows the warning message unless you choose not to redirect any resources. Your only option is to use a signed RDP file. This is described in the following blog post:
http://blogs.msdn.com/b/rds/archive/2009/01/05/why-you-should-sign-rdp-files-and-how-to-script-the-signing.aspx
Any Help and suggestion is greatly appreciated
We did spend some time researching this, uninstalling the KB2592687 will eliminate this prompt by downgrading the RDP version from 8 to 6.1; however, our IT is not happy with that as this update is a security update from MS.
As you suggested Manual mode does not work for our setup.
I have spent several hours with Microsoft Support and asked for way to bypass this warning and was told it is by design. They have suggested contacting you and asking for RDP client to be signed as part of Test complete engine.
Below is the final email I received from MS support
To follow up our conversation on the phone, the behavior you are seeing with the warning prompt is by design.
From a Web Application, you can only use the scriptable version which always shows the warning message unless you choose not to redirect any resources. Your only option is to use a signed RDP file. This is described in the following blog post:
http://blogs.msdn.com/b/rds/archive/2009/01/05/why-you-should-sign-rdp-files-and-how-to-script-the-signing.aspx
For your scenario, you will need to specify a signed RDP file, RdpFileContents property.
http://msdn.microsoft.com/en-us/library/aa381310(v=vs.85).aspx
Any Help and suggestion is greatly appreciated
Related Content
- 12 years ago
- 14 years ago
- 3 years ago
- 3 years ago