-->
- Microsoft Remote Desktop Mac Reboot Windows 7
- Microsoft Remote Desktop
- Microsoft Remote Desktop Mac Os
- Microsoft Remote Desktop Mac Os X
- Microsoft Remote Desktop Mac Os X
Apr 04, 2016 Solution A - GUI + keyboard. Press Win+D to minimized all open Windows to show your desktop. (alternatively, you can left-click the lower-right corner) Press Alt+F4 to bring up the Shut Down Windows - What do you want the computer to do? Dialog, where you can now choose any of the following list. Apr 16, 2018 A black screen may appear while logon by using remote desktop Content provided by Microsoft Applies to: Microsoft Windows Server 2003 Enterprise Edition for Itanium-based Systems Microsoft Windows Server 2003 Enterprise Edition (32-bit x86) Microsoft Windows Server 2003 Datacenter Edition (32-bit x86) Microsoft Windows Server 2003 Standard. Dec 18, 2018 Microsoft Desktop Virtualization automatically detects device configurations and network conditions to get users up and running sooner by enabling the instant setup of corporate applications and desktops, and it equips IT to provide access to legacy applications during migration to Windows 10.
Applies to: Windows 10, Windows 8.1, Windows Server 2019, Windows Server 2016, Windows Server 2012 R2
Can i add mac to microsoft account. Now that you've set up the Remote Desktop client on your device (Android, Mac, iOS, or Windows), you may have questions. Here are answers to the most commonly asked questions about the Remote Desktop clients.
The majority of these questions apply to all of the clients, but there are a few client specific items.
If you have additional questions that you'd like us to answer, leave them as feedback on this article.
Setting up
Which PCs can I connect to?
Check out the supported configuration article for information about what PCs you can connect to.
How do I set up a PC for Remote Desktop?
I have my device set up, but I don't think the PC's ready. Help?
First, have you seen the Remote Desktop Setup Wizard? It walks you through getting your PC ready for remote access. Download and run that tool on your PC to get everything set.
Otherwise, if you prefer to do things manually, read on.
For Windows 10, do the following:
- On the device you want to connect to, open Settings.
- Select System and then Remote Desktop.
- Use the slider to enable Remote Desktop.
- In general, it's best to keep the PC awake and discoverable to facilitate connections. Click Show settings to go to the power settings for your PC, where you can change this setting.
Note
You can't connect to a PC that's asleep or hibernating, so make sure the settings for sleep and hibernation on the remote PC are set to Never. (Hibernation isn't available on all PCs.)
Make note of the name of this PC under How to connect to this PC. You'll need this to configure the clients.
You can grant permission for specific users to access this PC - to do that, click Select users that can remotely access this PC.Members of the Administrators group automatically have access.
For Windows 8.1, follow the instructions to allow remote connections in Connect to another desktop using Remote Desktop Connections.
Connection, gateway, and networks
Why can't I connect using Remote Desktop?
Here are some possible solutions to common problems you might encounter when trying to connect to a remote PC. If these solutions don't work, you can find more help on the Microsoft Community website.
The remote PC can't be found. Make sure you have the right PC name, and then check to see if you entered that name correctly. If you still can't connect, try using the IP address of the remote PC instead of the PC name.
There's a problem with the network. Make sure you have internet connection.
The Remote Desktop port might be blocked by a firewall. If you're using Windows Firewall, follow these steps:
Open Windows Firewall.
Click Allow an app or feature through Windows Firewall.
Click Change settings. You might be asked for an admin password or to confirm your choice.
Under Allowed apps and features, select Remote Desktop, and then tap or click OK.
If you're using a different firewall, make sure the port for Remote Desktop (usually 3389) is open.
Remote connections might not be set up on the remote PC. To fix this, scroll back up to How do I set up a PC for Remote Desktop? question in this topic.
The remote PC might only allow PCs to connect that have Network Level Authentication set up.
The remote PC might be turned off. You can't connect to a PC that's turned off, asleep, or hibernating, so make sure the settings for sleep and hibernation on the remote PC are set to Never (hibernation isn't available on all PCs.).
Why can't I find or connect to my PC?
Check the following:
Is the PC on and awake?
Did you enter the right name or IP address?
Important Microsoft planner app for mac os x.
Using the PC name requires your network to resolve the name correctly through DNS. In many home networks, you have to use the IP address instead of the host name to connect.
Is the PC on a different network? Did you configure the PC to let outside connections through? Check out Allow access to your PC from outside your network for help.
Are you connecting to a supported Windows version?
Note
Windows XP Home, Windows Media Center Edition, Windows Vista Home and Windows 7 Home or Starter are not supported without 3rd party software.
Why can't I sign in to a remote PC?
If you can see the sign-in screen of the remote PC but you can't sign in, you might not have been added to the Remote Desktop Users Group or to any group with administrator rights on the remote PC. Ask your system admin to do this for you.
Which connection methods are supported for company networks?
If you want to access your office desktop from outside your company network, your company must provide you with a means of remote access. The RD Client currently supports the following:
- Terminal Server Gateway or Remote Desktop Gateway
- Remote Desktop Web Access
- VPN (through iOS built-in VPN options)
VPN doesn't work
VPN issues can have several causes. The first step is to verify that the VPN works on the same network as your PC or Mac computer. If you can't test with a PC or Mac, you can try to access a company intranet web page with your device's browser.
Other things to check:
- The 3G network blocks or corrupts VPN. There are several 3G providers in the world who seem to block or corrupt 3G traffic. Verify VPN connectivity works correctly for over a minute.
- L2TP or PPTP VPNs. If you are using L2TP or PPTP in your VPN, please set Send All Traffic to ON in the VPN configuration.
- VPN is misconfigured. A misconfigured VPN server can be the reason why the VPN connections never worked or stopped working after some time. Ensure testing with the iOS device's web browser or a PC or Mac on the same network if this happens.
How can I test if VPN is working properly?
Verify that VPN is enabled on your device. You can test your VPN connection by going to a webpage on your internal network or using a web service which is only available via the VPN.
How do I configure L2TP or PPTP VPN connections?
If you are using L2TP or PPTP in your VPN, make sure to set Send all traffic to ON in the VPN configuration.
Web client
Which browsers can I use?
The web client supports Microsoft Edge, Internet Explorer 11, Mozilla Firefox (v55.0 and later), Safari, and Google Chrome.
Microsoft Remote Desktop Mac Reboot Windows 7
What PCs can I use to access the web client?
The web client supports Windows, macOS, Linux, and ChromeOS. Mobile devices are not supported at this time.
Can I use the web client in a Remote Desktop deployment without a gateway?
No. The client requires a Remote Desktop Gateway to connect. Don't know what that means? Ask your admin about it.
Does the Remote Desktop web client replace the Remote Desktop Web Access page?
No. The Remote Desktop web client is hosted at a different URL than the Remote Desktop Web Access page. You can use either the web client or the Web Access page to view the remote resources in a browser.
Can I embed the web client in another web page?
This feature is not supported at the moment.
Monitors, audio, and mouse
How do I use all of my monitors?
To use two or more screens, do the following:
- Right-click the remote desktop that you want to enable multiple screens for, and then click Edit.
- Enable Use all monitors and Full screen.
Is bi-directional sound supported?
Bi-directional sound can be configured in the Windows client on a per-connection basis. The relevant settings can be accessed in the Remote audio section of the Local Resources options tab.
What can I do if the sound won't play?
Sign out of the session (don't just disconnect, sign all the way out), and then sign in again.
Mac client - hardware questions
Is retina resolution supported?
Yes, the remote desktop client supports retina resolution.
How do I enable secondary right-click?
In order to make use of the right-click inside an open session you have three options:
- Standard PC two button USB mouse
- Apple Magic Mouse: To enable right-click, click System Preferences in the dock, click Mouse, and then enable Secondary click.
- Apple Magic Trackpad or MacBook Trackpad: To enable right-click, click System Preferences in the dock, click Mouse, and then enable Secondary click.
Is AirPrint supported?
No, the Remote Desktop client doesn't support AirPrint. (This is true for both Mac and iOS clients.)
Why do incorrect characters appear in the session?
If you are using an international keyboard, you might see an issue where the characters that appear in the session do match the characters you typed on the Mac keyboard.
This can occur in the following scenarios:
- You are using a keyboard that the remote session does not recognize. When Remote Desktop doesn't recognize the keyboard, it defaults to the language last used with the remote PC.
- You are connecting to a previously disconnected session on a remote PC and that remote PC uses a different keyboard language than the language you are currently trying to use.
You can fix this issue by manually setting the keyboard language for the remote session. See the steps in the next section.
How do language settings affect keyboards in a remote session?
There are many types of Mac keyboard layouts. Some of these are Mac specific layouts or custom layouts for which an exact match may not be available on the version of Windows you are remoting into. The remote session maps your keyboard to the best matching keyboard language available on the remote PC.
Microsoft Remote Desktop
If your Mac keyboard layout is set to the PC version of the language keyboard (for example, French – PC) all your keys should be mapped correctly and your keyboard should just work.
If your Mac keyboard layout is set to the Mac version of a keyboard (for example, French) the remote session will map you to the PC version of the French language. Some of the Mac keyboard shortcuts you are used to using on OSX will not work in the remote Windows session.
If your keyboard layout is set to a variation of a language (for example, Canadian-French) and if the remote session cannot map you to that exact variation, the remote session will map you to the closest language (for example, French). Some of the Mac keyboard shortcuts you are used to using on OSX will not work in the remote Windows session.
If your keyboard layout is set to a layout the remote session cannot match at all, your remote session will default to give you the language you last used with that PC. In this case, or in cases where you need to change the language of your remote session to match your Mac keyboard, you can manually set the keyboard language in the remote session to the language that is the closest match to the one you wish to use as follows.
Use the following instructions to change the keyboard layout inside the remote desktop session:
On Windows 10 or Windows 8:
- From inside the remote session, open Region and Language. Click Start > Settings > Time and Language. Open Region and Language.
- Add the language you want to use. Then close the Region and Language window.
- Now, in the remote session, you'll see the ability to switch between languages. (In the right side of the remote session, near the clock.) Click the language you want to switch to (such as Eng).
You might need to close and restart the application you are currently using for the keyboard changes to take effect.
Specific errors
Why do I get an 'Insufficient privileges' error?
You are not allowed to access the session you want to connect to. The most likely cause is that you are trying to connect to an admin session. Only administrators are allowed to connect to the console. Verify that the console switch is off in the advanced settings of the remote desktop. If this is not the source of the problem, please contact your system administrator for further assistance.
Why does the client say that there is no CAL?
When a remote desktop client connects to a Remote Desktop server, the server issues a Remote Desktop Services Client Access License (RDS CAL) stored by the client. Whenever the client connects again it will use its RDS CAL and the server will not issue another license. The server will issue another license if the RDS CAL on the device is missing or corrupt. When the maximum number of licensed devices is reached the server will not issue new RDS CALs. Contact your network administrator for assistance.
Why did I get an 'Access Denied' error?
The 'Access Denied' error is a generated by the Remote Desktop Gateway and the result of incorrect credentials during the connection attempt. Verify your username and password. If the connection worked before and the error occurred recently, you possibly changed your Windows user account password and haven't updated it yet in the remote desktop settings.
What does 'RPC Error 23014' or 'Error 0x59e6' mean?
In case of an RPC error 23014 or Error 0x59E6 try again after waiting a few minutes, the RD Gateway server has reached the maximum number of active connections. Depending on the Windows version running on the RD Gateway the maximum number of connections differs: The Windows Server 2008 R2 Standard implementation limits the number of connections to 250. The Windows Server 2008 R2 Foundation implementation limits the number of connections to 50. All other Windows implementations allow an unlimited number of connections.
What does the 'Failed to parse NTLM challenge' error mean?
This error is caused by a misconfiguration on the remote PC. Make sure the RDP security level setting on the remote PC is set to 'Client Compatible.' (Talk to your system admin if you need help doing this.)
What does 'TS_RAP You are not allowed to connect to the given host' mean?
This error happens when a Resource Authorization Policy on the gateway server stops your user name from connecting to the remote PC. This can happen in the following instances:
- The remote PC name is the same as the name of the gateway. Then, when you try to connect to the remote PC, the connection goes to the gateway instead, which you probably don't have permission to access. If you need to connect to the gateway, do not use the external gateway name as PC name. Instead use 'localhost' or the IP address (127.0.0.1), or the internal server name.
- Your user account isn't a member of the user group for remote access.
We regularly update the Remote Desktop client for macOS, adding new features and fixing issues. Here's where you'll find the latest updates.
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:
Today we share The latest Mac Microsoft Office 2019 v16.35 Multilingual Full version with Crack tools (Keygen, Patch, Serial number and Production key maker). Microsoft word for mac student.
- 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: Microsoft sql mac client.
- 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.
Microsoft Remote Desktop Mac Os
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
Microsoft Remote Desktop Mac Os X
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
Microsoft Remote Desktop Mac Os X
- 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.