First identify which Remote Desktop browser experience you need. A legacy RD Web Access page that depends on ActiveX or a specific Web Single Sign-On (SSO) flow may need to run in Internet Explorer mode in Microsoft Edge. The separate HTML5 Remote Desktop web client supports modern browsers, including Edge and Google Chrome, when its deployment requirements are met. Chrome does not provide Edge’s Internet Explorer mode.
RD Web Access and the HTML5 web client are different experiences
The phrase “RD Web Access” is often used for two different browser experiences. The distinction matters because changing a browser setting can help with one and do nothing for the other. Before changing policy, identify the URL users open and what happens after they sign in.
As an Amazon Associate I earn from qualifying purchases.
| Experience | What it is | Browser compatibility path | What to check |
|---|---|---|---|
| Legacy RD Web Access page | The older RD Web portal. A particular legacy feature path may use an ActiveX control to display or launch RemoteApps and desktops. | If that site depends on ActiveX, test it in Edge Internet Explorer mode and, if appropriate, add it to the organization’s managed Enterprise Mode Site List. | Whether the portal or launch control is missing in standard Edge, and whether the organization uses the legacy ActiveX path. |
| HTML5 Remote Desktop web client | A separate browser client for accessing desktops and RemoteApps. Microsoft says it does not replace the RD Web Access page; the two experiences use different URLs. | Use a supported modern browser such as Edge or Chrome, subject to the client’s requirements. | Whether the client is deployed and published correctly, and whether its server and certificate configuration is valid. |
Microsoft’s Remote Desktop web-client documentation describes support for modern browsers including Edge and Chrome. Its separate legacy troubleshooting guidance discusses an RD Web scenario in which the MsRdpClientShell - MsRdpWebAccess.dll add-on is loaded as an ActiveX control. That specific case is not evidence that every RD Web Access installation requires IE mode: establish which client and feature path your organization actually uses.
Write down the exact address before troubleshooting. A legacy portal address and an HTML5 client address can be hosted on the same deployment but still represent different applications. A user who bookmarks the wrong address may appear to have a browser-compatibility problem when the real issue is simply that the intended client was never opened.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Does RD Web work in Chrome?
It depends on what you mean by RD Web. Chrome is supported for Microsoft’s HTML5 Remote Desktop web client, subject to that client’s browser and deployment requirements. Chrome does not run Microsoft Edge’s Internet Explorer mode, so it is not the equivalent compatibility route for an RD Web page that relies on ActiveX or for the documented Web SSO flow through the Windows inbox Remote Desktop Connection client.
If Chrome is required, ask the administrator whether the organization can provide the HTML5 web client. Do not assume that an older portal’s ActiveX controls or legacy launch behavior will work in Chrome merely because the HTML5 client does.
Microsoft’s user guidance also lists Safari and Firefox among modern browsers for the HTML5 client. That statement applies to the separately deployed web client, not automatically to every page served by RD Web Access. Keep browser claims tied to the actual client version and to the organization’s supported configuration.
When Edge Internet Explorer mode is relevant
Legacy ActiveX behavior
Standard Edge does not support ActiveX controls. Microsoft’s legacy RD Web troubleshooting guidance describes a case where the RD Web page uses the MsRdpClientShell - MsRdpWebAccess.dll add-on as an ActiveX control. If a page or launch control is missing in standard Edge, determine whether this is the feature path in use before changing compatibility settings. For that specific legacy requirement, Edge IE mode is the browser compatibility option described by Microsoft.
Do not infer that a missing button always means ActiveX. The same symptom can result from opening the HTML5 URL incorrectly, an incomplete web-client publication, authentication failure, a certificate problem, or a server-side configuration issue. Test the affected function, not just the landing page, and record whether the failure occurs before or after authentication.
Web SSO through the inbox Remote Desktop Connection client
Microsoft’s supported-configuration guidance is explicit for this scenario: “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 Mode in Microsoft Edge.” This is a specific Web SSO configuration, not a blanket requirement for every browser-based Remote Desktop connection.
For that Web SSO route, Microsoft lists these server-side requirements:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
- RD Web uses form-based authentication.
- RD Gateway uses password authentication.
- The deployment setting Use RD Gateway credentials for remote computers is enabled.
- Smart cards are not supported for this Web SSO configuration.
Microsoft says other configurations are unsupported for this particular Web SSO scenario. If SSO still fails after the site is opened in IE mode, compare the deployment with these requirements rather than repeatedly changing browser settings. A browser-mode change cannot make an unsupported authentication combination supported.
Test a legacy RD Web site locally in Edge
A local IE-mode reload is useful as a diagnostic or temporary bridge, if device policy permits it. It is not the organization-wide management method and it does not configure Chrome.
- Allow IE-mode reloads. In Edge, go to
edge://settings/defaultBrowserand enable Allow sites to be reloaded in Internet Explorer mode, if the option is available. An administrator can also manage the correspondingInternetExplorerIntegrationReloadInIEModeAllowedpolicy. On a managed device, policy may control or disable this option. - Open the RD Web URL. Navigate to the site that is failing in standard Edge. Use the exact host name users normally receive, rather than substituting an IP address or a different alias.
- Reload in IE mode. Open Settings and more (…) and select Reload in Internet Explorer mode.
- Test the affected function. Check the portal feature or launch path that was failing. A successful test shows that IE mode helps that specific site path; it does not establish that every part of the deployment requires IE mode.
A site remembered through this local experience is kept for 30 days by default. Microsoft describes the local entry as a way to keep a user working while an organization updates its managed site list. For a durable or organization-wide configuration, have IT manage the entry centrally. Users should not treat the 30-day memory as a permanent exception or as a substitute for change control.
If the reload command is absent, first check whether the reload policy is allowed and whether Edge has received current device policy. Do not ask users to install Internet Explorer; the documented compatibility path is the IE-mode engine built into Edge.
Configure IE mode centrally with an Enterprise Mode Site List
For managed devices, the central approach is to add the RD Web URL to the organization’s Enterprise Mode Site List and set its behavior to open in IE mode. Administrators can use Microsoft Edge’s Enterprise Site List Manager or the organization’s existing site-list process.
- Add the RD Web site. In Enterprise Site List Manager or the organization’s managed list, enter the RD Web URL that users need to access. Include the URL users actually open; if separate host names serve different paths, evaluate each required entry.
- Set the opening behavior. For that entry, choose IE mode for its Open in behavior. The setting is for the legacy site path that needs it, not for all browsing in Edge.
- Publish and point Edge to the list. Configure Edge’s
InternetExplorerIntegrationSiteListpolicy to use the hosted site-list XML or the organization’s managed list location. - Restart Edge. Microsoft notes that the site-list policy requires a browser restart for changes to take effect. Close all relevant Edge windows and reopen them after policy delivery.
- Verify the applied entry. Confirm that the policy and list reach the relevant user or device, open the RD Web URL, and check for Edge’s IE-mode indicator.
Site-list administration should be treated as a managed deployment task. Test the entry with the same account, device policy, URL, and authentication path used by affected users. If only part of a server needs IE mode, Microsoft also documents configurable sites for more targeted behavior. That is a narrower site-level option; use it only when the broader list entry is not the right fit for the deployment.
A common pitfall is to configure the list correctly but point Edge at an unreachable or stale XML location. Another is to test on a device that has not received the policy. Confirm both policy delivery and the effective list before concluding that IE mode failed.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Deploy the HTML5 Remote Desktop web client separately
If users need a modern browser experience rather than the legacy RD Web page, browser compatibility is only one part of the work. Microsoft’s administrator guidance covers the web client’s server deployment, installation and publishing, and broker-certificate import. Its setup guidance lists RD Gateway, RD Connection Broker, and RD Web Access among the deployment components.
Check the server-side setup
- Follow Microsoft’s administrator guide for the deployment topology and commands. Do not treat an Edge or Chrome setting as a substitute for server configuration.
- Confirm the web client has been installed and published as required by the deployment guide.
- Use a public certificate name that matches the RD Web URL users access; a mismatch can cause certificate-name problems.
- If the broker certificate changes, update and republish the web-client configuration as Microsoft’s guide instructs.
The broker certificate step is easy to overlook during renewal. A client that worked before certificate replacement can stop connecting even though the browser and user account are unchanged. Treat a certificate change as a web-client configuration event: import the new certificate where required, update the client configuration, and republish it.
Use the right URL and browser
The HTML5 client and the RD Web Access page have different URLs. Confirm users have the URL for the intended experience rather than expecting a browser change to transform one page into the other. Microsoft’s user guidance identifies modern browsers such as Edge, Chrome, Safari, and Firefox for the HTML5 client; check the current documentation for the exact client version and requirements in your deployment.
If the HTML5 page opens but no desktop or RemoteApp is available, verify publication and permissions on the Remote Desktop deployment rather than adding an IE-mode exception. IE mode is for the legacy compatibility case; it is not a repair for missing web-client resources.
Troubleshoot by symptom
The RD page or a launch control is missing in standard Edge
Establish whether the affected feature depends on ActiveX. If the organization confirms that legacy path, test the URL in IE mode. If the test works, ask IT to manage the site through the Enterprise Mode Site List rather than relying on each user’s temporary local entry. If the test does not work, move on to authentication, URL, server, and certificate checks instead of assuming the browser mode is irrelevant.
Recommended Free Tools
A user asks for IE mode in Chrome
There is no Edge IE-mode setting to enable in Chrome. Determine whether the user can access the organization’s HTML5 Remote Desktop web client instead. Do not promise that Chrome supports the legacy ActiveX behavior. If the organization has not deployed the HTML5 client, the administrator must choose between deploying that client and managing the legacy URL through Edge.
Web SSO still prompts for credentials or fails
Check that the user is following the documented Web SSO path through Edge IE mode and the Windows inbox Remote Desktop Connection client. Then verify RD Web form-based authentication, RD Gateway password authentication, and Use RD Gateway credentials for remote computers. Smart cards are outside the supported configuration for this Web SSO scenario. Check these server-side conditions before clearing browser data or repeatedly reloading the page.
Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
The HTML5 client loads but cannot connect
Check the web-client deployment roles and the broker-certificate installation and publishing procedure in Microsoft’s administrator guide. Confirm that the URL uses the public certificate name matching the RD Web address, and update and republish the client configuration if the broker certificate has changed. A successful page load proves only that the web page was delivered; it does not prove that the broker and gateway path is correctly configured.
The browser displays a certificate warning
Confirm that RD Web Access is using a trusted certificate and that the server fully qualified domain name (FQDN) users visit matches the certificate. A browser-mode change does not correct a certificate trust or name mismatch. Resolve trust-chain and name issues at the certificate and server configuration layer.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesThe local IE-mode option is unavailable
Check whether the device is managed by a policy that disables local reloads. The administrator can still deploy the URL through the Enterprise Mode Site List, which is Microsoft’s preferred organization-wide method. Do not bypass device policy by asking users to make unsupported registry changes.
IE mode works for one user but not another
Compare the effective Edge policy, site-list version, URL, and device assignment. Local remembered entries are per-user and expire after the default 30-day period, whereas a managed list should be delivered according to policy. This difference often explains why a temporary test appears successful on one workstation but is absent elsewhere.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Choose the compatibility path that matches the deployment
| Need | Use | Management or prerequisite |
|---|---|---|
| Test whether a legacy RD Web feature works with IE mode on one managed Windows device | Edge’s local Reload in Internet Explorer mode option, if policy allows it | Local entry; remembered entries default to 30 days. Useful for testing or bridging, not the central organization-wide solution. |
| Keep a legacy RD Web URL opening in IE mode for managed users or devices | Edge Enterprise Mode Site List with the RD Web entry set to IE mode | Configure InternetExplorerIntegrationSiteList to the managed list location and restart Edge. |
| Access desktops and RemoteApps using the HTML5 browser client | The separately deployed Remote Desktop web client in a supported modern browser such as Edge or Chrome | Requires the server deployment, publishing, and certificate setup described in Microsoft’s administrator guidance. |
| Use the documented Web SSO flow through the Windows inbox Remote Desktop Connection client | RD Web through Edge IE mode | Requires the documented RD Web, RD Gateway, and deployment authentication settings; smart cards are not supported for this Web SSO configuration. |
The deciding factors are the client users need, the legacy feature or authentication dependency, how the browser setting is managed, and whether the relevant server-side requirements are in place. Edge versus Chrome is only part of that decision.
Administrator rollout checklist
- Identify whether users need the legacy RD Web Access page, the HTML5 web client, or Web SSO through the inbox Remote Desktop Connection client.
- Record the exact URL, public host name, and FQDN used by users. Do not substitute a different alias during testing.
- For the legacy path, reproduce the missing control or launch failure in standard Edge and then test the same function with IE mode.
- If IE mode resolves the issue, use a temporary local reload only while the managed site-list change is prepared.
- Add the required URL to the Enterprise Mode Site List, select IE mode, publish the list, configure
InternetExplorerIntegrationSiteList, and restart Edge. - For Web SSO, verify form-based RD Web authentication, password-based RD Gateway authentication, and the Gateway credential setting. Document that smart cards are unsupported for this configuration.
- For the HTML5 client, verify RD Gateway, RD Connection Broker, and RD Web Access roles, installation and publication, and broker-certificate import.
- After any broker certificate change, update and republish the web-client configuration.
- Test with a representative user, device policy, browser, URL, and authentication method before broad rollout.
This sequence separates browser compatibility from deployment configuration. It also prevents a common operational mistake: declaring the browser fixed after the landing page opens while the actual desktop launch, SSO exchange, or certificate validation still fails.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Frequently Asked Questions
Does RD Web Access require Internet Explorer mode in Edge?
Not universally. IE mode is relevant when the legacy RD Web path depends on ActiveX or when using Microsoft’s documented Web SSO route through the Windows inbox Remote Desktop Connection client. The separate HTML5 Remote Desktop web client is intended for modern browsers.
Can Chrome run Microsoft Edge Internet Explorer mode?
No. IE mode is an Edge feature. Chrome can support the separate HTML5 Remote Desktop web client when that client is deployed and its browser requirements are met, but it is not a compatibility layer for legacy ActiveX RD Web pages.
Why is RD Web Access missing in Edge?
First determine whether the missing page element or launch control belongs to a legacy ActiveX path, the HTML5 client, or a server and authentication problem. If the confirmed legacy path uses ActiveX, test the URL in Edge IE mode and then manage it centrally if the test succeeds.
How long does a local Edge IE-mode entry last?
Microsoft documents a 30-day default for a site remembered through the local reload experience. It is intended as a temporary bridge while IT updates the centrally managed Enterprise Mode Site List.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallHow do I configure an organization-wide RD Web IE-mode exception?
Add the required RD Web URL to the Enterprise Mode Site List, set its Open in behavior to IE mode, configure Edge’s InternetExplorerIntegrationSiteList policy to the managed list location, restart Edge, and verify the IE-mode indicator on an affected device.
What are the Web SSO prerequisites?
The documented scenario requires RD Web form-based authentication, RD Gateway password authentication, and Use RD Gateway credentials for remote computers. Microsoft states that smart cards and other configurations are unsupported for this Web SSO flow.
The HTML5 client opens but cannot connect. What should I check?
Check the RD Gateway, RD Connection Broker, and RD Web Access deployment, the web-client installation and publication, and the broker-certificate import procedure. Confirm that the public certificate name matches the RD Web URL and republish the client after a broker certificate change.
Will changing the browser fix a certificate warning?
No. Verify that the certificate is trusted and that the server FQDN users visit matches the certificate name. IE mode or switching between Edge and Chrome does not repair certificate trust or name mismatches.
Free tools Windows power users keep installed
One-click scans. No signup required.
The Bottom Line
Choose the client first. Use Edge IE mode for a confirmed legacy ActiveX path or the documented Windows inbox-client Web SSO configuration, and manage that exception with an Enterprise Mode Site List for organization-wide use. Use the separately deployed HTML5 Remote Desktop web client for modern Edge or Chrome access, with its own server, publication, and broker-certificate requirements. Chrome cannot provide Edge’s IE mode, and no browser setting can substitute for correct authentication, deployment, or certificate configuration.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
