Microsoft Remote Desktop Mac Slow
- Microsoft Remote Desktop Mac App
- Microsoft Remote Desktop Mac Slow Download
- Microsoft Remote Desktop Mac Very Slow
- Mac Microsoft Remote Desktop 12
We regularly update the Remote Desktop client for macOS, adding new features and fixing issues. Here's where you'll find the latest updates.
I'm using Remote Desktop for Mac on my base Retina MBP. Remote Desktop is incredibly slow for connecting to my Windows 7 PC. Download this app from Microsoft Store for Windows 10, Windows 8.1, Windows 10 Mobile, Windows Phone 8.1, Windows 10 Team (Surface Hub), HoloLens. See screenshots, read the latest customer reviews, and compare ratings for Microsoft Remote Desktop. 1 day ago Forum discussion: There are 2 computers that are the same make (lenovo) and model that are running very slow on remote desktop. These computers have Windows 10 (all updates), SSD, 32 GB of ram. Nov 27, 2017 Use Microsoft Remote Desktop for Mac to connect to a remote PC or virtual apps and desktops made available by your admin. With Microsoft Remote Desktop, you can be productive no matter where you are. GET STARTED Configure your PC for remote access using the information at https://aka.ms/rdsetup. Inside the Mac App Store, type 'Microsoft Remote Desktop' into the search bar at the top right hand portion of the window. The option you want is an orange icon with a computer monitor on it.
If you encounter any issues, you can always contact us by navigating to Help > Report an Issue.
Updates for version 10.3.9
Date published: 4/6/20
In this release we've made some changes to improve interoperability with the Windows Virtual Desktop service. In addition, we've included the following updates:
- Control+Option+Delete now triggers the Ctrl+Alt+Del sequence (previously required pressing the Fn key).
- Fixed the keyboard mode notification color scheme for Light mode.
- Addressed scenarios where connections initiated using the GatewayAccessToken RDP file property didn't work.
Note
This is the last release that will be compatible with macOS 10.12.
Updates for version 10.3.8
Date published: 2/12/20
It's time for our first release of 2020!
With this update, you can switch between Scancode (Ctrl+Command+K) and Unicode (Ctrl+Command+U) modes when entering keyboard input. Unicode mode allows extended characters to be typed using the Option key on a Mac keyboard. For example, on a US Mac keyboard, Option+2 will enter the trademark (™) symbol. You can also enter accented characters in Unicode mode. For example, on a US Mac keyboard, entering Option+E and the 'A' key at the same time will enter the character 'á' on your remote session.
Other updates in this release include:
- Cleaned up the workspace refresh experience and UI.
- Addressed a smart card redirection issue that caused the remote session to stop responding at the sign-in screen when the 'Checking Status' message appeared.
- Reduced time to create temporary files used for clipboard-based file copy and paste.
- Temporary files used for clipboard file copy and paste are now deleted automatically when you exit the app, instead of relying on macOS to delete them.
- PC bookmark actions are now rendered at the top-right corner of thumbnails.
- Made fixes to address issues reported through crash telemetry.
Updates for version 10.3.7
Date published: 1/6/20
In our final update of the year, we fine-tuned some code and fixed the following behaviors:
- Copying things from the remote session to a network share or USB drive no longer creates empty files.
- Specifying an empty password in a user account no longer causes a double certificate prompt.
Updates for version 10.3.6
Date published: 1/6/20
In this release, we addressed an issue that created zero-length files whenever you copied a folder from the remote session to the local machine using file copy and paste.
Updates for version 10.3.5
Date published: 1/6/20
We made this update with the help of everyone who reported issues. In this version, we've made the following changes:
- Redirected folders can now be marked as read-only to prevent their contents from being changed in the remote session.
- We addressed a 0x607 error that appeared when connecting using RPC over HTTPS RD Gateway scenarios.
- Fixed cases where users were double-prompted for credentials.
- Fixed cases where users received the certificate warning prompt twice.
- Added heuristics to improve trackpad-based scrolling.
- The client no longer shows the 'Saved Desktops' group if there are no user-created groups.
- Updated UI for the tiles in PC view.
- Fixes to address crashes sent to us via application telemetry.
Note
In this release, we now accept feedback for the Mac client only through UserVoice.
Updates for version 10.3.4
Date published: 11/18/19
We've been hard at work listening to your feedback and have put together a collection of bug fixes and feature updates.
- When connecting via an RD Gateway with multifactor authentication, the gateway connection will be held open to avoid multiple MFA prompts.
- All the client UI is now fully keyboard-accessible with Voiceover support.
- Files copied to the clipboard in the remote session are now only transferred when pasting to the local computer.
- URLs copied to the clipboard in the remote session now paste correctly to the local computer.
- Scale factor remoting to support Retina displays is now available for multimonitor scenarios.
- Addressed a compatibility issue with FreeRDP-based RD servers that was causing connectivity issues in redirection scenarios.
- Addressed smart card redirection compatibility with future releases of Windows 10.
- Addressed an issue specific to macOS 10.15 where the incorrect available space was reported for redirected folders.
- Published PC connections are represented with a new icon in the Workspaces tab.
- 'Feeds' are now called 'Workspaces,' and 'Desktops' are now called 'PCs.'
- Fixed inconsistencies and bugs in user account handling in the preferences UI.
- Lots of bug fixes to make things run smoother and more reliably.
Updates for version 10.3.3
Date published: 11/18/19
We've put together a feature update and fixed bugs for the 10.3.3 release.
First, we've added user defaults to disable smart card, clipboard, microphone, camera, and folder redirection:
- ClientSettings.DisableSmartcardRedirection
- ClientSettings.DisableClipboardRedirection
- ClientSettings.DisableMicrophoneRedirection
- ClientSettings.DisableCameraRedirection
- ClientSettings.DisableFolderRedirection
Next, the bug fixes:
- Resolved an issue that was causing programmatic session window resizes to not be detected.
- Fixed an issue where the session window contents appeared small when connecting in windowed mode (with dynamic display enabled).
- Addressed initial flicker that occurred when connecting to a session in windowed mode with dynamic display enabled.
- Fixed graphics mispaints that occurred when connected to Windows 7 after toggling fit-to-window with dynamic display enabled.
- Fixed a bug that caused an incorrect device name to be sent to the remote session (breaking licensing in some third-party apps).
- Resolved an issue where remote app windows would occupy an entire monitor when maximized.
- Addressed an issue where the access permissions UI appeared underneath local windows.
- Cleaned up some shutdown code to ensure the client closes more reliably.
Updates for version 10.3.2
Date published: 11/18/19
In this release, we fixed a bug that made the display low resolution while connecting to a session
Updates for version 10.3.1
Date published: 11/18/19
We've put together some fixes to address regressions that managed to sneak into the 10.3.0 release.
- Addressed connectivity issues with RD Gateway servers that were using 4096-bit asymmetric keys.
- Fixed a bug that caused the client to randomly stop responding when downloading feed resources.
- Fixed a bug that caused the client to crash while opening.
- Fixed a bug that caused the client to crash while importing connections from Remote Desktop, version 8.
Updates for version 10.3.0
Date published: 8/27/19
It's been a few weeks since we last updated, but we've been hard at work during that time. Version 10.3.0 brings some new features and lots of under-the-hood fixes.
- Camera redirection is now possible when connecting to Windows 10 1809, Windows Server 2019 and later.
- On Mojave and Catalina we've added a new dialog that requests your permission to use the microphone and camera for device redirection.
- The feed subscription flow has been rewritten to be simpler and faster.
- Clipboard redirection now includes the Rich Text Format (RTF).
- When entering your password you have the option to reveal it with a 'Show password' checkbox.
- Addressed scenarios where the session window was jumping between monitors.
- The Connection Center displays high resolution remote app icons (when available).
- Cmd+A maps to Ctrl+A when Mac clipboard shortcuts are being used.
- Cmd+R now refreshes all of your subscribed feeds.
- Added new secondary click options to expand or collapse all groups or feeds in the Connection Center.
- Added a new secondary click option to change the icon size in the Feeds tab of the Connection Center.
- A new, simplified, and clean app icon.
Updates for version 10.2.13
Date published: 5/8/2019
- Fixed a hang that occurred when connecting via an RD Gateway.
- Added a privacy notice to the 'Add Feed' dialog.
Updates for version 10.2.12
Date published: 4/16/2019
- Resolved random disconnects (with error code 0x904) that took place when connecting via an RD Gateway.
- Fixed a bug that caused the resolutions list in application preferences to be empty after installation.
- Fixed a bug that caused the client to crash if certain resolutions were added to the resolutions list.
- Addressed an ADAL authentication prompt loop when connecting to Windows Virtual Desktop deployments.
Updates for version 10.2.10
Date published: 3/30/2019
- In this release we addressed instability caused by the recent macOS 10.14.4 update. We also fixed mispaints that appeared when decoding AVC codec data encoded by a server using NVIDIA hardware.
Updates for version 10.2.9
Date published: 3/6/2019
- In this release we fixed an RD gateway connectivity issue that can occur when server redirection takes place.
- We also addressed an RD gateway regression caused by the 10.2.8 update.
Updates for version 10.2.8
Date published: 3/1/2019
- Resolved connectivity issues that surfaced when using an RD Gateway.
- Fixed incorrect certificate warnings that were displayed when connecting.
- Addressed some cases where the menu bar and dock would needlessly hide when launching remote apps.
- Reworked the clipboard redirection code to address crashes and hangs that have been plaguing some users.
- Fixed a bug that caused the Connection Center to needlessly scroll when launching a connection.
Updates for version 10.2.7
Date published: 2/6/2019
- In this release we addressed graphics mispaints (caused by a server encoding bug) that appeared when using AVC444 mode.
Updates for version 10.2.6
Date published: 1/28/2019
- Added support for the AVC (420 and 444) codec, available when connecting to current versions of Windows 10.
- In Fit to Window mode, a window refresh now occurs immediately after a resize to ensure that content is rendered at the correct interpolation level.
- Fixed a layout bug that caused feed headers to overlap for some users.
- Cleaned up the Application Preferences UI.
- Polished the Add/Edit Desktop UI.
- Made lots of fit and finish adjustments to the Connection Center tile and list views for desktops and feeds.
Note
There is a bug in macOS 10.14.0 and 10.14.1 that can cause the '.com.microsoft.rdc.application-data_SUPPORT/_EXTERNAL_DATA' folder (nested deep inside the ~/Library folder) to consume a large amount of disk space. To resolve this issue, delete the folder content and upgrade to macOS 10.14.2. Note that a side-effect of deleting the folder contents is that snapshot images assigned to bookmarks will be deleted. These images will be regenerated when reconnecting to the remote PC.
Updates for version 10.2.4
Date published: 12/18/2018
- Added dark mode support for macOS Mojave 10.14.
- An option to import from Microsoft Remote Desktop 8 now appears in the Connection Center if it is empty.
- Addressed folder redirection compatibility with some third-party enterprise applications.
- Resolved issues where users were getting a 0x30000069 Remote Desktop Gateway error due to security protocol fallback issues.
- Fixed progressive rendering issues some users were experiencing with fit to window mode.
- Fixed a bug that prevented file copy and paste from copying the latest version of a file.
- Improved mouse-based scrolling for small scroll deltas.
Updates for version 10.2.3
Date published: 11/06/2018
- Added support for the 'remoteapplicationcmdline' RDP file setting for remote app scenarios.
- The title of the session window now includes the name of the RDP file (and server name) when launched from an RDP file.
- Fixed reported RD gateway performance issues.
- Fixed reported RD gateway crashes.
- Fixed issues where the connection would hang when connecting through an RD gateway.
- Better handling of full-screen remote apps by intelligently hiding the menu bar and dock.
- Fixed scenarios where remote apps remained hidden after being launched.
- Addressed slow rendering updates when using 'Fit to Window' with hardware acceleration disabled.
- Handled database creation errors caused by incorrect permissions when the client starts up.
- Fixed an issue where the client was consistently crashing at launch and not starting for some users.
- Fixed a scenario where connections were incorrectly imported as full-screen from Remote Desktop 8.
Updates for version 10.2.2
Date published: 10/09/2018
- A brand new Connection Center that supports drag and drop, manual arrangement of desktops, resizable columns in list view mode, column-based sorting, and simpler group management.
- The Connection Center now remembers the last active pivot (Desktops or Feeds) when closing the app.
- The credential prompting UI and flows have been overhauled.
- RD Gateway feedback is now part of the connecting status UI.
- Settings import from the version 8 client has been improved.
- RDP files pointing to RemoteApp endpoints can now be imported into the Connection Center.
- Retina display optimizations for single monitor Remote Desktop scenarios.
- Support for specifying the graphics interpolation level (which affects blurriness) when not using Retina optimizations.
- 256-color support to enable connectivity to Windows 2000.
- Fixed clipping of the right and bottom edges of the screen when connecting to Windows 7, Windows Server 2008 R2 and earlier.
- Copying a local file into Outlook (running in a remote session) now adds the file as an attachment.
- Fixed an issue that was slowing down pasteboard-based file transfers if the files originated from a network share.
- Addressed a bug that was causing to Excel (running in a remote session) to hang when saving to a file on a redirected folder.
- Fixed an issue that was causing no free space to be reported for redirected folders.
- Fixed a bug that caused thumbnails to consume too much disk storage on macOS 10.14.
- Added support for enforcing RD Gateway device redirection policies.
- Fixed an issue that prevented session windows from closing when disconnecting from a connection using RD Gateway.
- If Network Level Authentication (NLA) is not enforced by the server, you will now be routed to the login screen if your password has expired.
- Fixed performance issues that surfaced when lots of data was being transferred over the network.
- Smart card redirection fixes.
- Support for all possible values of the 'EnableCredSspSupport' and 'Authentication Level' RDP file settings if the ClientSettings.EnforceCredSSPSupport user default key (in the com.microsoft.rdc.macos domain) is set to 0.
- Support for the 'Prompt for Credentials on Client' RDP file setting when NLA is not negotiated.
- Support for smart card-based login via smart card redirection at the Winlogon prompt when NLA is not negotiated.
- Fixed an issue that prevented downloading feed resources that have spaces in the URL.
Updates for version 10.2.1
Date published: 08/06/2018
- Enabled connectivity to Azure Active Directory (AAD) joined PCs. To connect to an AAD joined PC, your username must be in one of the following formats: 'AzureADuser' or 'AzureADuser@domain'.
- Addressed some bugs affecting the usage of smart cards in a remote session.
Updates for version 10.2.0
Date published: 07/24/2018
- Incorporated updates for GDPR compliance.
- MicrosoftAccountusername@domain is now accepted as a valid username.
- Clipboard sharing has been rewritten to be faster and support more formats.
- Copy and pasting text, images or files between sessions now bypasses the local machine's clipboard.
- You can now connect via an RD Gateway server with an untrusted certificate (if you accept the warning prompts).
- Metal hardware acceleration is now used (where supported) to speed up rendering and optimize battery usage.
- When using Metal hardware acceleration we try to work some magic to make the session graphics appear sharper.
- Got rid of some instances where windows would hang around after being closed.
- Fixed bugs that were preventing the launch of RemoteApp programs in some scenarios.
- Fixed an RD Gateway channel synchronization error that was resulting in 0x204 errors.
- The mouse cursor shape now updates correctly when moving out of a session or RemoteApp window.
- Fixed a folder redirection bug that was causing data loss when copy and pasting folders.
- Fixed a folder redirection issue that caused incorrect reporting of folder sizes.
- Fixed a regression that was preventing logging into an AAD-joined machine using a local account.
- Fixed bugs that were causing the session window contents to be clipped.
- Added support for RD endpoint certificates that contain elliptic-curve asymmetric keys.
- Fixed a bug that was preventing the download of managed resources in some scenarios.
- Addressed a clipping issue with the pinned connection center.
- Fixed the checkboxes in the Display tab of the Add a Desktop window to work better together.
- Aspect ratio locking is now disabled when dynamic display change is in effect.
- Addressed compatibility issues with F5 infrastructure.
- Updated handling of blank passwords to ensure the correct messages are shown at connect-time.
- Fixed mouse scrolling compatibility issues with MapInfra Pro.
- Fixed some alignment issues in the Connection Center when running on Mojave.
Updates for version 10.1.8
Date published: 05/04/2018
- Added support for changing the remote resolution by resizing the session window!
- Fixed scenarios where remote resource feed download would take an excessively long time.
- Resolved the 0x207 error that could occur when connecting to servers not patched with the CredSSP encryption oracle remediation update (CVE-2018-0886).
Updates for version 10.1.7
Date published: 04/05/2018
- Made security fixes to incorporate CredSSP encryption oracle remediation updates as described in CVE-2018-0886.
- Improved RemoteApp icon and mouse cursor rendering to address reported mispaints.
- Addressed issues where RemoteApp windows appeared behind the Connection Center.
- Fixed a problem that occurred when you edit local resources after importing from Remote Desktop 8.
- You can now start a connection by pressing ENTER on a desktop tile.
- When you're in full screen view, CMD+M now correctly maps to WIN+M.
- The Connection Center, Preferences, and About windows now respond to CMD+M.
- You can now start discovering feeds by pressing ENTER on the **Adding Remote Resources*- page.
- Fixed an issue where a new remote resources feed showed up empty in the Connection Center until after you refreshed.
Updates for version 10.1.6
Date published: 03/26/2018
- Fixed an issue where RemoteApp windows would reorder themselves.
- Resolved a bug that caused some RemoteApp windows to get stuck behind their parent window.
- Addressed a mouse pointer offset issue that affected some RemoteApp programs.
- Fixed an issue where starting a new connection gave focus to an existing session, instead of opening a new session window.
- We fixed an error with an error message - you'll see the correct message now if we can't find your gateway.
- The Quit shortcut (⌘ + Q) is now consistently shown in the UI.
- Improved the image quality when stretching in 'fit to window' mode.
- Fixed a regression that caused multiple instances of the home folder to show up in the remote session.
- Updated the default icon for desktop tiles.
This topic discusses how to select Remote Desktop Session Host (RD Session Host) hardware, tune the host, and tune applications.
In this topic:
Selecting the proper hardware for performance
For an RD Session Host server deployment, the choice of hardware is governed by the application set and how users use them. The key factors that affect the number of users and their experience are CPU, memory, disk, and graphics. This section contains additional guidelines that are specific to RD Session Host servers and is mostly related to the multi-user environment of RD Session Host servers.
CPU configuration
CPU configuration is conceptually determined by multiplying the required CPU to support a session by the number of sessions that the system is expected to support, while maintaining a buffer zone to handle temporary spikes. Multiple logical processors can help reduce abnormal CPU congestion situations, which are usually caused by a few overactive threads that are contained by a similar number of logical processors.
Therefore, the more logical processors on a system, the lower the cushion margin that must be built in to the CPU usage estimate, which results in a larger percentage of active load per CPU. One important factor to remember is that doubling the number of CPUs does not double CPU capacity.
Memory configuration
Memory configuration is dependent on the applications that users employ; however, the required amount of memory can be estimated by using the following formula: TotalMem = OSMem + SessionMem * NS
OSMem is how much memory the operating system requires to run (such as system binary images, data structures, and so on), SessionMem is how much memory processes running in one session require, and NS is the target number of active sessions. The amount of required memory for a session is mostly determined by the private memory reference set for applications and system processes that are running inside the session. Shared code or data pages have little effect because only one copy is present on the system.
One interesting observation (assuming the disk system that is backing up the page file does not change) is that the larger the number of concurrent active sessions the system plans to support, the bigger the per-session memory allocation must be. If the amount of memory that is allocated per session is not increased, the number of page faults that active sessions generate increases with the number of sessions. These faults eventually overwhelm the I/O subsystem. By increasing the amount of memory that is allocated per session, the probability of incurring page faults decreases, which helps reduce the overall rate of page faults.
Disk configuration
Storage is one of the most overlooked aspects when you configure RD Session Host servers, and it can be the most common limitation in systems that are deployed in the field.
The disk activity that is generated on a typical RD Session Host server affects the following areas:
System files and application binaries
Page files
User profiles and user data
Ideally, these areas should be backed up by distinct storage devices. Using striped RAID configurations or other types of high-performance storage further improves performance. We highly recommend that you use storage adapters with battery-backed write caching. Controllers with disk write caching offer improved support for synchronous write operations. Because all users have a separate hive, synchronous write operations are significantly more common on an RD Session Host server. Registry hives are periodically saved to disk by using synchronous write operations. To enable these optimizations, from the Disk Management console, open the Properties dialog box for the destination disk and, on the Policies tab, select the Enable write caching on the disk and Turn off Windows write-cache buffer flushing on the device check boxes.
Network configuration
Network usage for an RD Session Host server includes two main categories:
Microsoft Remote Desktop Mac App
RD Session Host connection traffic usage is determined almost exclusively by the drawing patterns that are exhibited by the applications running inside the sessions and the redirected devices I/O traffic.
For example, applications handling text processing and data input consume bandwidth of approximately 10 to 100 kilobits per second, whereas rich graphics and video playback cause significant increases in bandwidth usage.
Back-end connections such as roaming profiles, application access to file shares, database servers, e-mail servers, and HTTP servers.
The volume and profile of network traffic is specific to each deployment.
Tuning applications for Remote Desktop Session Host
Most of the CPU usage on an RD Session Host server is driven by apps. Desktop apps are usually optimized toward responsiveness with the goal of minimizing how long it takes an application to respond to a user request. However in a server environment, it is equally important to minimize the total amount of CPU usage that is needed to complete an action to avoid adversely affecting other sessions.
Consider the following suggestions when you configure apps that are to be used on an RD Session Host server:
Minimize background idle loop processing
Typical examples are disabling background grammar and spell check, data indexing for search, and background saves.
Minimize how often an app performs a state check or update.
Disabling such behaviors or increasing the interval between polling iterations and timer firing significantly benefits CPU usage because the effect of such activities is quickly amplified for many active sessions. Typical examples are connection status icons and status bar information updates.
Minimize resource contention between apps by reducing their synchronization frequency.
Examples of such resources include registry keys and configuration files. Examples of application components and features are status indicator (like shell notifications), background indexing or change monitoring, and offline synchronization.
Disable unnecessary processes that are registered to start with user sign-in or a session startup.
These processes can significantly contribute to the cost of CPU usage when creating a new user session, which generally is a CPU-intensive process, and it can be very expensive in morning scenarios. Use MsConfig.exe or MsInfo32.exe to obtain a list of processes that are started at user sign-in. For more detailed info, you can use Autoruns for Windows.
For memory consumption, you should consider the following:
Verify that DLLs loaded by an app are not relocated.
Relocated DLLs can be verified by selecting Process DLL view, as shown in the following figure, by using Process Explorer.
Here we can see that y.dll was relocated because x.dll already occupied its default base address and ASLR was not enabled
If DLLs are relocated, it is impossible to share their code across sessions, which significantly increases the footprint of a session. This is one of the most common memory-related performance issues on an RD Session Host server.
For common language runtime (CLR) applications, use Native Image Generator (Ngen.exe) to increase page sharing and reduce CPU overhead.
When possible, apply similar techniques to other similar execution engines.
Remote Desktop Session Host tuning parameters
Page file
Insufficient page file size can cause memory allocation failures in apps or system components. You can use the memory-to-committed bytes performance counter to monitor how much committed virtual memory is on the system.
Antivirus
Installing antivirus software on an RD Session Host server greatly affects overall system performance, especially CPU usage. We highly recommend that you exclude from the active monitoring list all the folders that hold temporary files, especially those that services and other system components generate.
Task Scheduler
Task Scheduler lets you examine the list of tasks that are scheduled for different events. For an RD Session Host server, it is useful to focus specifically on the tasks that are configured to run on idle, at user sign-in, or on session connect and disconnect. Because of the specifics of the deployment, many of these tasks might be unnecessary.
Desktop notification icons
Notification icons on the desktop can have fairly expensive refreshing mechanisms. You should disable any notifications by removing the component that registers them from the startup list or by changing the configuration on apps and system components to disable them. You can use Customize Notifications Icons to examine the list of notifications that are available on the server.
Remote Desktop Protocol data compression
Remote Desktop Protocol compression can be configured by using Group Policy under Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Remote Session Environment > Configure compression for RemoteFX data. Three values are possible:
Optimized to use less memory Consumes the least amount of memory per session but has the lowest compression ratio and therefore the highest bandwidth consumption.
Balances memory and network bandwidth Reduced bandwidth consumption while marginally increasing memory consumption (approximately 200 KB per session).
Microsoft word template location mac. Optimized to use less network bandwidth Further reduces network bandwidth usage at a cost of approximately 2 MB per session. If you want to use this setting, you should assess the maximum number of sessions and test to that level with this setting before you place the server in production.
You can also choose to not use a Remote Desktop Protocol compression algorithm, so we only recommend using it with a hardware device designed to optimize network traffic. Even if you choose not to use a compression algorithm, some graphics data will be compressed.
Device redirection
Device redirection can be configured by using Group Policy under Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection or by using the Session Collection properties box in Server Manager.
Generally, device redirection increases how much network bandwidth RD Session Host server connections use because data is exchanged between devices on the client computers and processes that are running in the server session. The extent of the increase is a function of the frequency of operations that are performed by the applications that are running on the server against the redirected devices.
Printer redirection and Plug and Play device redirection also increases CPU usage at sign-in. You can redirect printers in two ways:
Matching printer driver-based redirection when a driver for the printer must be installed on the server. Earlier releases of Windows Server used this method.
Introduced in Windows Server 2008, Easy Print printer driver redirection uses a common printer driver for all printers.
We recommend the Easy Print method because it causes less CPU usage for printer installation at connection time. The matching driver method causes increased CPU usage because it requires the spooler service to load different drivers. For bandwidth usage, Easy Print causes slightly increased network bandwidth usage, but not significant enough to offset the other performance, manageability, and reliability benefits.
Audio redirection causes a steady stream of network traffic. Audio redirection also enables users to run multimedia apps that typically have high CPU consumption.
Client experience settings
By default, Remote Desktop Connection (RDC) automatically chooses the right experience setting based on the suitability of the network connection between the server and client computers. We recommend that the RDC configuration remain at Detect connection quality automatically.
For advanced users, RDC provides control over a range of settings that influence network bandwidth performance for the Remote Desktop Services connection. You can access the following settings by using the Experience tab in Remote Desktop Connection or as settings in the RDP file.
The following settings apply when connecting to any computer:
Disable wallpaper (Disable wallpaper:i:0) Does not show desktop wallpaper on redirected connections. This setting can significantly reduce bandwidth usage if desktop wallpaper consists of an image or other content with significant costs for drawing.
Bitmap cache (Bitmapcachepersistenable:i:1) When this setting is enabled, it creates a client-side cache of bitmaps that are rendered in the session. It provides a significant improvement on bandwidth usage, and it should always be enabled (unless there are other security considerations).
Show contents of windows while dragging (Disable full window drag:i:1) When this setting is disabled, it reduces bandwidth by displaying only the window frame instead of all the content when the window is dragged.
Menu and window animation (Disable menu anims:i:1 and Disable cursor setting:i:1): When these settings are disabled, it reduces bandwidth by disabling animation on menus (such as fading) and cursors.
Font smoothing (Allow font smoothing:i:0) Controls ClearType font-rendering support. When connecting to computers running Windows 8 or Windows Server 2012 and above, enabling or disabling this setting does not have a significant impact on bandwidth usage. However, for computers running versions earlier than Windows 7 and Windows 2008 R2, enabling this setting affects network bandwidth consumption significantly.
The following settings only apply when connecting to computers running Windows 7 and earlier operating system versions:
Desktop composition This setting is supported only for a remote session to a computer running Windows 7 or Windows Server 2008 R2.
Visual styles (disable themes:i:1) When this setting is disabled, it reduces bandwidth by simplifying theme drawings that use the Classic theme.
By using the Experience tab within Remote Desktop Connection, you can choose your connection speed to influence network bandwidth performance. The following lists the options that are available to configure your connection speed:
Microsoft Remote Desktop Mac Slow Download
Detect connection quality automatically (Connection type:i:7) When this setting is enabled, Remote Desktop Connection automatically chooses settings that will result in optimal user experience based on connection quality. (This configuration is recommended when connecting to computers running Windows 8 or Windows Server 2012 and above).
Modem (56 Kbps) (Connection type:i:1) This setting enables persistent bitmap caching.
Low Speed Broadband (256 Kbps - 2 Mbps) (Connection type:i:2) This setting enables persistent bitmap caching and visual styles.
Cellular/Satellite (2Mbps - 16 Mbps with high latency) (Connection type:i:3) This setting enables desktop composition, persistent bitmap caching, visual styles, and desktop background.
High-speed broadband (2 Mbps – 10 Mbps ) (Connection type:i:4) This setting enables desktop composition, show contents of windows while dragging, menu and window animation, persistent bitmap caching, visual styles, and desktop background.
WAN (10 Mbps or higher with high latency) (Connection type:i:5) This setting enables desktop composition, show contents of windows while dragging, menu and window animation, persistent bitmap caching, visual styles, and desktop background.
LAN (10 Mbps or higher) (Connection type:i:6) This setting enables desktop composition, show contents of windows while dragging, menu and window animation, persistent bitmap caching, themes, and desktop background.
Microsoft Remote Desktop Mac Very Slow
Desktop Size
Mac Microsoft Remote Desktop 12
Desktop size for remote sessions can be controlled by using the Display tab in Remote Desktop Connection or by using the RDP configuration file (desktopwidth:i:1152 and desktopheight:i:864). The larger the desktop size, the greater the memory and bandwidth consumption that is associated with that session. The current maximum desktop size is 4096 x 2048.