Microsoft Remote Desktop For Mac
Sherman Desrosiers
With Microsoft Remote Desktop clients, you can connect to Remote Desktop Services from Windows Server and remote PCs, and use and control desktops and apps that your admin has made available to you. There are clients available for many different types of devices on different platforms and form factors, such as desktops and laptops, tablets, smartphones, and through a web browser. Using your web browser on desktops and laptops, you can connect without having to download and install any software.
Some features are only available with certain clients, so it's important to check Compare the features of the Remote Desktop clients to understand the differences when connecting to Remote Desktop Services or remote PCs.
You can also use most versions of the Remote Desktop client to also connect to Azure Virtual Desktop, as well as to Remote Desktop Services in Windows Server or to a remote PC. If you want information on Azure Virtual Desktop instead, see Remote Desktop clients for Azure Virtual Desktop.
Here's a list of the Remote Desktop client apps and our documentation for connecting to Remote Desktop Services or remote PCs, where you can find download links, what's new, and learn how to install and use each client.
For the last couple days (since upgrading to macOS 12.4, although I don't know whether this is related) I can no longer copy and paste between my remote computer on Microsoft Remote Desktop and other macOS apps. The remote desktop and my Mac appear to be keeping separate clipboards.
In the version of Remote Desktop Web client (Version 1.0.27.0) used by the organization I remotely connect to, there are no options to enable or disable clipboard transfer. (In fact, there are no useful options for users at all!) PATHETIC
I'm trying to remote onto a Windows 2012 Server using Remote Desktop Connection for Mac. Using the same credentials, it works from my Windows PC (using Remote Desktop for Windows), but trying to do it from my Mac I get the error:
That's the ticket... if you check your version of remote desktop for mac it says it's up to date... you have to know that the new version of RDP for mac is called Microsoft Remote Desktop.... maddening!!
I doubt this a 'problem' with the mac as such nor does it have anything to do with Remote Desktop for Mac which is an entirely different product and for which this forum is for. Questions about RDC for Mac should be put on the relevant Microsoft forum rather than here. However your problem may be with your understanding of the secure remote connections requirements between your server and remote connections. I doubt you'd be aware of any of this as generally server administrators won't necessarily discuss them. By default a mac will not have server-client trust certificates installed simply because the exchange won't happen transparently between an MS based server and non MS-OS such as OS X.
You begin to solve the problem by asking your server administrator for the server's root certificate. He/she has to export this using the built-in tools. They should know how to do this? Once exported save it to a memory stick, insert it into your mac, double click on the .cer file and when prompted install it as a system keychain. On further prompts make sure you select 'Always Trust'. Launch RDC for Mac and you should be OK?
Thanks jaredfs. Im running Mac OS X Yosemite and just upgraded to Win10. I used to use the Remote Desktop Connection App but after the upgrade to Win10, I couldnt connect from my Mac. I installed Microsoft Remote Desktop and now I can connect to my Win 10 machine with no issues. Thanks for the quick fix!
So i HAVE been using CORD to log into my PCs from OSX. But it was not working on the Win10 box. I was in the insiders Beta program. and after some update CORD finaly started working. Well as said above, that was short lived with the next update CORD stopped working again. I can remote desktop in from a PC but not from CORD on my Mac.
So following the advice above i downloaded MICROSOFTS's remote desktop. and as soon as i tried to remote into my Win10 box, a message come up about generating a security certificate for this user. I said Yes, and boom! remote desktop ed in perfectly!
Sadly CORD (my preferred client) is still NOT working, but now we know WHY! Win 10 looks for this "security certificate" and if it doesnt find it Win10 will REFUSE the connection. This must be a PC to PC handshake that we never see.
Again the only lead I have is that Microsoft Remote Desktop app works on the original box, but not CORD. And i THINK this is due to a security certificate issue. Problem is I have not idea where to find that in Windows 10
I have had good success with Microsoft Remote Desktop, but one tecious process is setting up the connections. We have to do that manually. I did see the article about scripting this and deploying it via Policy:
-to-create-a-microsoft-remote-desktop-8-connection/
Being new to Jamf I'm not sure why that isn't working for me. I can create the script, set up the policy, get the policy to run without error, but the connection settings are not written to the plist file. Adding and editing connections manual works just fine.
looks like the script is expecting a username as parameter 8.
If I remember correctly all casper scripts insert the username in parameter 3.
If you want to use this with casper you are going to have to remove all the parameter checks or you are going to have to move them into the correct locations and actually have the option to assign them at run with casper remote.
Sorry for the late response, other projects sidelined this one for a few weeks. Thanks for the tips and help. I'll look into these options and report back what worked for us and anything else that may prove helpful for others.
Sorry for waking up an older thread, but have any of you found a way to do something similar with version 10? From what I've been able to find, they shifted to a sqlite database that is protected (technet comments).
It's good to revisit an issue every once in a while. Back in November, Microsoft introduced a new scripting feature for Remote Desktop. I get my app from the Mac App Store. It's version 10.2.4 from December 2018.
If you have detailed questions or need clarification for something, I encourage you to hop into MacAdmins Slack (signup) and join the #microsoft-rdc channel. Developers from Microsoft are interacting with us directly there and taking feedback.
In our environment we have task schedulers that run many Powershell scripts, one of those automated recurring scripts is one thats pulls down all our servers living in a specific OU in AD, and based on that creates a .RDP file with specific settings for every server. and when thats there, we can import al those .RDP files. You can schedule this so when a new server pop's up a new .RDP file is created.
@txhaflaire, for a large number of servers, you may be interested in the feed feature if you're not already using it. This was new to me a few months ago. It's possible to point to a URL to get a list of server connections. Just one place to maintain.
Thought I'd post our updated script. We have been using the excellent one that Steve Wood provided a few years ago now and with some help from the Slack Channel we've got app streaming working with MRD 10.
Jamf's purpose is to simplify work by helping organizations manage and secure an Apple experience that end users love and organizations trust. Jamf is the only company in the world that provides a complete management and security solution for an Apple-first environment that is enterprise secure, consumer simple and protects personal privacy. Learn about Jamf.
This site contains User Content submitted by Jamf Nation community members. Jamf does not review User Content submitted by members or other third parties before it is posted. All content on Jamf Nation is for informational purposes only. Information and posts may be out of date when you view them. Jamf is not responsible for, nor assumes any liability for any User Content or other third-party content appearing on Jamf Nation.
I've been working on this problem for 5 days, Google doesn't seem to be helping and that is surprising. Lack of posts on the topic made me believe it was a differnt issue than this router, however this morning I have conclusively proved the problem is the TL-ER5120 V3 router. It may be a simple setup or configuration issue, but frankly I can't find it/figure it out. Yes I've RTFM. Yes i've googled the problem endlessly. Yes I've tried random things, yes I reversed those that failed before moving on. Yes, i've rebooted the router multiple times. Yes, I have disabled everything in "firewall" section of router setup. Yes, I have above average networking knowledge and can usually figure out the problem, however networking and/or IT is NOT my day job so i'm far from expert.
Used RDP via that setup locally and remotely for years. Locally RDP is available 24/7/365, when out of town, port forwarded and opened a high numbered port (49XXX) and forwarded it to the local machine IP:port 3389. Both setups, local and remote, worked perfectly--never had a problem. Therefor, I suspected it wasn't a problem with Windows Settings.
My cable providers connection is however problematic, and connectivity as a whole will randomly drop for awhile. For more than one reason, I decided to upgrade to a multi-WAN connection, thus the purchase of the TL-ER5120. The other WAN provider is a metered "unlimited" cellular connection with a 22gb/month high speed cap (i.e.weird American "unlimited but limited" cellular broadband).
I initially attempted to just hang the R7000 as is on port 5, disabling DHCP on the 5120, hoping that the 5120 could be a "failover" router and I could just continue to use the Netgear R7000 as the local network router. That worked somewhat, but I had a few devices (camera's and a dedicated equipment controller) that just didn't get along with double NAT.
c80f0f1006