Notitie
Voor toegang tot deze pagina is autorisatie vereist. U kunt proberen u aan te melden of de directory te wijzigen.
Voor toegang tot deze pagina is autorisatie vereist. U kunt proberen de mappen te wijzigen.
This article describes the requirements and limitations for using Microsoft Edge in a virtual environment.
What is VDI?
Virtual desktop infrastructure (VDI) is a desktop virtualization technology that hosts an operating system and applications on a centralized server in a data center. This technology enables a fully personalized desktop experience for users on a secure and compliant centralized source.
Microsoft Edge can be used in a virtual environment in much the same way as it's used on a local device. A virtual desktop takes advantage of a secure and controlled server environment. Depending on the VDI solution you choose, it might also be possible to give your users seamless access to intranet applications and sites.
Most Microsoft Edge features are supported in VDI environments without any special configuration. However, to ensure an optimal experience we recommend that you review the following guidance.
Platforms certified for Microsoft Edge
The following platforms are certified for Microsoft Edge:
- Azure Virtual Desktop
- Citrix Virtual Apps and Desktops (formerly known as XenApp and XenDesktop)
Although the Microsoft team hasn't certified other VDI solutions yet, it's expected that the most common workflows in Microsoft Edge should be supported. The following guidance might or might not be applicable to your chosen solution.
Performance considerations for Microsoft Edge on VDI
When designing your VDI environment you should carefully consider the workflows and needs of your users to achieve optimal performance, and understand the limits of your server configuration.
The following minimum requirements are recommended for deploying Microsoft Edge on a VDI environment:
- vCPU – 2-4 cores per User
- RAM – 1 GB per User
Large and complex web applications and extensions need more memory and processing capability, which must be considered when configuring your virtual environment.
Microsoft Edge on non-persisted VDI environments
Many VDI solutions allow access to persisted environments, where users are assigned as a virtual environment that persists between sessions, and non-persisted environments, where users are assigned to one of several available machines, possibly a different machine each session, user data might or might not sync between sessions.
When using a non-persisted environment, one usually creates a "golden image" that has the required apps and configurations that are deployed on each device. Use the following recommendations as a guide for preparing a golden image.
Deploy Microsoft Edge
If you are on Windows 10, version 1803 and above, you should already have Microsoft Edge installed on your system. However, if you're using an older version of Windows or want to deploy a different Microsoft Edge channel, follow these steps:
Download the Microsoft Edge MSI package that matches your VDI VM operating system from:
Run the following command to install the MSI to the VDI virtual machine (VM):
msiexec /i <path_to_msi> /qn /norestart /l*v <install_logfile_name>
Disable automatic updates
For non-persisted machines, the best practice to disable automatic updates and update Microsoft Edge by updating the golden image to ensure that there are no version mismatches among the pool of virtual machines.
For more information about disabling automatic updates, see the following policies:
Profile management
On non-persisted setups, it's important to consider that VMs might not maintain user state between sessions or users might be assigned a VM they've never used before. In this scenario, the VM doesn't have any of the user's data.
Microsoft Edge supports two methods for syncing user data so it's available regardless of how they're accessing Microsoft Edge:
- Microsoft Entra ID sync
- On-premises sync for Microsoft Entra users.
Microsoft Entra ID Sync
If your Microsoft Entra ID plan supports it, Enterprise sync is the fastest and easiest method to ensure that Microsoft Edge user data is synced to all user devices. For more information, see Configure Microsoft Edge enterprise sync
Enterprise sync supports multiple concurrent sessions, works across versions and is the recommended solution for syncing user data.
On-premises Sync for Active Directory Users
With on-premises sync, Microsoft Edge saves an Active Directory user's favorites and settings to a file that can easily be moved between different computers.
For more information about requirements and configuration, see On-premises sync for Active Directory (AD) users
On-premises sync doesn't support syncing multiple concurrent sessions.
User Profile Redirection
Although there are some solutions in use for migrating and redirecting the user data folder (UDF) to maintain user context in a non-persisted environment, they come with reliability and performance risks.
Some popular solutions include the following options:
Redirecting the entire UDF should be avoided, as it can cause reliability issues when a data type stored in the UDF has an incompatible storage-format upgrade in a Microsoft Edge version update. In some scenarios, such as when there are rolling version updates on a server farm, Microsoft Edge can crash or hang when it tries to use an incompatible stored version from the UDF.
If you plan to redirect any portion of the UDF, it should only be a small subset such as Bookmarks, Preferences, and History. Some examples of folders that are known to cause performance issues when roamed, and should therefore be excluded, are:
- %LocalAppData%\Microsoft\Edge\User Data\Default\Cache
- %LocalAppData%\Microsoft\Edge\User Data\Default\Code Cache
- %LocalAppData%\Microsoft\Edge\User Data\Default\JumpListIconsTopSites
- %LocalAppData%\Microsoft\Edge\User Data\Default\JumpListIconsRecentClosed
Microsoft Edge Enterprise sync and On-premises sync don't carry these risks, and are therefore the recommended way to sync Edge user data.
Known issues
Microsoft Edge crashes in older versions of XenApp and XenDesktop
This issue should be mitigated in newer versions of these products. However, if you're encountering this issue in your environment, you can work around the issue by disabling Citrix API Hooks for Microsoft Edge, see How to Disable Citrix API Hooks on a Per-application Basis.
Degraded performance when rendering pages with exceptionally large HTML tables
The following Citrix policies are known to slow rendering of html pages with large (30,000+ row) tables.
Automatic keyboard display
Remote the combo box
For more information, see Mobile experience policy settings (citrix.com) for more information. Disabling these policies should mitigate the issue.
Windows Account Manager authorization scenarios (that is, Azure sync) fail in Microsoft Edge when run as a Citrix seamless application
This is a known issue in Microsoft Edge and other applications that use WAM (that is, Office) due to necessary Windows components not being initialized when running in the "seamless" mode. Try one of the following options to work around this issue:
- Use Microsoft Edge via a Remote Desktop to the Citrix Host instead of a seamless remote application.
- Use Azure Virtual Desktop remote apps instead, which has mitigations for this issue.