Today's technology has come a long way in closing the divide between Windows and Mac applications, especially in the enterprise. However, a gap still exists for some and requires a bridge to move between computing environments.
For Mac users, the stalwart tool has been the Microsoft Remote Desktop connection. Available now through the Mac App store, it allows users to remotely connect to a Windows desktop to access local files, applications, and network resources.
Note: If you want to access Microsoft Remote Desktop on a newer Mac running macOS Sierra, check out this article instead.
In order to get started with Microsoft Remote Desktop, you must begin by downloading it from the Mac App Store. Click the blue 'App Store' icon in your dock. Or, you can download it from our sister site Download.com here.
Once you've accessed the Mac App Store, use the search bar at the top right of the screen to search for 'Microsoft Remote Desktop.' The first search result should be what you're looking for. To begin the download, click the blue 'Get' button. This app is free, so no price will be listed.
Microsoft Remote Deskop is an effective free tool for managing remote-desktop connections from a Mac. Perfect for those who travel frequently, or those who have a Mac/PC environment at work that. Hi, I installed the Remote Desktop Client App from the Appstore on my OS X 10.8 Lion. There was a very nice Feature 'Use All Monitors'. Since I have installed the Update of the Application under OS X 10.9 Mavericks, the Feature was removed. Parallels Client (formerly 2X RDP Client), when connected to Parallels Remote Application Server, provides secure access to business applications, virtual desktops, and data from your device.
Next, open the application by clicking through the grey 'Launchpad' icon and clicking on the Remote Desktop app icon. Or, you can use the searchlight feature by clicking the looking glass at the top right of your home screen, or by using the shortcut Command + Space Bar, and searching for 'Microsoft Remote Desktop.' Opening the app should look like this:
If you think you'll be frequently using this remote desktop connection, now would be a good time to set it in your dock. Right click (control + click) on the icon, mouse over 'Options,' and click 'Keep in Dock.' This will keep you from having to look for the icon every time you need to use it.
At this point you'll need to enable remote access on your target PC. For a Windows 8 machine, the fastest way to get this done is to search for 'Allow remote access to your computer' and click on that when it comes up. You may need an administrator password to complete this step. Under the 'System Properties' box you should see 'Remote Desktop' and the button labeled 'Allow remote connections to this computer' should be selected.
Next, you'll need to select the users who will be able to be accessed through the remote desktop connection. Now, search for 'System' and click it when it appears. Turn off hibernation and sleep settings for the target PC, as you won't be able to access it remotely if it falls asleep.
SEE: Software usage policy (Tech Pro Research)
While still in 'System,' it's a good time to go ahead and get your full PC name if you don't already have it, as you'll need it to set up the connection. Click on 'Computer name, domain, and workgroup settings' to find the full PC name and write it down. Enabling a Windows 7 computer is a little different, but you can find out how to do that here.
Head back to your Mac and click the 'New' button at the top left of the Microsoft Remote Desktop screen. You'll be prompted to fill in quite a few fields.
The first thing you'll need to input is the connection name. This is simply what you want to call the connection and it has no real bearing on the connection itself. For example, you could call it 'John's work computer,' or 'Jennifer's PC.'
Next, you'll need to input the PC name (the one you wrote down from earlier), or the IP address so your Mac knows where to find your PC. The next line down allows you to configure a Gateway, which would let you connect to virtual desktops or session-based desktops that are on your company's network. Check with your network administrator to see if there is a gateway you are to use.
Credentials is where you will type in the domain, username, and password for the target PC so you can log in through the remote connection. Resolution, colors, and full screen mode are all personal preferences for how you want the remote desktop to launch on your machine. If you're not sure, start with the standard settings and go from there.
If you want to configure peripheral devices for your remote desktop, you can find options for that under the middle tab, 'Session.'
The first choice is a drop-down menu for sound. You can disable sound, have it play on the remote PC, or have it play on your Mac. If you want to connect to an administrator session on a Windows server, click the box next to 'Connect to admin session.'
The next option to 'Forward printing devices' will make your local printers available during your remote desktop session. 'Swap mouse buttons' will allow you to use left click commands with a right-click Mac mouse.
The last tab at the top of the window is 'Redirection.' This is where you would choose a local folder you wanted to be available during your remote session. Click the '+' button, choose a name for the folder, and input the folder's path to have it available.
When you are finished configuring your remote desktop, click the red close button at the top left of the dialog box and your new remote desktop will be added. To start a session with that desktop, simply double-click it to begin.
If you want to edit, duplicate, export, or delete that remote connection, right-click (control + click) on the desktop name to access those options.
If you don't think Microsoft Remote Desktop is the option for you, here are some other options available at Download.com:
What do you think?
Is there a better way to access your Windows applications? Tell us in the comments.
Apple Weekly Newsletter
Whether you need iPhone and Mac tips or rundowns of enterprise-specific Apple news, we've got you covered. Delivered Tuesdays
Sign up today Sign up today
Also see
Windows has supported TLS for server authentication with RDP going back to Windows Server 2003 SP1. When connecting to a Windows PC, unless certificates have been configured, the remote PC presents a self-signed certificate, which results in a warning prompt from the Remote Desktop client. An environment with an enterprise certificate authority can enable certificate autoenrollment to enable trusted certificates on the RDP listener, thus removing the prompt. To get OS X clients to accept the certificate takes a little extra configuration not required on Windows clients.
While I may only be configuring certificates in my lab environment, there’s not much effort required to remove these certificate warnings.
Microsoft Rdp Client For MacClient Warnings for Untrusted Certificates
Here are the client certificate warnings on various Microsoft Remote Desktop clients, including OS X. First up the original Remote Desktop Connection (mstsc) on Windows:
The new Remote Desktop Universal app on Windows 10:
And the Remote Desktop client on OS X 10.11:
Configuring the Certificate Template
I won’t cover installing and configuring an enterprise certificate authority here; however, here are a number of articles worth reading on this topic:
To configure a certificate for use with Remote Desktop Services (or RDP into any Windows PC), you’ll need to create a new certificate template and enable both the Server Authentication and the Remote Desktop Authentication application policies. This was key for OS X clients - both of these policies must exist. Some articles will walk through this configuration and recommend removing the Server Authentication policy; however, the certificates will then not work on non-Windows clients.
This article has a great walk-through of the entire process and more: RDP TLS Certificate Deployment Using GPO. In my lab, I’ve created a ‘Remote Desktop Computer’ certificate template and enabled it to be autoenrolled via Group Policy.
Certificate Template Options
To create the new template, open the Certificate Templates console and duplicate the Computer template. Use this template because it already has the Server Authentication policy enabled.
Navigate to the Extensions tab, edit the ‘Application Policies’ extension and remove ‘Client Authentication’ from the list.
After you added the ‘Remote Desktop Authentication’ policy, you should see the policies and see in the following dialog box. See below for the actual ’Remote Desktop Authentication’ policy.
Adding the ’Remote Desktop Authentication’ policy requires adding a new extension named ‘Remote Desktop Authentication’ (or similar) with an object value of “1.3.6.1.4.1.311.54.1.2” (excluding quotes). and enter the values as above.
Save the template and configure your CA to issue the new template. In my lab my certificate template display name ‘Remote Desktop Computer’. Since my first template failed, it’s actually called ‘Remote Desktop Computer v2’. However, the important name to note for the next step is the actual template name, which can be found on the General tab of the template. In my case this is ‘RemoteDesktopComputerv2’ (the display name, minus the spaces).
Windows Rdp Client For LinuxConfigure Autorenrollment
To configure autoenrollment, I’ve created a new GPO dedicated to the autoenrollment setting and linked it to the organisational units containing server and workstation computer account objects. Edit the policy and enable the following setting:
Mac Rdp Windows 10
Computer Configuration / Administrative Templates / Windows Components / Remote Desktop Services / Remote Desktop Session Host / Security / Server authentication certificate template
Add the name of the certificate template and shown in the screenshot below:
Once a Group Poliy refresh occurs or on the next boot, the target Windows machines will autoenroll for the certificate and configure their RDP listener.
OS X Configuration
Now that my Remote Desktop certificates are configured for autoentrollment and Windows machines are picking up the certificates, I can import the root CA certificate into my MacBook running OS X.
Microsoft Rdp Client For Macintosh
Navigate to the URL of your certificate server (e.g. http://cert1/certsrv) and download the certificate via ‘Download a CA certificate, certificate chain, or CRL’. Download the CA certificate in DER format. Find the downloaded certificate in Finder and open the certificate to install it into Keychain.
Once installed the certificate is not automatically trused as you can see below:
Set the certificate to be trusted by selecting ‘Alway Trust’ from the ‘When using this certificate’ option. Close the certificate properties window and you should be prompted for your password to save the changes. Now when connecting to PCs via the Remote Desktop client, you should no longer receive certificate warnings.
Mac Rdp To Windows
This article shows how to install the root CA certificate via Terminal, which should assist in automating the import across a number of Macs.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |