1. Microsoft Remote Desktop System Requirements Mac Os High Sierra
2. Microsoft Remote Desktop Mac Requirements
3. Microsoft Remote Desktop System Requirements Mac Os Mojave
4. Microsoft Remote Desktop 10 Mac Requirements
5. Microsoft Remote Desktop System Requirements Mac Os Catalina
6. Mac Microsoft Remote Desktop 12
7. Desktop System Info

-->

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

1. Hardware Requirements and Performance Recommendations.; 2 minutes to read; In this article. This topic describes the hardware that is required to run a MultiPoint Services system and support user application scenarios.
2. Manage Mac computers on your network with Apple Remote Desktop (ARD). Learn more with these resources.

Learn about Windows Virtual Desktop, why it's unique, and what's new in this video:

Nov 27, 2017  ‎Read reviews, compare customer ratings, see screenshots and learn more about Microsoft Remote Desktop 10. Download Microsoft Remote Desktop 10 for macOS 10.12 or later and enjoy it on your Mac. ‎Use Microsoft Remote Desktop for Mac to connect to a remote PC or virtual apps and desktops made available by your admin.

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

Microsoft Remote Desktop System Requirements Mac Os High Sierra

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.

Microsoft Remote Desktop Mac Requirements

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

Microsoft Remote Desktop System Requirements Mac Os Mojave

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:

1. Register your virtual machines to the Windows Virtual Desktop host pool.
2. Open Event viewer and navigate to Windows logs > Application > WVD-Agent and look for Event ID 3702.
3. 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.

-->

This topic describes the hardware that is required to run a MultiPoint Services system and support user application scenarios. The user scenario directly affects the CPU, RAM, and network bandwidth requirements.

Optimize MultiPoint Services system performance

The performance of your MultiPoint Services system will be directly affected by the capability of the CPU, the GPU, and the amount of RAM that is available on the computer that is running MultiPoint Services.

Microsoft Remote Desktop 10 Mac Requirements

Applications and Internet content

Because MultiPoint Services is a shared resource computing solution, the type and number of applications that are running on the stations can impact the performance of your MultiPoint Services system. It is important to consider the types of programs that are used regularly when you are planning your system. For example, a graphics-intensive application requires a more powerful computer than an application such as a word processor. Overloading the computer with graphics-intensive applications will likely cause lag problems throughout the entire system.

The type of content that is accessed by applications also affects the system's performance. If multiple stations are using web browsers to access multimedia content, such as full-motion video, fewer stations can be connected before adversely affecting the system performance. Conversely, if the multiple stations are using web browsers to access static web content, more stations can be connected without a significant effect on performance.

Hardware recommendations

To achieve good performance with your MultiPoint Services system under various loads, use the guidelines in the following table when you are planning and testing your system. These are the basic requirements forMultiPoint Services . The actual configuration sizing depends on your system configuration, the workload you are running, and the hardware capability. You should always validate by testing your applications and hardware.

Note

2C = 2 cores, 4C = 4 cores, 6C = 6 cores, MT = multithreading. Processor speed should be at least 2.0 gigahertz (GHz).

Minimum recommended hardware for running default MultiPoint Server stations

Application Scenario	Up to 5 Stations	6-8 Stations	9-12 Stations	13-16 Stations	17-20 Stations	21-24 Stations
Productivity Office, web browsing, line-of-business applications	CPU: 2C RAM: 2 GB	CPU: 2C RAM: 4 GB	CPU: 4C RAM: 6 GB	CPU: 4C RAM: 8 GB	CPU: 4C+MT or 6C RAM: 10 GB	CPU: 6C+MT RAM: 12 GB
Mixed Office, web browsing, line-of-business applications, and occasional video use by some users	CPU: 2C RAM: 2 GB	CPU: 2C RAM: 4 GB	CPU: 4C RAM: 6 GB	CPU: 4C+MT or 6C RAM: 8 GB	CPU: 6C+MT RAM: 10 GB	CPU: 6C+MT RAM: 12 GB
Video intensive Office, web browsing, line-of-business applications, and frequent video use by all users Note: Video testing was performed using 360p H.264 video at native resolution.	CPU: 4C+MT RAM: 2 GB	CPU: 6C+MT RAM: 4 GB	CPU: 8C+MT RAM: 6 GB	CPU: 12C+MT RAM: 8 GB	CPU: 16C+MT RAM: 10 GB - Thin Client: RemoteFX - USB video not recommended	CPU: 20C+MT RAM: 12 GB - Thin Client: RemoteFX - USB video not recommended

Minimum recommended hardware for running full Windows 10 virtual desktops

Running a full virtual operating system instance for each station is more compute resource-intensive than running the default MultiPoint desktop sessions, so the host hardware requirements per station are higher:

Microsoft Remote Desktop System Requirements Mac Os Catalina

1. CPU: 1 core or thread per station

2. Solid State Drive (SSD)

   1. Capacity >= 20GB per station + 40GB for the WMS host operating system

   2. Random Read/Write IOPS >= 3K per station

3. RAM >= 2GB per station + 2GB for the WMS host operating system

Mac Microsoft Remote Desktop 12

BIOS CPU setting has been configured to enable virtualization – Second Level Address Translation (SLAT)

Desktop System Info

For more information about choosing the best MultiPoint Services hardware for your needs, contact your hardware vendor.