Using Windows Server 2019, RDweb still relies on ActiveX for:
OneClick launch of RemoteApp
Connect to a remote PC
This means that if you visit an RDweb site (hosted on RDS using Windows Server 2019) with Chrome, Edge, Firefox and all those other browsers not supporting ActiveX - you will not be able to use the "Connect to a PC" tab, and you will have to download a .RDP file to access RemoteApps.
Now that Microsoft has changed to the Chromium engine in their own Edge browser, you would think that things like ActiveX dependencies would be removed from currently supported software.
Are there any plans for this? Did they just forget?
I cannot believe that we still must rely on Internet Explorer for these things now days.
Hey there :),
How is everything going?
Have you checked if below answers help? If they are helpful, please do not forget to accept the answers.
Thanks
Karlie
Check
here
,
For some enterprise web apps and a small set of sites that were built to work with older technologies like ActiveX, we will need to use Enterprise Mode to automatically send users to Internet Explorer 11.
----------
If the Answer is helpful, please click
"Accept Answer"
and upvote it.
Note: Please follow the steps in our
documentation
to enable e-mail notifications if you want to receive the related email notification for this thread.
Best Regards
Karlie
Hello
@Karlie Weng
Your answer is interesting. However it will only be practical for internal users controlled by GPO.
External users will still experience the same issue.
To make it even more challenging, our organization has choosen Chrome as the default browser. Not Edge...
Hi
@Lars Olsen
Sorry that didn't help :(
If you have a feature suggestion, you can tell us using the client user voice forum.
Remote Desktop Services for user voice
https://remotedesktop.uservoice.com/forums/266795-remote-desktop-services
Best regards
karlie