RDM no longer functional after W10 Anniversary Update
Hi David & Jean-François,
Looks like the 64bit version works fine. Thanks for your help. Hopefully Microsoft releases an update shortly.
Jake
RDM no longer functional after W10 Anniversary Update
Hi David,
I changed it to RDP 7, but it made no difference. Also tried RDP 6.1 and 8.1, but were also the same.
Jake
RDM no longer functional after W10 Anniversary Update
Hi,
RDCMan comes up with a password prompt (saying login attempt failed). After entering the same password it logged in ok.
I exported the connection from RDM as an RDP file, then edited in mstsc and resaved as a new file. (I removed servername details via notepad)
Looks like it added these lines:
screen mode id:i:2
desktopwidth:i:800
desktopheight:i:600
connection type:i:7
enableworkspacereconnect:i:0
gatewaybrokeringtype:i:0
use redirection server name:i:0
rdgiskdcproxy:i:0
kdcproxyname:s:
Files are also attached.
Jake
RDM no longer functional after W10 Anniversary Update
Hi,
Yes, the credentials for gateway and host are the same. It is set to 'use the same rd gateway credentials on remote computer'.
I tested with inherited (which work for another host in the same folder that does not use the RD gateway), and Default. Also tried without any credentials, which prompts for a password (not the rdm password prompt, but the windows password prompt), but still fails after entering the correct password. Same results with NLA off and on.
It might be something with the remote desktop gateway server itself. Possibly the new version of mstsc (v10.2 by the looks of it) changed an authentication method. When testing with a host with a 2012/2012R2 RD Gateway it worked, but 2008/2008R2 gateways didn't.
Jake
RDM no longer functional after W10 Anniversary Update
Hi,
I also just installed the W10 Anniversary Update, and am using RDM Enterprise 11.6.2.0, and cannot connect via embedded RDP when a remote desktop gateway is used. Connects fine when using external (but prompts for password).
Embedded works fine as long as no RD gateway is used.
Debug logs shows:
Opening in Console / Admin mode
Your computer can't connect to the Remote Desktop Gateway server. Contact your network administrator for assistance.
RDP - Disconnect:50331656 / exDiscReasonNoInfo
Also tested on a new machine, and the same issue occurs. If it makes a difference, data source is Azure SQL.
Jake