So…yeah. Seems MS, in their endless wisdom has decided to rename their virtual desktop software, called before as “Remote Desktop” (and good luck trying to find issues with that that are not related to the old RDP tool MTSC.exe) to… “Windows App”. Perfect. Now everything will look like everything, and there’s no way to ever try to search for help for it. Next in line, I guess they can call it just “App”. I’m sure that will help everyone.
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.
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.