So, as most users have seen, the “newer” Remote Desktop App in Windows ends support today…
The suggestion is to use the “Windows App” but it doesn’t work for us…says the system Admin hasn’t provided access to it yet. And it looks like Azure / Cloud only. Is that correct? Will this not work for local connections?
We can always fallback to the OG Remote Desktop Connection but a lot of our users got used to this new version.
My co-worker, on a Mac, can access our local servers with the Windows App but on Windows, it says we don’t have permission to use the app at all.
Was wondering if anyone else is migrating off of this and have tried the “Windows App”…we may just use OG RD or get them in via TeamViewer when they need to connect to another machine.
14 Spice ups
I recently asked my director about this very same thing. I don’t have access to our tenant so I’m not sure if local devices can be provisioned or not. I’ll be watching to see what others say because generically googling for that answer wasn’t as straightforward as I hoped it would be when I looked a few weeks ago. It’s another example of poorly done branding, too. Could they have used a more generic name?
2 Spice ups
I do not like the “Windows” app. I did some research and found a lot of options but I have been using and really like Devolutions Remote Desktop Manager. They have free and paid version.
5 Spice ups
The Windows App isn’t designed to work from a Windows PC to a remote Windows PC! The recommendation is to use RDP.
I have enjoyed the ability to have multiple PCs & Servers saved in the Remote Desktop App. The visual aspect is most appealing. I can save multiple connections in RDP, but it’s not the same.
4 Spice ups
Windows has a remote desktop connection manager (RCDMAN) that I absolutely swear by
Remote Desktop Connection Manager - Sysinternals | Microsoft Learn
7 Spice ups
