Microsoft Remote Desktop Mac Beta

Getting Started

Because the mechanism of mac application, pevious versions of Microsoft Remote Desktop cannot be archived in Mac App Store. And the Remote Desktop 10 has ended supporting El Capitan, it is still suggested to find a way to upgrade the macOS to 10.12 or higher. If your macOS version is El Capitan, it means your Mac has at least 2GB of memory. Microsoft Remote Desktop Beta for Mac 是一款用于macOS系统远程连接windows桌面服务器的工具。可以帮你快速连接windows桌面，windows服务器。. What is Microsoft Remote Desktop Connection (RDC) 2.1.1? Microsoft Remote Desktop Connection (often abbreviated as 'RDC') is a simple tool to remotely view and control another computer. This software allows for a Mac running an Intel version of OSX to control a Windows PC. Download Microsoft Remote Desktop Connection (RDC) 2.1.1 for Mac.

To test beta versions of apps and App Clips using TestFlight, you’ll need to accept an email or public link invitation from the developer and have a device that you can use to test.

Members of the developer’s team can be given access to all builds of the app.

All other invited testers can access builds that the developer makes available to them. A developer can invite you to test with an email or a public link.

Required platforms

• iOS apps: iPhone, iPad, or iPod touch running iOS 8 or later. App Clips require iOS 14 or later. iMessage apps and sticker packs require iOS 10 or later.
• tvOS apps: Apple TV running tvOS 9 or later.
• watchOS apps: Apple Watch running watchOS 2 or later.

TestFlight is not available for Mac apps.

Available Languages

TestFlight for both iOS and tvOS is available in Arabic, Catalan, Chinese (simplified), Chinese (traditional), Croatian, Czech, Danish, Dutch, English (Australia), English (U.K.), English (U.S.), Finnish, French, French (Canada), German, Greek, Hebrew, Hindi, Hungarian, Indonesian, Italian, Japanese, Korean, Malaysian, Norwegian, Polish, Portuguese (Brazil), Portuguese (Portugal), Romanian, Russian, Slovak, Spanish, Spanish (Latin America), Swedish, Thai, Turkish, Ukrainian, and Vietnamese.

Installing and Testing Beta Apps

Each build is available to test for up to 90 days, starting from the day the developer uploads their build. You can see how many days you have left for testing under the app name in TestFlight. TestFlight will notify you each time a new build is available and will include instructions on what you need to test. Alternatively, with TestFlight 3 or later, you can turn on automatic updates to have the latest beta builds install automatically.

When the testing period is over, you'll no longer be able to open the beta build. To install the App Store version of the app, download or purchase the app from the App Store. In-app purchases are free only during beta testing, and any in-app purchases made during testing will not carry over to App Store versions.

Installation

To get started, install TestFlight on the device you’ll use for testing. Then, accept your email invitation or follow the public link invitation to install the beta app. You can install the beta app on up to 30 devices.

Installing a Beta iOS App via Email or Public Link Invitation

1. Install TestFlight on the iOS device that you’ll use for testing.
2. Open your invitation email or tap on the public link on your iOS device.
3. Tap View in TestFlight or Start Testing; or tap Install or Update for the app you want to test.

Installing a Beta tvOS App via Email Invitation

1. Install TestFlight on Apple TV.
2. Open your invitation email on a mobile device or computer.
3. Click or tap Start Testing. You'll be taken to a web page with a redemption code.
4. Open TestFlight on Apple TV.
5. Go to Redeem and enter the redemption code.

Installing a Beta tvOS App via Public Link Invitation

1. Install TestFlight on an iOS device and Apple TV where you can sign in to the same App Store account.
2. Tap the public link on your iOS device.
3. Tap Accept for the app you want to test.
4. Open TestFlight on Apple TV. You must be signed in to the same App Store account you used on your iOS device.
5. Install the app you want to test.

Installing a Beta watchOS App via Email or Public Link Invitation

1. Install TestFlight on the iOS device that you’ll use for testing.
2. Open your invitation email or tap on the public link on your iOS device.
3. Tap View in TestFlight or Start Testing.
4. If you're testing an app that’s for Apple Watch only, tap Install or Update from the Apps list.
5. If the app is an iOS app that includes an Apple Watch app, install the iOS app first, then from the App Details page under the Information section, you will see a Watch section. If the Apple Watch app is available and compatible with your watch, you’ll see a button to install it.

Testing

Testing iMessage Apps (iOS 10 or later)

1. Install TestFlight on the iOS device that you’ll use for testing.
2. Open your invitation email or tap on the public link on your iOS device.
3. Tap View in TestFlight or Start Testing; or tap Install or Update for the app you want to test.
4. If you’re testing an iOS app that includes an iMessage app, launch the beta app from the home screen as you would with any app.
5. If you’re testing an app that’s for iMessage only or a sticker pack, you can launch it from inside Messages.

Testing Beta App Clips (iOS 14 or later)

After accepting your email or public link invitation to test the app, you’ll see the option to test the App Clip in TestFlight. You can install either the app or the App Clip on your device (but not both at once), and can replace one with the other at any time. If the app is installed on your device, testing the App Clip will replace the app and some app data may be lost. You can reinstall the app by tapping Install on the app’s page in TestFlight.

1. Install TestFlight on the iOS device that you’ll use for testing.
2. Open your invitation email or tap on the public link on your iOS device.
3. Tap View in TestFlight or Start Testing; or tap Install or Update for the app you want to test.
4. Go to the app’s page in TestFlight.
5. In the App Clips section, tap TEST next to the beta App Clip you want to test.

Managing Automatic Updates

After installing TestFlight 3 or later, you’ll be prompted to turn on automatic updates. This allows the latest available beta builds to install automatically. TestFlight will notify you each time a new build is installed on your device. Automatic updates can be turned off at any time.

Change automatic update settings for all of the beta apps you’re testing using TestFlight:

Macos Remote Desktop

TestFlight for iOS

1. Open TestFlight and tap Settings in the upper-right corner.
2. Tap Automatic Updates.
3. Tap On or Off.

TestFlight for tvOS

1. Open TestFlight and click the Settings tab at the top.
2. Under GENERAL INFORMATION, turn Automatic Updates On or Off.

Change automatic update settings for individual beta apps you’re testing using TestFlight:

TestFlight for iOS

1. Open TestFlight and go to the app’s page.
2. Under App Information, turn Automatic Updates On or Off.

TestFlight for tvOS

1. Open TestFlight and go to the app’s page.
2. Under the app icon, click the More button.
3. Click Turn On Automatic Updates or Turn Off Automatic Updates.

Testing Previous Builds

When viewing an app in TestFlight, you'll see the latest available build by default. You can still test all other builds that are available to you.

1. Go to the app’s page in TestFlight.
2. Tap on Previous Builds.
3. Tap and install the build you want to test. The one you select will replace what’s currently installed.

If you already have the App Store version of the app installed on your device, the beta version of the app will replace it. After you download the beta app, you’ll see an orange dot next to its name that identifies it as a beta.

When you accept a TestFlight invitation through a public link, your name and email address are not visible to the developer. However, they’ll be able to see your number of sessions and crashes, the day you installed their app, and the latest installed version.

Giving Feedback

While testing a beta version of an app or App Clip, you can send the developer feedback about issues you experience or make suggestions for improvements based on the “What to Test” content. Feedback you submit through TestFlight is also provided to Apple as part of the TestFlight service.

iOS Apps

If your device is running iOS 13 or later, you can send feedback through the TestFlight app or directly from the beta app or beta App Clip by taking a screenshot, and you can report a crash after it occurs. If you were invited to test an app with a public link, you can choose not to provide your email address or other personal information to the developer. Apple will also receive all feedback you submit and will be able to tie it to your Apple ID.

Sending Feedback through the TestFlight App (iOS 13 or later)

1. Open the TestFlight app on your device.
2. From the Apps list, tap the app.
3. Tap Send Beta Feedback.
4. In the share dialog, tap Include Screenshot to choose a screenshot. If you don’t want to send an attachment, tap Don't Include Screenshot.
5. Add your comments (up to 2,000 characters), and optionally enter your email address if you were invited with a public link.
6. Tap Submit.

Sending Feedback through the Beta App (iOS 13 or later)

When you take a screenshot while testing a beta app or beta App Clip, you can send the screenshot with feedback directly to the developer without leaving the app or App Clip Experience. Developers can opt out of receiving this type of feedback, so this option is only available if the developer has it enabled.

1. Take a screenshot on your device. For details on how to take screenshots, see Take a screenshot on your iPhone, Take a screenshot on your iPad, and Take a screenshot on your iPod touch.
2. A thumbnail of your screenshot appears in the lower-left corner of your device. Tap the thumbnail and, if needed, add drawings and text with Markup. Then tap the Done button.
3. Tap the Share Beta Feedback.
4. Optionally, you can add comments (up to 2,000 characters), and your email address if you were invited with a public link.
5. Tap Submit.

Sending Crash Information (iOS 13 or later)

If you experience a crash while testing a beta app or beta App Clip, you’ll receive an alert asking if you want to send crash details to the developer through TestFlight. Developers can opt out of receiving this type of feedback, so this option is only available if the developer has it enabled.

When the crash alert displays, tap Share, add any additional comments, and tap Submit.

Sending Feedback through the TestFlight App (iOS 12.4 or earlier)

If your device is running iOS 12.4 or earlier, tap Send Beta Feedback to compose an email to the developer. The feedback email contains detailed information about the beta app and about your iOS device. You can also provide additional information, such as necessary screenshots and steps required to reproduce any issues. Your email address will be visible to the developer when you send email feedback through the TestFlight app even if you were invited through a public link.

Contacting the Developer

If you need to contact the developer while you’re testing their beta app for reasons other than feedback, you can view their email address. In TestFlight, go to the app’s page, go to the Information section, and tap App Details to view the developer’s email address.

tvOS Apps

To provide feedback on a tvOS app, open TestFlight, go to app’s page, go to the Information section to view the developer's email address, and send them an email. Provide as much information as you can, including screenshots and steps required to reproduce any issues you encountered. Please note that your email address will be visible to the developer when you send email feedback through TestFlight.

Opting Out from Testing

If you do not accept your email invitation, the beta app will not be installed and you will not be listed as a tester, and Apple will not take any action with respect to your email address. Additionally, you can unsubscribe using the link at the bottom of the invitation email to notify the developer that you’d like to be removed from their list. If you accepted the invitation and no longer wish to test the app, you can delete yourself as a tester in the app’s Information page in TestFlight by tapping Stop Testing.

Your Privacy and Data

When you test beta apps and beta App Clips with TestFlight, Apple will collect and send crash logs, your personal information such as name and email address, usage information, and any feedback you submit to the developer. Information that is emailed to the developer directly is not shared with Apple. The developer is permitted to use this information only to improve their App and is not permitted to share it with a third party. Apple may use this information to improve the TestFlight app.

Apple retains TestFlight data for one year. To view and manage your data with Apple, including your data that is sent to Apple through TestFlight, visit Data and Privacy. For more information about how the developer handles your data, consult their privacy policy. To request access to or deletion of your TestFlight data, you should contact the developer directly.

Information Shared by Using TestFlight

The following data is collected by Apple and shared with the developer when you use TestFlight. If you accepted an invitation through a public link only, your email address and name are not visible to the developer.

Data Shared When Sending Feedback (iOS only)

When you send feedback through TestFlight or send crashes or screenshots from the beta app, the following additional information is shared. If your device runs iOS 12.4 or earlier, this information is only shared with the developer. If your device runs iOS 13 or later, this information is collected by Apple and shared with developers. Apple retains the data for one year.

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:

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

What about the Mac beta client?

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

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

Add a workspace

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

To subscribe to a feed:

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

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

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

Export and import connections

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

To export an RDP file:

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

To import an RDP file:

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

Add a remote resource

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

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

To add a remote resource:

1. In the Connection Center select +, and then select Add Remote Resources.
2. 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.
3. Select Save.

The remote resources will be displayed in the Connection Center.

Connect to an RD Gateway to access internal assets

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

To set up a new gateway in preferences:

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

Manage your user accounts

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

To create a new user account:

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

Customize your display resolution

Microsoft Remote Desktop Mac Beta Software

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

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

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

Displays have separate spaces

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

Drive redirection for remote resources

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

Note

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

Use a keyboard in a remote session

Mac keyboard layouts differ from the Windows keyboard layouts.

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

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

Support for Remote Desktop gateway pluggable authentication and authorization

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

Important

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

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

Tip

Microsoft Remote Desktop For Mac Download

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.