Forum Discussion

DavidBelanger's avatar
DavidBelanger
Icon for Microsoft rankMicrosoft
Nov 12, 2019

Version 1.2.341 of the Windows client now available to all users.

We have just released version 1.2.431 to all users which includes the new 32-bit and ARM64 versions.   Additional information is available on the What's new page: https://docs.microsoft.com/en-us...
Naudski's avatar
Naudski
Copper Contributor
Nov 14, 2019
I just installed version 1.2.247 and my remote desktop connection to my on-prem RDSH through ADFS is working again 🙂
RussellSUK: Thank you for the MSI!

Can you explain why this isn't working anymore with this new client?
  • RussellSUK's avatar
    RussellSUK
    Copper Contributor
    Nov 14, 2019

    Naudski great stuff - glad it helped

     

    I suspect something is wrong in the way 1.2.341 reads the RDP file (we have skimmed almost everything out of one including the code signing and it still fails)

     

    We are going to test again and send the ETLs over to see if it can be debugged

     

    There is a reg key in the documentation to prevent updating, but the UI still prompts that an update is available!? (the reg key hides the button). If you have restricted users and use machine wide installer a user cannot install the update without admin credentials

     

    You can stop the UI appearing if you dont need it by renaming msrdcw.exe to msrdcw.old (msrdcw.exe invokes the MSRDC client window itself which offers shortcuts/RDP links and the update button)

     

    Russell

    • DavidBelanger's avatar
      DavidBelanger
      Icon for Microsoft rankMicrosoft
      Nov 14, 2019

      Hi RussellSUK , thank you for mentioning that the update notification still shows even if the key is set. Definitely not supposed to be the case. We'll test it out and fix it as needed.

       

      Naudski Installing the agent on servers on-premise is not supported. You can only install the agent on servers running in Azure. I will follow up separately to understand what changed but I recommend you look at moving these workloads to Azure as soon as possible.

Resources