Microsoft Windows Desktop For Mac
With Microsoft Remote Desktop for Mac, you can connect to a remote PC and your work resources from almost anywhere. Experience the power of Windows with RemoteFX in a Remote Desktop client designed to help you get your work done wherever you are. Features and Highlights. Access to remote resources through the Remote Desktop Gateway. RELATED: How to Access Windows Remote Desktop Over the Internet. If you already have a Windows system, you could skip running Windows software on your Mac completely and use remote desktop software to access the Windows machine from your Mac’s desktop. Organizations with business software that runs on Windows can host Windows servers and make.
- Microsoft Windows Desktop Themes
- Microsoft Remote
- Microsoft Windows Desktop For Mac Pro
- Microsoft Remote Desktop
- Microsoft Remote Client
- Microsoft Desktop For Mac
Windows Virtual Desktop is a desktop and app virtualization service that runs on the cloud.
Here's what you can do when you run Windows Virtual Desktop on Azure:
- Set up a multi-session Windows 10 deployment that delivers a full Windows 10 with scalability
- Virtualize Office 365 ProPlus and optimize it to run in multi-user virtual scenarios
- Provide Windows 7 virtual desktops with free Extended Security Updates
- Bring your existing Remote Desktop Services (RDS) and Windows Server desktops and apps to any computer
- Virtualize both desktops and apps
- Manage Windows 10, Windows Server, and Windows 7 desktops and apps with a unified management experience
Introductory video
Learn about Windows Virtual Desktop, why it's unique, and what's new in this video:
Microsoft office 365 mac. Close the uninstall tool. Follow the remaining prompts.Select the steps for the version of Office you want to install or reinstall.
For more videos about Windows Virtual Desktop, see our playlist.
Key capabilities
With Windows Virtual Desktop, you can set up a scalable and flexible environment:
- Create a full desktop virtualization environment in your Azure subscription without having to run any additional gateway servers.
- Publish as many host pools as you need to accommodate your diverse workloads.
- Bring your own image for production workloads or test from the Azure Gallery.
- Reduce costs with pooled, multi-session resources. With the new Windows 10 Enterprise multi-session capability exclusive to Windows Virtual Desktop and Remote Desktop Session Host (RDSH) role on Windows Server, you can greatly reduce the number of virtual machines and operating system (OS) overhead while still providing the same resources to your users.
- Provide individual ownership through personal (persistent) desktops.
You can deploy and manage virtual desktops:
- Use the Windows Virtual Desktop PowerShell and REST interfaces to configure the host pools, create app groups, assign users, and publish resources.
- Publish full desktop or individual remote apps from a single host pool, create individual app groups for different sets of users, or even assign users to multiple app groups to reduce the number of images.
- As you manage your environment, use built-in delegated access to assign roles and collect diagnostics to understand various configuration or user errors.
- Use the new Diagnostics service to troubleshoot errors.
- Only manage the image and virtual machines, not the infrastructure. You don't need to personally manage the Remote Desktop roles like you do with Remote Desktop Services, just the virtual machines in your Azure subscription.
You can also assign and connect users to your virtual desktops:
- Once assigned, users can launch any Windows Virtual Desktop client to connect users to their published Windows desktops and applications. Connect from any device through either a native application on your device or the Windows Virtual Desktop HTML5 web client.
- Securely establish users through reverse connections to the service, so you never have to leave any inbound ports open.
Requirements
There are a few things you need to set up Windows Virtual Desktop and successfully connect your users to their Windows desktops and applications.
We plan to add support for the following OSes, so make sure you have the appropriate licenses for your users based on the desktop and apps you plan to deploy:
| OS | Required license |
|---|---|
| Windows 10 Enterprise multi-session or Windows 10 Enterprise | Microsoft 365 E3, E5, A3, A5, F1, Business Windows E3, E5, A3, A5 |
| Windows 7 Enterprise | Microsoft 365 E3, E5, A3, A5, F1, Business Windows E3, E5, A3, A5 |
| Windows Server 2012 R2, 2016, 2019 | RDS Client Access License (CAL) with Software Assurance |
Your infrastructure needs the following things to support Windows Virtual Desktop:
- An Azure Active Directory
- A Windows Server Active Directory in sync with Azure Active Directory. You can configure this with one of the following:
- Azure AD Connect (for hybrid organizations)
- Azure AD Domain Services (for hybrid or cloud organizations)
- An Azure subscription that contains a virtual network that either contains or is connected to the Windows Server Active Directory
The Azure virtual machines you create for Windows Virtual Desktop must be:
- Standard domain-joined or Hybrid AD-joined. Virtual machines can't be Azure AD-joined.
- Running one of the following supported OS images.
Note
If you need an Azure subscription, you can sign up for a one-month free trial. If you're using the free trial version of Azure, you should use Azure AD Domain Services to keep your Windows Server Active Directory in sync with Azure Active Directory.
The Azure virtual machines you create for Windows Virtual Desktop must have access to the following URLs:
| Address | Outbound TCP port | Purpose | Service Tag |
|---|---|---|---|
| *.wvd.microsoft.com | 443 | Service traffic | WindowsVirtualDesktop |
| mrsglobalsteus2prod.blob.core.windows.net | 443 | Agent and SXS stack updates | AzureCloud |
| *.core.windows.net | 443 | Agent traffic | AzureCloud |
| *.servicebus.windows.net | 443 | Agent traffic | AzureCloud |
| prod.warmpath.msftcloudes.com | 443 | Agent traffic | AzureCloud |
| catalogartifact.azureedge.net | 443 | Azure Marketplace | AzureCloud |
| kms.core.windows.net | 1688 | Windows activation | Internet |
Important
Opening these URLs is essential for a reliable Windows Virtual Desktop deployment. Blocking access to these URLs is unsupported and will affect service functionality. These URLs only correspond to Windows Virtual Desktop sites and resources, and don't include URLs for other services like Azure Active Directory.
The following table lists optional URLs that your Azure virtual machines can have access to:
| Address | Outbound TCP port | Purpose | Service Tag |
|---|---|---|---|
| *.microsoftonline.com | 443 | Authentication to MS Online Services | None |
| *.events.data.microsoft.com | 443 | Telemetry Service | None |
| www.msftconnecttest.com | 443 | Detects if the OS is connected to the internet | None |
| *.prod.do.dsp.mp.microsoft.com | 443 | Windows Update | None |
| login.windows.net | 443 | Login to MS Online Services, Office 365 | None |
| *.sfx.ms | 443 | Updates for OneDrive client software | None |
| *.digicert.com | 443 | Certificate revocation check | None |
Note
Windows Virtual Desktop currently doesn't have a list of IP address ranges that you can whitelist to allow network traffic. We only support whitelisting specific URLs at this time.
For a list of Office-related URLs, including required Azure Active Directory-related URLs, see Office 365 URLs and IP address ranges.
You must use the wildcard character (*) for URLs involving service traffic. If you prefer to not use * for agent-related traffic, here's how to find the URLs without wildcards:
- Register your virtual machines to the Windows Virtual Desktop host pool.
- Open Event viewer and navigate to Windows logs > Application > WVD-Agent and look for Event ID 3702.
- Whitelist the URLs that you find under Event ID 3702. The URLs under Event ID 3702 are region-specific. You'll need to repeat the whitelisting process with the relevant URLs for each region you want to deploy your virtual machines in.
Windows Virtual Desktop comprises the Windows desktops and apps you deliver to users and the management solution, which is hosted as a service on Azure by Microsoft. Desktops and apps can be deployed on virtual machines (VMs) in any Azure region, and the management solution and data for these VMs will reside in the United States. This may result in data transfer to the United States.
For optimal performance, make sure your network meets the following requirements:
- Round-trip (RTT) latency from the client's network to the Azure region where host pools have been deployed should be less than 150 ms.
- Network traffic may flow outside country/region borders when VMs that host desktops and apps connect to the management service.
- To optimize for network performance, we recommend that the session host's VMs are collocated in the same Azure region as the management service.
Supported Remote Desktop clients
The following Remote Desktop clients support Windows Virtual Desktop:
Important
Windows Virtual Desktop doesn't support the RemoteApp and Desktop Connections (RADC) client or the Remote Desktop Connection (MSTSC) client.
Important
Windows Virtual Desktop doesn't currently support the Remote Desktop client from the Windows Store. Support for this client will be added in a future release.
The Remote Desktop clients must have access to the following URLs:
| Address | Outbound TCP port | Purpose | Client(s) |
|---|---|---|---|
| *.wvd.microsoft.com | 443 | Service traffic | All |
| *.servicebus.windows.net | 443 | Troubleshooting data | All |
| go.microsoft.com | 443 | Microsoft FWLinks | All |
| aka.ms | 443 | Microsoft URL shortener | All |
| docs.microsoft.com | 443 | Documentation | All |
| privacy.microsoft.com | 443 | Privacy statement | All |
| query.prod.cms.rt.microsoft.com | 443 | Client updates | Windows Desktop |
Important
Opening these URLs is essential for a reliable client experience. Blocking access to these URLs is unsupported and will affect service functionality. These URLs only correspond to the client sites and resources, and don't include URLs for other services like Azure Active Directory.
Supported virtual machine OS images
Windows Virtual Desktop supports the following x64 operating system images:
- Windows 10 Enterprise multi-session, version 1809 or later
- Windows 10 Enterprise, version 1809 or later
- Windows 7 Enterprise
- Windows Server 2019
- Windows Server 2016
- Windows Server 2012 R2
Windows Virtual Desktop does not support x86 (32-bit), Windows 10 Enterprise N, or Windows 10 Enterprise KN operating system images. Windows 7 also doesn't support any VHD or VHDX-based profile solutions hosted on managed Azure Storage due to a sector size limitation.
Available automation and deployment options depend on which OS and version you choose, as shown in the following table:
| Operating system | Azure Image Gallery | Manual VM deployment | Azure Resource Manager template integration | Provision host pools on Azure Marketplace | Windows Virtual Desktop Agent updates |
|---|---|---|---|---|---|
| Windows 10 multi-session, version 1903 | Yes | Yes | Yes | Yes | Automatic |
| Windows 10 multi-session, version 1809 | Yes | Yes | No | No | Automatic |
| Windows 10 Enterprise, version 1903 | Yes | Yes | Yes | Yes | Automatic |
| Windows 10 Enterprise, version 1809 | Yes | Yes | No | No | Automatic |
| Windows 7 Enterprise | Yes | Yes | No | No | Manual |
| Windows Server 2019 | Yes | Yes | No | No | Automatic |
| Windows Server 2016 | Yes | Yes | Yes | Yes | Automatic |
| Windows Server 2012 R2 | Yes | Yes | No | No | Automatic |
Next steps
To get started, you'll need to create a tenant. To learn more about how to create a tenant, continue to the tenant creation tutorial.
-->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 user_name@domain.com.
- For Azure Active Directory (AAD) joined computers, use one of these formats: AzureADuser_name or AzureADuser_name@domain.com.
- 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.
Microsoft Windows Desktop Themes
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.
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 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.
- 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
Microsoft Remote
In order to use this feature, the administrator needs to set the appropriate settings on the server.
Microsoft Windows Desktop For Mac Pro
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
Microsoft office 2016 home and student for mac os. 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
Microsoft Remote Desktop
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.
Microsoft Remote Client
Tip
Microsoft Desktop For Mac
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.