Microsoft Remote Desktop Mac Standalone

03.04.2020 admin

Mac Microsoft Remote Desktop 10
Mac Microsoft Remote Desktop Client
Remote Desktop Mac
Microsoft Remote Desktop Mac Standalone Download

Oct 22, 2019 Use Windows Server 2016 for your Remote Desktop infrastructure - the Web Access, Gateway, Connection Broker, and license server. Windows Server 2016 is backward compatible for these components - so a 2012 R2 RD Session Host can connect to a 2016 RD Connection Broker, but the reverse is not true. Nov 27, 2017 Scarica Microsoft Remote Desktop 10 per macOS 10.12 o versione successiva e comincia a usarlo sul tuo Mac. ‎Use Microsoft Remote Desktop for Mac to connect to a remote PC or virtual apps and desktops made available by your admin.

-->

This article describes an update for the Remote Desktop Protocol (RDP) 8.1 in Windows 7 Service Pack 1 (SP1) and Windows Server 2008 R2 SP1. This update package provides the following improvements: Fixes connection reliability issues.
Feb 13, 2020 Microsoft Remote Desktop for Mac is an application that allows connecting to virtual apps or another PC remotely. Discover the power of Windows with Remote Desktop designed to help you manage your work from any location over a network connection.
Jun 03, 2014 Two screens and Microsoft Remote Desktop. I have not run Remote Desktop in a while but I used to run it on dual screens under Mountain Lion.
MacAdmins asked and Microsoft answered: Microsoft Remote Desktop is now available standalone, outside of the Mac App Store. With the release of 10.1.6 today Microsoft Remote Desktop is now available as a standalone installer, perfect for MacAdmins to distribute as they do other packages without needing users to deal with the Mac App Store.

Applies To: Windows Server 2016, Windows Server 2019

When it comes to supported configurations for Remote Desktop Services environments, the largest concern tends to be version interoperability. Most environments include multiple versions of Windows Server - for example, you may have an existing Windows Server 2012 R2 RDS deployment but want to upgrade to Windows Server 2016 to take advantage of the new features (like support for OpenGLOpenCL, Discrete Device Assignment, or Storage Spaces Direct). The question then becomes, which RDS components can work with different versions and which need to be the same?

So with that in mind, here are basic guidelines for supported configurations of Remote Desktop Services in Windows Server.

Note

Make sure to review the system requirements for Windows Server 2016 and system requirements for Windows Server 2019.

Best practices

Use Windows Server 2019 for your Remote Desktop infrastructure (the Web Access, Gateway, Connection Broker, and license server). Windows Server 2019 is backward-compatible with these components, which means a Windows Server 2016 or Windows Server 2012 R2 RD Session Host can connect to a 2019 RD Connection Broker, but not the other way around.
For RD Session Hosts - all Session Hosts in a collection need to be at the same level, but you can have multiple collections. You can have a collection with Windows Server 2016 Session Hosts and one with Windows Server 2019 Session Hosts.
If you upgrade your RD Session Host to Windows Server 2019, also upgrade the license server. Remember that a 2019 license server can process CALs from all previous versions of Windows Server, down to Windows Server 2003.
Follow the upgrade order recommended in Upgrading your Remote Desktop Services environment.
If you are creating a highly available environment, all of your Connection Brokers need to be at the same OS level.

RD Connection Brokers

Windows Server 2016 removes the restriction for the number of Connection Brokers you can have in a deployment when using Remote Desktop Session Hosts (RDSH) and Remote Desktop Virtualization Hosts (RDVH) that also run Windows Server 2016. The following table shows which versions of RDS components work with the 2016 and 2012 R2 versions of the Connection Broker in a highly available deployment with three or more Connection Brokers.

3+ Connection Brokers in HA	RDSH or RDVH 2019	RDSH or RDVH 2016	RDSH or RDVH 2012 R2
Windows Server 2019 Connection Broker	Supported	Supported	Supported
Windows Server 2016 Connection Broker	N/A	Supported	Supported
Windows Server 2012 R2 Connection Broker	N/A	N/A	Not Supported

Support for graphics processing unit (GPU) acceleration

Remote Desktop Services support systems equipped with GPUs. Applications that require a GPU can be used over the remote connection. Additionally, GPU-accelerated rendering and encoding can be enabled for improved app performance and scalability.

Remote Desktop Services Session Hosts and single-session client operating systems can take advantage of the physical or virtual GPUs presented to the operating system in many ways, including the Azure GPU optimized virtual machine sizes, GPUs available to the physical RDSH server, RemoteFX vGPUs (Only on Windows Server 2016), and GPUs presented to the VMs by supported hypervisors.

See Which graphics virtualization technology is right for you? for help figuring out what you need. For specific information about DDA, check out Plan for deploying Discrete Device Assignment.

GPU vendors may have a separate licensing scheme for RDSH scenarios or restrict GPU use on the server OS, verify the requirements with your favorite vendor.

GPUs presented by a non-Microsoft hypervisor or Cloud Platform must have drivers digitally-signed by WHQL and supplied by the GPU vendor.

Remote Desktop Session Host support for GPUs

The following table shows the scenarios supported by different versions of RDSH hosts.

Feature	Windows Server 2008 R2	Windows Server 2012 R2	Windows Server 2016	Windows Server 2019
Use of hardware GPU for all RDP sessions	No	Yes	Yes	Yes
H.264/AVC hardware encoding (if suppported by the GPU)	No	No	Yes	Yes
Load balancing between multiple GPUs presented to the OS	No	No	No	Yes
H.264/AVC encoding optimizations for minimizing bandwidth usage	No	No	No	Yes
H.264/AVC support for 4K resolution	No	No	No	Yes

VDI support for GPUs

The following table shows support for GPU scenarios in the client OS.

Feature	Windows 7 SP1	Windows 8.1	Windows 10
Use of hardware GPU for all RDP sessions	No	Yes	Yes
H.264/AVC hardware encoding (if suppported by the GPU)	No	No	Windows 10 1703 and later
Load balancing between multiple GPUs presented to the OS	No	No	Windows 10 1803 and later
H.264/AVC encoding optimizations for minimizing bandwidth usage	No	No	Windows 10 1803 and later
H.264/AVC support for 4K resolution	No	No	Windows 10 1803 and later

RemoteFX 3D Video Adapter (vGPU) support

Remote Desktop Services supports RemoteFX vGPUs when VM is running as a Hyper-V guest on Windows Server 2012 R2 or Windows Server 2016. The following guest operating systems have RemoteFX vGPU support:

Windows 7 SP1
Windows 8.1
Windows 10 1703 or later
Windows Server 2016 in a single-session deployment only
Windows Server 2019 in a single-session deployment only

Discrete Device Assignment support

Remote Desktop Services supports Physical GPUs presented with Discrete Device Assignment from Windows Server 2016 or Windows Server 2019 Hyper-V hosts. See Plan for deploying Discrete Device Assignment for more details.

VDI deployment – supported guest OSes

Windows Server 2016 and Windows Server 2019 RD Virtualization Host servers support the following guest OSes:

Windows 10 Enterprise
Windows 8.1 Enterprise
Windows 7 SP1 Enterprise

Note

Remote Desktop Services doesn't support heterogeneous session collections. The OSes of all VMs in a collection must be the same version.
You can have separate homogeneous collections with different guest OS versions on the same host.
The Hyper-V host used to run VMs must be the same version as the Hyper-V host used to create the original VM templates.

Single sign-on

Windows Server 2016 and Windows Server 2019 RDS supports two main SSO experiences:

In-app (Remote Desktop application on Windows, iOS, Android, and Mac)
Web SSO

Using the Remote Desktop application, you can store credentials either as part of the connection info (Mac) or as part of managed accounts (iOS, Android, Windows) securely through the mechanisms unique to each OS. Microsoft office 2016 for mac launches for office 365 subscribers.

To connect to desktops and RemoteApps with SSO through the inbox Remote Desktop Connection client on Windows, you must connect to the RD Web page through Internet Explorer. The following configuration options are required on the server side. No other configurations are supported for Web SSO:

RD Web set to Forms-Based Authentication (Default)
RD Gateway set to Password Authentication (Default)
RDS Deployment set to 'Use RD Gateway credentials for remote computers' (Default) in the RD Gateway properties

Note

Due to the required configuration options, Web SSO is not supported with smartcards. Users who login via smartcards might face multiple prompts to login.

For more information about creating VDI deployment of Remote Desktop Services, check out Supported Windows 10 security configurations for Remote Desktop Services VDI.

Using Remote Desktop Services with application proxy services

Mac Microsoft Remote Desktop 10

You can use Remote Desktop Services, except for the web client, with Azure AD Application Proxy. Remote Desktop Services does not support using Web Application Proxy, which is included in Windows Server 2016 and earlier versions.

The following page(s) contain instructions on using Remote Desktop to connect to Faculty & Staff Windows computers on the UMKC campus (from off-campus). Your campus computer must be powered on to receive connections.

Mac Microsoft Remote Desktop Client

Don't know your computer name or don't know if your account has the correct permissions? Find out here. If you need assistance, please contact the IS Technology Support Center or your IT Liaison.

Please note: Before you attempt to connect to UMKC resources remotely, please make sure your operating system (Apple OS X) has all applicable security updates installed.
To connect to your campus Windows PC from a Mac you will need to use the Microsoft Remote Desktop application for Mac version 10.3.8 (or higher). If you are using a university-owned Mac, you may already have this app installed. Please contact the Technology Support Center or your IT Liaison if you have questions about using this software on a university-owned Mac.

Supported	Default Icon	Client Name
Microsoft RDP v10 Link to Download
Microsoft RDP v8
Apple RDC

Remote Desktop Mac

Mac OS X Remote Desktop Connection Instructions

Open the Microsoft Remote Desktop application
Click the '+' icon
Select PC
For PC Name, enter the name of the remote computer to connect to. Or check How to find my computer name
For User Account, click the dropdown to change the setting
Click Add User Account
For User Name, type UMKCusername@umsystem.edu in DomainUsername
For Password, type your UMKC Username Password. Note: you will need to update your Remote Desktop settings every time you change your UMKC Username password.
Click Save
For Friendly Name, enter the PC name
Click on no gateway to change the setting
Select Add Gateway from the dropdown
For Server Name, enter tsg.umkc.edu
For User Account, click Use PC User account
Select your UMKC username from the list
Click Add
Click Add again
To initiate the connection, double click on your PC Name tile
Click Show Certificate
Click Always Trust to prevent seeing this warning again for the PC specified
Click Continue