Microsoft Remotefx For Mac

Remotefx 3d Windows 10
Microsoft Remotefx For Mac Computer
Microsoft Remotefx For Mac Free

RDP 8 and RemoteFX. The apps use RDP 8.0 and RemoteFX for high fidelity audio and graphics. The protocol automatically adjusts for client performance and network bandwidth. Given sufficient bandwidth and client resources, streaming of HD video with high definition audio is possible up to 30fps.

Microsoft RemoteFX is a Microsoft brand name that covers a set of technologies that enhance visual experience of the Microsoft-developed remote display protocol Remote Desktop Protocol (RDP).^[1] RemoteFX was first introduced in Windows Server 2008 R2 SP1 and is based on intellectual property that Microsoft acquired and continued to develop since acquiring Calista Technologies.^[2] It is a part of the overall Remote Desktop Services workload.

Jul 29, 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. May 27, 2020 Microsoft RemoteFX. RemoteFX is a set of protocols for Microsoft's Remote Desktop Protocol (RDP) that can be used to provide virtual Windows desktops over a local area network. A central Windows server hosts the virtual desktops. UNG for Mac UNG for Linux. Aug 26, 2020 Microsoft Q&A is the best place to get answers to all your technical questions on. (RemoteFX, ClearCodec, NSCodec, etc.). Microsoft Remote Desktop Mac Mouse. Mar 20, 2020 We're told to direct technical issues to this forum, but I'm unsure if it's monitored by Microsoft or it's just a community based support forum. There seems to be a few recent issues with Mac/RDP so we need a bit of guidance if it's a Mac issue, an RDP issue,.

History[edit]

Windows Server 2008 R2 SP1[edit]

RemoteFX components introduced in Windows Server 2008 R2 SP1 include:

RemoteFX vGPU: the ability to present a virtualized instance of a physical GPU into multiple Windows 7 virtual machines. This provides VMs with access to the physical GPU, enabling hardware-acceleration for rich graphics scenarios such as 3D rendering and game play.
RemoteFX USB Redirection: generalized support for redirecting USB devices into Windows 7 VMs. This allows peripheral devices connected to thin client terminals to be used within virtual machines.^[3]^[4]
RemoteFX Codec (also referred to as RemoteFX Calista Codec): a lossy codec that is capable of preserving a high-fidelity experience for both video and text. The RemoteFX Codec does not require any special hardware, and uses the CPU for encoding.^[5]

Windows Server 2012[edit]

In Windows Server 2012, the following components were added to RemoteFX.^[6]

RemoteFX Adaptive Graphics: The RemoteFX graphics pipeline dynamically adapts to various runtime conditions, such as graphic content types, CPU and network bandwidth availability, and client rendering speed.^[7]
RemoteFX for WAN: a series of changes to the network transport pipeline to support UDP and ensure a fluid experience in both WAN and wireless network configurations.^[8]
RemoteFX Multi-Touch: supports remoting of gestures (e.g. pinch and zoom) between the client and host with up to 256 touch points^[9]
RemoteFX Media Redirection API: allows Voice over IP (VoIP) applications to natively integrate with RemoteFX, and enables transmission and rendering of audio and video content directly on the client side.^[10]
Choice of GPU: All RemoteFX features can be used with either a software-emulated GPU, which is available by default in all virtual machines and session hosts, or they can benefit from hardware acceleration when a physical video card is placed in the server and the RemoteFX vGPU is enabled.^[11]

In addition, the following components were updated:

RemoteFX vGPU: updated to support DirectX 11^[9]
RemoteFX USB Redirection: updated to support all desktop remoting scenarios vGPU-enabled virtual machines, traditional VMs, desktop sessions and physical desktop hosts^[9]
RemoteFX Codec (also referred to as RemoteFX Progressive Calista Codec): updated to include progressive rendering, which is more effective for rendering content over the WAN by sending images at full resolution only if bandwidth permits.^[12]

Windows Server 2016, Windows 10 Enterprise[edit]

In Windows Server 2016 (RDP 10), the following components were added to RemoteFX. ^[13]

OpenGL 4.4 and OpenCL 1.1 API support in a virtual machine with the RemoteFX adapter
More dedicated VRAM for the RemoteFX adapter
Various performance improvements in transport and API implementations

Remotefx 3d Windows 10

RemoteFX Media Streaming (H.264) replaced Multi Media Redirection (MMR). Note: MMR is now completely removed from RDP 10 given that RemoteFX Media Streaming works for all types of video content whereas MMR which just worked for some. ^[14]

Requirements[edit]

In Windows Server 2008 R2, the RemoteFX Codec could be leveraged for both session hosting (Remote Desktop Session Hosts) and VDI scenarios (and Remote Desktop Virtualization Hosts). The RemoteFX vGPU and RemoteFX USB Redirection features could only be used in VDI scenarios (Remote Desktop Virtualization Hosts).^[15]

Windows 10 version 1511 brings RemoteFX to client Hyper-V, removing dependency on Remote Desktop Services role.^[16]

Generation 2 VMs on Windows Server 2012 R2 do not support RemoteFX.^[17] Windows Server 2016 added such support.^[18]

In Windows Server 2012, all features of RemoteFX (with the exception of the vGPU) can be used with or without a physical GPU present in the server.^[19] When no GPU is present in the server, a synthetic software-emulated GPU is used to render content. When a GPU is present in the server, it can be used to hardware accelerate the graphics via the RemoteFX vGPU feature.

RemoteFX vGPU Requirements[edit]

The RemoteFX vGPU has the following requirements:^[20]

Hyper-V must be installed on the server. The VMs must be created and run using Hyper-V.
The server's CPU must support Second Level Address Translation (SLAT), and have it enabled.
For Windows Server 2008 R2 SP1, at least one DirectX 9.0c and 10.0 capable graphics card must be installed on the server.
For Windows Server 2012, at least one DirectX 11.0 capable graphics card with a WDDM 1.2 driver must be installed on the server.^[21]
The host machine must not be a Domain Controller. For single server configuration, Microsoft supports running Domain Controller as a Hyper-V virtual machine.^[22]

Windows Server 2008 R2 with SP1 has been tested for up to twelve virtual machines per GPU, for a total of twenty-four virtual machines on two physical GPUs.^[20]

Although any GPU meeting the above requirements will be capable of using RemoteFX, the Windows Server Catalog carries an additional qualification to further define the requirements for server-qualified GPUs. These specifications define GPUs configuration requirements and provide VM performance targets.^[23]Graphics cards that meet these are typically professional workstation products such as ATI/AMD's FirePro, v5800, v5900, v7800, v7900, v8800, v9800, and Nvidia's Quadro 2000, 3800, 4000, 4800, 5000, 5800, 6000, Quadro FX 2800M and 880M, QuadroPlex 7000 and Tesla M2070Q.^[24]

Servers running the RemoteFX vGPU need to accommodate such graphics cards with either larger power supplies and more PCIe slots^[25] or alternatively connect existing servers to an external PCIe expansion chassis.

Guest OS requirements[edit]

The RemoteFX virtual graphics adapter is only supported by Enterprise editions of Windows^[26], starting from Windows 7 SP1. Other editions are missing the required drivers to use the RemoteFX graphics adapter and will fall back to the default emulated graphics adapter instead.

References[edit]

^'Microsoft Announces New VDI Brand RemoteFX'. Redmond Channel Partner.
^'Explaining Microsoft RemoteFX'. Windows Virtualization Team Blog.
^'Introducing Microsoft RemoteFX USB Redirection: Part 2'. Microsoft Enterprise Mobility + Security Team.
^'Introducing Microsoft RemoteFX USB Redirection: Part 3'. Microsoft Enterprise Mobility + Security Team.
^'RemoteFX Codec'. Microsoft Protocol Specifications.
^'What's New in Windows Server 2012'. Remote Desktop Services Blog.
^'RemoteFX Adaptive Graphics in Windows Server 2012 and Windows 8'. Remote Desktop Services Blog.
^'RemoteFX for WAN: Overview of Intelligent and Adaptive Transports in Windows 8 and Windows Server 2012'. Remote Desktop Services Blog.
^ ^a^b^c'Windows Server 2012 Remote Desktop Services (RDS)'. Windows Server Blog.
^'Fast and fluid audio/video experience with the new Lync and RemoteFX'. Remote Desktop Services Blog.
^'Remote Desktop Services in Windows 8'. concurrency.com.
^'RemoteFX – Windows Server 2008 R2 vs. Windows Server 2012'. croftcomputers.wordpress.com.
^'RemoteFX vGPU Updates in Windows Server Next'. Retrieved 2016-09-15.
^'Remote Desktop Protocol (RDP) 10 AVC/H.264 improvements in Windows 10 and Windows Server 2016 Technical Preview'. Retrieved 2016-09-15.
^'Microsoft RemoteFX'. Microsoft Technet.
^'After 9 months of begging, it looks like RemoteFX is coming to client Hyper-V'. Reddit.
^'Generation 2 Virtual Machine Overview'. Microsoft Technet.
^'RemoteFX and vGPU Improvements in Windows Server 2016 Hyper-V'.
^'Delivering a Fast and Fluid User Experience on WAN RemoteFX in Windows Server 2012'. Remote Desktop Services Blog.
^ ^a^b'Hardware Considerations for RemoteFX'. Microsoft TechNet.
^'Your desktop will be a rich DX11-based experience, and your virtual GPU should be too'. Remote Desktop Services Blog.
^'New and existing RemoteFX-enabled virtual machines do not start on a domain controller that is running the Remote Desktop Virtualization Host service in Windows Server 2008 R2 Service Pack 1'.
^'RemoteFX Additional Qualifications'. Windows Server Catalog.
^'RemoteFX qualified video cards'. Windows Server Catalog.^{[dead link]}
^'Is That a Graphics Card in My Server?'. dcsblog.burtongroup.com.
^'RemoteFX vGPU Setup and Configuration Guide for Windows Server 2012'. Microsoft TechNet Wiki.

Retrieved from 'https://en.wikipedia.org/w/index.php?title=RemoteFX&oldid=945675553'

-->

Applies To: Windows 10, Windows 8.1, Windows Server 2012 R2, Windows Server 2016

You can use the Remote Desktop client for Mac to work with Windows apps, resources, and desktops from your Mac computer. Use the following information to get started - and check out the FAQ if you have questions.

Note

Curious about the new releases for the macOS client? Check out What's new for Remote Desktop on Mac?
The Mac client runs on computers running macOS 10.10 and newer.
The information in this article applies primarily to the full version of the Mac client - the version available in the Mac AppStore. Test-drive new features by downloading our preview app here: beta client release notes.

Get the Remote Desktop client

Follow these steps to get started with Remote Desktop on your Mac:

Download the Microsoft Remote Desktop client from the Mac App Store.
Set up your PC to accept remote connections. (If you skip this step, you can't connect to your PC.)
Add a Remote Desktop connection or a remote resource. You use a connection to connect directly to a Windows PC and a remote resource to use a RemoteApp program, session-based desktop, or a virtual desktop published on-premises using RemoteApp and Desktop Connections. This feature is typically available in corporate environments.

What about the Mac beta client?

We're testing new features on our preview channel on AppCenter. Want to check it out? Go to Microsoft Remote Desktop for Mac and select Download. You don't need to create an account or sign into AppCenter to download the beta client.

If you already have the client, you can check for updates to ensure you have the latest version. In the beta client, select Microsoft Remote Desktop Beta at the top, and then select Check for updates.

Add a workspace

Subscribe to the feed your admin gave you to get the list of managed resources available to you on your macOS device.

To subscribe to a feed:

Select Add feed on the main page to connect to the service and retrieve your resources.
Enter the feed URL. This can be a URL or email address:
- This URL is usually a Windows Virtual Desktop URL. Which one you use depends on which version of Windows Virtual Desktop you're using.
  - For Windows Virtual Desktop (classic), use https://rdweb.wvd.microsoft.com/api/feeddiscovery/webfeeddiscovery.aspx.
  - For Windows Virtual Desktop, use https://rdweb.wvd.microsoft.com/api/arm/feeddiscovery.
- To use email, enter your email address. This tells the client to search for a URL associated with your email address if your admin configured the server that way.
Select Subscribe.
Sign in with your user account when prompted.

After you've signed in, you should see a list of available resources.

Once you've subscribed to a feed, the feed's content will update automatically on a regular basis. Resources may be added, changed, or removed based on changes made by your administrator.

Export and import connections

You can export a remote desktop connection definition and use it on a different device. Remote desktops are saved in separate RDP files.

To export an RDP file:

In the Connection Center, right-click the remote desktop.
Select Export.
Browse to the location where you want to save the remote desktop RDP file.
Select OK.

To import an RDP file:

In the menu bar, select File > Import.
Browse to the RDP file.
Select Open.

Add a remote resource

Remote resources are RemoteApp programs, session-based desktops, and virtual desktops published using RemoteApp and Desktop Connections.

The URL displays the link to the RD Web Access server that gives you access to RemoteApp and Desktop Connections.
The configured RemoteApp and Desktop Connections are listed.

To add a remote resource:

In the Connection Center select +, and then select Add Remote Resources.
Enter information for the remote resource:
- Feed URL - The URL of the RD Web Access server. You can also enter your corporate email account in this field – this tells the client to search for the RD Web Access Server associated with your email address.
- User name - The user name to use for the RD Web Access server you are connecting to.
- Password - The password to use for the RD Web Access server you are connecting to.
Select Save.

The remote resources will be displayed in the Connection Center.

Connect to an RD Gateway to access internal assets

A Remote Desktop Gateway (RD Gateway) lets you connect to a remote computer on a corporate network from anywhere on the Internet. You can create and manage your gateways in the preferences of the app or while setting up a new desktop connection.

To set up a new gateway in preferences:

In the Connection Center, select Preferences > Gateways.
Select the + button at the bottom of the table Enter the following information:
- Server name – The name of the computer you want to use as a gateway. This can be a Windows computer name, an Internet domain name, or an IP address. You can also add port information to the server name (for example: RDGateway:443 or 10.0.0.1:443).
- User name - The user name and password to be used for the Remote Desktop gateway you are connecting to. You can also select Use connection credentials to use the same user name and password as those used for the remote desktop connection.

Manage your user accounts

When you connect to a desktop or remote resources, you can save the user accounts to select from again. You can manage your user accounts by using the Remote Desktop client.

To create a new user account:

In the Connection Center, select Settings > Accounts.
Select Add User Account.
Enter the following information:
- User Name - The name of the user to save for use with a remote connection. You can enter the user name in any of the following formats: user_name, domainuser_name, or user_name@domain.com.
- Password - The password for the user you specified. Every user account that you want to save to use for remote connections needs to have a password associated with it.
- Friendly Name - If you are using the same user account with different passwords, set a friendly name to distinguish those user accounts.
Select Save, then select Settings.

Customize your display resolution

You can specify the display resolution for the remote desktop session.

In the Connection Center, select Preferences.
Select Resolution.
Select +.
Enter a resolution height and width, and then select OK.

To delete the resolution, select it, and then select -.

Displays have separate spaces

Remotefx

If you're running Mac OS X 10.9 and have disabled Displays have separate spaces in Mavericks (System Preferences > Mission Control), you need to configure this setting in the Remote Desktop client using the same option.

Drive redirection for remote resources

Drive redirection is supported for remote resources, so that you can save files created with a remote application locally to your Mac. The redirected folder is always your home directory displayed as a network drive in the remote session.

Note

In order to use this feature, the administrator needs to set the appropriate settings on the server.

Use a keyboard in a remote session

Mac keyboard layouts differ from the Windows keyboard layouts.

The Command key on the Mac keyboard equals the Windows key.
To perform actions that use the Command button on the Mac, you will need to use the control button in Windows (for example Copy = Ctrl+C).
The function keys can be activated in the session by pressing additionally the FN key (for example, FN+F1).
The Alt key to the right of the space bar on the Mac keyboard equals the Alt Gr/right Alt key in Windows.

By default, the remote session will use the same keyboard locale as the OS you're running the client on. (If your Mac is running an en-us OS, that will be used for the remote sessions as well.) If the OS keyboard locale is not used, check the keyboard setting on the remote PC and change it manually. See the Remote Desktop Client FAQ for more information about keyboards and locales.

Support for Remote Desktop gateway pluggable authentication and authorization

Windows Server 2012 R2 introduced support for a new authentication method, Remote Desktop Gateway pluggable authentication and authorization, which provides more flexibility for custom authentication routines. You can now try this authentication model with the Mac client.

Important

Custom authentication and authorization models before Windows 8.1 aren't supported, although the article above discusses them.

To learn more about this feature, check out https://aka.ms/paa-sample.