RDP Button - Not working - Potentially an issue on my PC

[DustinB]

Is anyone else having issues with the RDP button not launching RDP when attempting to connect to the console of a VM?

It could very well be on my side (laptop), lord knows. If I launch MSTSC manually and input the IP address I can connect just fine.

TIA

[Tristis Oris]

yeah it really do nothing. Probably it should open some rdp client, same as ssh button.

Tried changing state of a disconnected RFB object index.js:1:125915
    Error http://1.2.3.4/index.js:1
    _updateConnectionState http://1.2.3.4/index.js:1
    disconnect http://1.2.3.4/index.js:1
    _clean http://1.2.3.4/index.js:163
    f http://1.2.3.4/index.js:163
    (Асинхронный: setTimeout handler)
    _onUpdateState http://1.2.3.4/index.js:163
    _updateConnectionState http://1.2.3.4/index.js:1
    p http://1.2.3.4/index.js:1
    onclose http://1.2.3.4/index.js:1
    (Асинхронный: EventHandlerNonNull)
    open http://1.2.3.4/index.js:1
    _connect http://1.2.3.4/index.js:1
    _updateConnectionState http://1.2.3.4/index.js:1
    connect http://1.2.3.4/index.js:1
    f http://1.2.3.4/index.js:163
    componentDidMount http://1.2.3.4/index.js:163
    notifyAll http://1.2.3.4/index.js:111
    close http://1.2.3.4/index.js:111
    closeAll http://1.2.3.4/index.js:111
    perform http://1.2.3.4/index.js:111
    perform http://1.2.3.4/index.js:111
    perform http://1.2.3.4/index.js:111
    O http://1.2.3.4/index.js:111
    closeAll http://1.2.3.4/index.js:111
    perform http://1.2.3.4/index.js:111
    batchedUpdates http://1.2.3.4/index.js:111
    e http://1.2.3.4/index.js:111
    i http://1.2.3.4/index.js:111
    enqueueSetState http://1.2.3.4/index.js:111
    setState http://1.2.3.4/index.js:143
    onStateChange http://1.2.3.4/index.js:143
    v http://1.2.3.4/index.js:143
    n http://1.2.3.4/index.js:143
    connectStore http://1.2.3.4/index.js:167
    (Асинхронный: promise callback)
    connectStore http://1.2.3.4/index.js:167
    emit http://1.2.3.4/index.js:14
    emit http://1.2.3.4/index.js:14
    _signIn http://1.2.3.4/index.js:163
    (Асинхронный: promise callback)
    _signIn http://1.2.3.4/index.js:163
    c http://1.2.3.4/index.js:163
    emit http://1.2.3.4/index.js:14
    emit http://1.2.3.4/index.js:14
    _open http://1.2.3.4/index.js:33
    (Асинхронный: promise callback)
    _open http://1.2.3.4/index.js:33
    exports http://1.2.3.4/index.js:33
    _open http://1.2.3.4/index.js:33
    exports http://1.2.3.4/index.js:33
    _open http://1.2.3.4/index.js:33
    a http://1.2.3.4/index.js:33
    open http://1.2.3.4/index.js:33
    be http://1.2.3.4/index.js:167
    [1993]< http://1.2.3.4/index.js:167
    o http://1.2.3.4/index.js:1
    o http://1.2.3.4/index.js:1
    [1944]< http://1.2.3.4/index.js:167
    o http://1.2.3.4/index.js:1
    o http://1.2.3.4/index.js:1
    [2015]< http://1.2.3.4/index.js:167
    o http://1.2.3.4/index.js:1
    e http://1.2.3.4/index.js:1
    <анонимный> http://1.2.3.4/index.js:1

[DustinB]

@Tristis-Oris That is what it definitely did in the past (can't say for sure as to when). I suspect this has to do with Internet Explorer being killed off (due to compatibility issues) and Edge taking its place.

Actually I was just able to confirm this. @danp happened to reach out and suggested I try this registry edit, which in fact did fix the issue, https://gist.github.com/jeremyrsellars/364ea48ea067505037ef

Of course, having to make edits to each or multiple workstations kind of sucks.