polle@feddit.org 6 days ago
I didn’t believe it until i verified it. This shit is true. Wtf! techcommunity.microsoft.com/blog/…/4390893
polle@feddit.org 6 days ago
I didn’t believe it until i verified it. This shit is true. Wtf! techcommunity.microsoft.com/blog/…/4390893
LifeInMultipleChoice@lemmy.world 6 days ago
Am I reading that wrong or is it just saying the Windows Store version (which was terrible) is going away. It tells you to use the normal remote desktop function that has existed in Windows until they put that new stupidly named app in the Store.
So if you run rdp.exe it should function as normal. The mstsc.exe was just a stupid interface saved in your user profile.
People should just be able to create their RDP shortcuts as normal and go on with their day by simply ignoring the Microsoft store like most enterprise users have been trying to do all along.
Though I could be wrong, I don’t have a windows computer around me to try it on at the moment. I moved my machines at home to different flavors of Linux when I didn’t want to figure out comparability work around for 11
Pilterlisky@sh.itjust.works 6 days ago
I actually just deployed this out at my company and Windows App (or the non Windows Store Remote Desktop App) is required to access AVD and W365 devices. Windows RDP is still present and works for accessing domain joined Windows devices, and both Windows App and Remote Desktop have that functionality as well.
LifeInMultipleChoice@lemmy.world 6 days ago
I wonder if that has to do with them trying to integrate access for zero client type setups. If 20 people are remoted into a VM setup but they all are coming from the same rack, the IP/Hostname would be the same in theory, so if you try to RDP to it, the protocol doesn’t work properly, it would want to kick all the other users off their instances to let them sign in. Been a bit since I’ve had tonl manage virtual instances though, so maybe I’m forgetting something.