This message was deleted.

Thanks Ray, it is the same info that I found. Based on this, it means only IE works with BCR when using VDA7.15 and you need VDA 1808. But if you read https://docs.citrix.com/en-us/xenapp-and-xendesktop/7-15-ltsr/whats-new/cumulative-update-4.html it mentions Chrome so it should work. That's why I'm confused.

we do use BCR on VDA 7.15 CU5 in Chrome (annoying thing : the DPI/Scaling on client needs to be 100% or you've to disable GPU use)

Did you remember to download the BCR extension in Chrome? https://chrome.google.com/webstore/detail/browser-redirection-exten/hdppkjifljbdpckfajcmlblbchhledln?hl=da

Thanks Tom and Kasper! It's great to get confirmation 👍 Yes I've got the Chrome extension installed, turn on by policy, the VDA installed without html5 and BCR.msi installed. I must be missing something. I've got only an handful of GPU VMs, I may just disable BCR on those, we'll see! Thanks again 😀

To be clear : it is not GPU on the VM but GPU or DPI scaling on the client : see https://support.citrix.com/article/CTX230052 Due to the limitation of CEF(Chromium Embedded Framework), client endpoint GPU needs to be disabled if DPI scaling factor is set to a number other than 100% in order for BCR feature to work. Otherwise BCR displays the website in a corrupted fashion (like zoomed in and cropped). To disable, configure on the Client: HKLM\SOFTWARE\Citrix\HdxMediastream\ For 64-bit: HKLM\SOFTWARE\Wow6432Node\Citrix\HdxMediastream\ Key: GPU (DWORD) Value: 0

OK thanks for the clarification Tom! It's going to be tricky to do on the users own devices. In general how happy are you (and your users) with BCR? Was it worth it?

it is ok if you manage the endpoint (as such you can control GPU setting), for non managed devices it is more "complicated". Strange that Workspace App does not detect the "bad" conditions and adapts its parameters. In addition we're having issues if we want to use BCR over our internal Proxy (server fetch), for now we don't. Also webex is an issue ... bottom line : we are not (yet) convinced if we'll roll out generally ...

Thanks Tom. Yes indeed Workspace is not so smart, I'm not so surprise haha. I'll see how it goes, it is probably good only for some specific sites like YouTube.

What WSA are you on? We have this working fine with 7.15LTSR CU4 with Server 2016 and WSA 1911 on Chrome.

Yea @Ryan Gallier is correct. I had the same issue.

Ah I was testing with Workspace 1912 CU1 LTSR, crap. So you can't use BCR wih WSA 1912, hm and what about latest WSA? And thanks!

The latest WSA should support BCR

Thanks

Hahahha

Sure

Thanks guys, that's a sneaky way to force customer on CR release ... anyway I'm going to try BCR with latest WSA.

CR is the way to go

At least for WSA....

@Ryan Gallier are you on LTSR only?

On a majority of our environments, yes

Any particular reason?

I'm LTSR too, that's why I'm reluctant to go CR.

too many things break during upgrades for us to keep up with it

100!!?? OMG

Hm I am not taking a risk to do in-place, at least not the Controllers and PVS, to 1912 for thousand of users.

So you are not installing CUs then?

I do for CUs. With latest CWA, BCR is still not working, white page when loading YouTube when it is enabled. I can see in the debug the page is redirected, strange.

Which browser are you using for BCR?

Chrome 83 32bit

Hmm.. I don't have 32-bit of anything left in my lab setup

Ok I'll do a bit more tests, thanks!

I have just tested BCR in 64-bit Edge in WS2019 with latest VDA and Windows 10 v2004 with latest CWA. No issues with BCR.

@Kasper Johansen Yeah, if I only had 1 large environment, I would run things MUCH differently.

I tested on my lab and BCR works fine zith 7.15 CU4 with latest CWA and Chrone 84 32bit. The BCR.msi architecture is based on the VDA, I was wondering if it could be the issue (need 32 bits BCR for 32bit browser). So something in my env break BCR, new error on the Chrome extension "could not connect on the websocket server", it is red icon. I enabled the debug log but I can't find it, I may need to do a procmon except is someone know where it is. My BCR issue could be proxy related or the fact I have 2 NICs in my VM (1 PVS, 1 prod), it would make sense what it can't connect on the local websocket. I need to do more tests.

Any particular reason as to why you are using a 32-bit browser?

Yes it is needed by some other internal apps, but we could probably move to 64bit with some effort. I found for the debug, it is in Chrome debugging but nothing about the webSocket connection error.