Menu
2019-12-13 Windows 系统均自带了远程桌面功能,你不需要额外安装软件即可通过支持「RDP 协议」的工具对它们进行远程控制。微软官方的 Microsoft Remote Desktop 10 「微软远程桌面」 应用则是简单、安全、完全免费的好用神器!也是最值得推荐的远程控制软件首选。. On your local Windows 10 PC: In the search box on the taskbar, type Remote Desktop Connection, and then select Remote Desktop Connection.In Remote Desktop Connection, type the name of the PC you want to connect to (from Step 1), and then select Connect. On your Windows, Android, or iOS device: Open the Remote Desktop app (available for free from Microsoft Store, Google Play, and the Mac App. 2020-3-19 You can help protect yourself from scammers by verifying that the contact is a Microsoft Agent or Microsoft Employee and that the phone number is an official Microsoft global customer service number. Site Feedback. Remote Desktop License - Windows server 2012 R2. 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. 2017-3-8 Just migrated SBS 2011 server to 2012 R2 Essentials. Users, Anywhere Access and devices have been configured. Using the MS Remote Desktop (v8.0.37) app downloaded from the App Store, I can login as Admin, then RDP into Windows 7 Pro desktops. If I try to login with a regular user using domain. Ultimately this turned out to be a configuration issue.
-->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 click 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, click Microsoft Remote Desktop Beta at the top, and then click Check for updates.
Add a Remote Desktop connection
To create a remote desktop connection:
- In the Connection Center, click +, and then click Desktop.
- Enter the following information:
- PC name - the name of the computer.
- This can be a Windows computer name (found in the System settings), a domain name, or an IP address.
- You can also add port information to the end of this name, like MyDesktop:3389.
- User Account - Add the user account you use to access the remote PC.
- For Active Directory (AD) joined computers or local accounts, use one of these formats: user_name, domainuser_name, or [email protected].
- For Azure Active Directory (AAD) joined computers, use one of these formats: AzureADuser_name or [email protected].
- You can also choose whether to require a password.
- When managing multiple user accounts with the same user name, set a friendly name to differentiate the accounts.
- Manage your saved user accounts in the preferences of the app.
- PC name - the name of the computer.
- You can also set these optional settings for the connection:
- Set a friendly name
- Add a Gateway
- Set the sound output
- Swap mouse buttons
- Enable Admin Mode
- Redirect local folders into a remote session
- Forward local printers
- Forward Smart Cards
- Click Save.
To start the connection, just double-click it. The same is true for remote resources.
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.
- In the Connection Center, right-click the remote desktop.
- Click Export.
- Browse to the location where you want to save the remote desktop .RDP file.
- Click OK.
Use the following steps to import a remote desktop .RDP file.
- In the menu bar, click File > Import.
- Browse to the .RDP file.
- Click 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 click +, and then click 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.
- Click 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.
PowerPoint gives you templates to work from and the ability to edit your slides and presentations.Customise your presentations on the go, collaborating with others in real time. Pradumn Gupta, Tap with two finger to make iPad keyboard, a trackpad bug is really annoyingI am using Microsoft Powerpoint and word on my Apple iPad and i found a bug or you can say some problem in the application. Create, edit and share presentations with ease when you download Microsoft PowerPoint today.Present with confidence. Sync your PowerPoint documents via OneDrive, share with colleagues and create amazing presentations as a team.Get the complete Microsoft Office experience when you sign in with your Office 365 subscription. Never miss a beat with PowerPoint on the go. Microsoft powerpoint stopped working mac.
To set up a new gateway in preferences:
- In the Connection Center, click Preferences > Gateways.
- Click 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, click Settings > Accounts.
- Click 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 [email protected].
- 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.
- Tap Save, and then tap Settings.
Customize your display resolution
You can specify the display resolution for the remote desktop session.
- In the Connection Center, click Preferences.
- Click Resolution.
- Click +.
- Enter a resolution height and width, and then click OK.
To delete the resolution, select it, and then click -.
Displays have separate spacesIf you are running Mac OS X 10.9 and 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 (e.g.: Copy = Ctrl + C).
- The function keys can be activated in the session by pressing additionally the FN key (e.g.: 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 are not supported, although the article above discusses them.
To learn more about this feature, check out https://aka.ms/paa-sample.
Tip
Questions and comments are always welcome. However, please do NOT post a request for troubleshooting help by using the comment feature at the end of this article. Instead, go to the Remote Desktop client forum and start a new thread. Have a feature suggestion? Tell us in the client user voice forum.
-->Applies To: Windows Server 2016, Windows Server 2019
Microsoft Remote Desktop
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.
I don't care what they say they should have sent you an email within24-36 hours. Microsoft office 365 mac price.
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.
Way 1 – Uninstall Silverlight Manually. Quit all your browsers. Open the Finder → go to Macintosh HD → Library → Application Support → Microsoft and remove the PlayReady and Silverlight folders from there. Jan 23, 2020 Part 1: How To Manually Uninstall Silverlight on Mac Catalina. Step 1: Quit Chrome, Safari, Firefox or other browsers. Step 2: Open the Finder → go to Macintosh HD → Library → Application Support → Microsoft and remove the PlayReady and Silverlight folders. Step 3: Then go to the Internet. Mar 19, 2020 It's pretty easy to do a Spotlight Search to find Silverlight on your Mac. The Sliverlight.plugin file is the actual plug-in. Put that file into the trash, empty the trash, and Silverlight is no longer available to run on your Mac. How do i uninstall microsoft silverlight on my mac. To find out how to uninstall the following plug-ins. Uninstalling previous versions of Silverlight on Macintosh. Note: If you do not see any of the above installed on your computer, then you have not installed a previous version of Silverlight. Removing Silverlight plugins on Macintosh. Access your hard drive. Double-click the hard drive icon on your desktop. Find the plugin. Navigate to your Internet Plug-Ins directory: /Library/Internet Plug-Ins/. Remove the plugin. Drag any of the following into your trash bin: Silverlight.plugin.
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
Microsoft Remote Desktop 10 For Mac
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
Microsoft Remote Desktop Dmg
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
![Microsoft Remote Desktop Mac Windows Server 2012 Microsoft Remote Desktop Mac Windows Server 2012](/uploads/1/2/6/0/126069432/675607659.png)
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.
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
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.