- #CONFIGURE GATEWAY ON MICROSOFT REMOTE DESKTOP FOR MAC FULL#
- #CONFIGURE GATEWAY ON MICROSOFT REMOTE DESKTOP FOR MAC WINDOWS 10#
- #CONFIGURE GATEWAY ON MICROSOFT REMOTE DESKTOP FOR MAC PC#
- #CONFIGURE GATEWAY ON MICROSOFT REMOTE DESKTOP FOR MAC MAC#
- #CONFIGURE GATEWAY ON MICROSOFT REMOTE DESKTOP FOR MAC WINDOWS#
#CONFIGURE GATEWAY ON MICROSOFT REMOTE DESKTOP FOR MAC PC#
There is an option on the new Remote desktop client to configure a gateway, but it looks like that only links to PC and you cannot add a gateway to the workspace. Please note for testing the RDWebserver does not have a gateway installed on it, and uses the active gateway. I am a little confused why it works for the RDweb page but not the workspace discover as these are the same server. It looks like the server\RDweb\feed\ feeddiscovery.aspx is not giving the gateway information. What looks to be happening is that its not using the gateway and tries to connect directly to the VDI on port 3389. I can setup the workspace but it fails to connect to the internal VDI. If I setup a workspace on the new remote desktop client.
This connect to the gateway and then to the internal vdi. Connect externally using the Webpage or old Remote desktop client.
#CONFIGURE GATEWAY ON MICROSOFT REMOTE DESKTOP FOR MAC WINDOWS#
Windows 2016 RDS servers, with 2016 Webserver and gateway servers.Įverything works internally you can logon to the webpage and connect to the VDI or setup a workspace and connect to the VDI. I am trying to work out if this is a bug or a configuration issue. There have a version for on premise now but I cannot get it working externally. You can see my other article where I discuss that it was only for Azure before. This is a new client that was release around Feb. I believe you can tell the difference by their version number.
There does seem to be two version of the remote desktop client, one for Azure and one for on premise. But this is macos limitation.It looks like Microsoft has developed the new Remote Desktop Client to work on premises now.
#CONFIGURE GATEWAY ON MICROSOFT REMOTE DESKTOP FOR MAC FULL#
Also annoying is that control left/right arrow to move cursor is not possible as macos intercepts it for switching between full screen apps. No stars off from this, but it would be nice if modifier key remapping was possible, as control/option/start button/alt are in annoying places. Probably also due to the scaling is image being blurry in some cases. 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).
#CONFIGURE GATEWAY ON MICROSOFT REMOTE DESKTOP FOR MAC 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.
#CONFIGURE GATEWAY ON MICROSOFT REMOTE DESKTOP FOR MAC MAC#
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.
0 kommentar(er)
