My next issue happened with the newest update. Rebooting or flushing the network makes no difference. I can map my shared drive from my MAC using the hostname yet cannot connect to the hostname with this Microsoft Remote Desktop app running on my MAC. One day I can connect to the Windows 10 LAB via the hostname, the next I must use the IP address. Both MAC and Windows PC are on the same Local network and IP scheme. However, I do PC support from home and have a Windows 10 work LAB running. But recently migrated to MAC for personal use. I have used Microsoft from DOS days to Windows 11. Its good, but needs to fix these 2 issue to be great. Also, while I appreciate the option that allows the Apple key to be interchangable with ctrl for edit operations and find, it doesn't seem to work consistently, and as everyone who has ever switched back and forth between the Mac and Windows knows, confusion over which meta key to use in editing will eventually cause brain damage and is likely to send hardware on ballistic journeys through windows (not Windows). So properly-speaking, this probably a complaint about the service and not the client app, but the entire eco-system is failing me in small ways. Now, I'm sure there really IS such a way, but the internet is not my friend in helping me find it. Since there are some operations that cannot be performed via RDP - attaching to a VPN being one of them - it would be nice if I could just leave the PC logged in and operate it via Remote Desktop at the same time. This works reasonable well except that the Remote Desktop Service on the PC requires that I can only be logged in either via the Remote Desktop app OR the PC itself. I don't want to keep changing physical keyboards, so despite the fact that the two physical machines are next to eachother beneath my desk, I use remote desktop to view and operate the PC while working on the Mac. I have a specific usage case - I work in a multiplatform environment in which I work on the Mac and on the PC.

Rdp server for macos