- MICROSOFT REMOTE DESKTOP 8.0 MAC HOW TO
- MICROSOFT REMOTE DESKTOP 8.0 MAC FOR MAC
- MICROSOFT REMOTE DESKTOP 8.0 MAC UPDATE
- MICROSOFT REMOTE DESKTOP 8.0 MAC UPGRADE
- MICROSOFT REMOTE DESKTOP 8.0 MAC FULL
I'm not sure what else I can provide, but the TL DR is I upgraded the active Remote Desktop Connection Broker from 2012R2 to 2016, and after that, macs could not connect to any session host in the deployment, but PCs could connect fine. Once installed you can skip the first run experience. Next look for Microsoft Remote Desktop in the App Store to download the new application on your Mac running OS X Yosemite or higher.
MICROSOFT REMOTE DESKTOP 8.0 MAC HOW TO
I then saved a snapshot of the connection broker in it's 'upgraded to 2016' state and reverted back to the 2012r2 snapshot, after which, everyone, including mac users, could connect. How to migrate connection data from Microsoft Remote Desktop 8.0 Verify you have the latest version 8.0.43 installed to migrate your connection data. The other time it can come up is with macs, if you have the admin session box checked in the RDP app.Īfter a bit, it became apparent that only macs were having issues, which explained why I couldn't duplicate the issues even when connecting as users that were reporting issues. When everyone started coming in, there were a lot of issues though - Some getting the message 'The requested session access is denied', which is usually a damaged RDP file that's causing you to try to be connected to the session broker instead of a deployment server.
MICROSOFT REMOTE DESKTOP 8.0 MAC UPGRADE
I then tried to upgrade to 2016 instead of 2019, and while that also took forever, it succeeded, and once I had patched the 2016 connection broker to address the CredSSP issue, I was able to connect fine to several different collections. The other, currently inactive connection broker (you're supposed to remove all but one broker in a HA deployment and then do the in place upgrade) upgraded to 2019 without issue, although it took FOREVER. My Plan was to go from 2012R2 to 2019, then 2019 to 2022, however, one connection broker failed to upgrade to 2019, with the error after rollback indicating some sort of Sysprep issue. I appreciate the fact its free, easy to use and it has the ability to import or export the RDP files.I had previously tested upgrading a Remote Desktop installation from 2012R2 all the way to 2022 in a test sandbox environment, which all went well, so I planned to upgrade our production deployment.
MICROSOFT REMOTE DESKTOP 8.0 MAC UPDATE
So, I truly hope that these two issues get fixed in an update soon. I really hate this as it makes using multiple apps hard while connect. The issue sort of looks like I am using the old Microsoft magnifier app.
MICROSOFT REMOTE DESKTOP 8.0 MAC FULL
Once I am connected and use the fit to Window option and exit out of full screen mode to window mode, The desktop rather than stay at a scaled down version now blows up. 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. When I remote in from a PC, all works as expected. We use a cluster of 3 RDS servers that are load-balanced with round-robin DNS and an RD Gateway.
MICROSOFT REMOTE DESKTOP 8.0 MAC FOR MAC
But recently migrated to MAC for personal use. MS Remote Desktop for Mac (v8.0.9 - 8.0.12): issue with 'Session (ID ) remote control failed.' Hello, I'm a SysAdmin for a small-med business in CO. 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.
0 kommentar(er)
