- Microsoft remote desktop for mac mtu full#
- Microsoft remote desktop for mac mtu windows 10#
- Microsoft remote desktop for mac mtu Pc#
Microsoft remote desktop for mac mtu full#
Sometimes DPI is messed up and Windows target shows massive fonts, but if I exit and re-enter full screen it will resolve.
I suspect this is the issue with the slowness, that both sides cannot agree consistently on DPI and resolution settings so there is a lot of scaling going on on both sides. Setting up resolution too a lot of manipulating with choosing "optimize for retina" vs. All 3 are using 4k resolution (at 4k though even Windows RDP client has some noticeable lag but nothing compared to macos RDP client).
Microsoft remote desktop for mac mtu windows 10#
Using Windows 10 RDP client to same Windows 10 target on same network is dramatically faster. Connecting to a local Windows 10 machine over 1 gbps Ethernet has very noticeable lag and low framerate. MacOS version works but has horrible peformance compared to the Windows version. 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.
Microsoft remote desktop for mac mtu Pc#
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 deleted all non Windows standard fonts (my company had a policy to add some corporate fonts) from registry hive "HKLM\software\microsoft\windows nt\currentversion\fonts" and it started working inmediately.Įven if the cause of registry corruption may be different for different users, procmon showed me what was wrong.I have a specific usage case - I work in a multiplatform environment in which I work on the Mac and on the PC. So I've examined a server with process monitor (procmon.exe) and noticed a lot of overflow errors related to registry "HKLM\software\microsoft\windows nt\currentversion\fonts". Only chance to get them back to normal was to overwrite the C:\WINDOWS\SYSTEM32\CONFIG\SOFTWARE registry from backup C:\WINDOWS\SYSTEM32\CONFIG\REGBACK\SOFTWARE (server has to be powered off), but that not always worked. Server works OK, services run normally and can connect remotely with powershell and WindowsAdminCentre and my usual remote tools. No way to get into safe mode: always black. VMware console is black, RDP connection is black and it even happened with a physical server (but only domain joined servers). I had a similar problem with Windows Servers (a mix from 2012 to 2019):
0 kommentar(er)
