This message was deleted.
# _general
s
This message was deleted.
k
r
Have you guys by chance installed it on 2016 server ?
d
but that’s still the beta release
k
Yes, I don't think Redmond is awake yet :)
@Ray Davis I have it running in both 2016 and 2019 no issues so far. Be aware of the Citrix API hooks though: https://jkindon.com/2019/09/17/deploying-brave-and-microsoft-edge-dev-browsers-in-citrix-cvad-environments/
r
Ahh ok, Yea I figure that would be needed. Cool, glad its working.
u
@dready will be made Stable today or Tomorrow
d
Edge Chromium is available now and it's working on my Windows 10 Enterprise 1909 - no Citrix API hooks tweaking needed
👍 3
k
Great news @dready :)
r
Nice
k
@dready I see that it is still necessary to disable the Citrix API hooks for Edge when installing the browser in WS2019
r
It does need API hooks. CPU went nuts and it locked up on 2016.
👍 1
Did this on multiple 2016 Servers
k
Thanks for confirming @Ray Davis
r
No problem
d
will double check on my Windows 10 deployment - didn’t notice any issues so far
👍 1
OK folks, I still thin in my Win 10 1909 / Citrix CVAD 1912 deployment disabling API hooks for the new Chromium Edge is not necessary. Server OS might be an other story, didn't test that. @Ray Davis @Kasper Johansen
👍 1
r
No prob, i tested it on 2016 OS. It was needed for us. Also side note api hooks is needed on teams on 2016 as well. @Tim Riegler has a case with MS on it as well. Not meaning to get off track but wanted to share his finding as well with them.
I use as well to much lol
d
thx fir the update @Ray Davis - no issues with teams as well 😂
r
Server 2016?