I like choice, and I really like privacy, so naturally, I am drawn to the Brave browser due to its underpinning fundamentals of “privacy first”. In short, it’s the Chrome engine with a load of inbuilt privacy and tracking protection similar to uBlock Origin, an extension for Google Chrome but all built-in.
I had some fun getting it to work in a Citrix environment but after some playing around have a neat deployment.
Important to note, I am not providing advice to move to Brave, it’s not really enterprise-ready (if you want all the controls that something like Chrome or IE give you in a supported fashion), however should you choose to have a play, the below should get you started.
Conversely, the same symptoms and challenges are raised with the new Chromium-based Microsoft Edge browser, so I documented both.
When you install either Brave or Microsoft Edge Dev on a server or desktop with the Citrix VDA installed, launching either process will result in a white window which will spank your CPU and leave your session effectively useless
Task Manager shows us a load of processes launched, but nothing plays
No surprises, but the underlying cause of this is the Citrix API hooks latching themselves onto either the
Brave.exe or the
MSEdge.exe processes. Simply disabling the hooking brings it back to life.
As per the Citrix, Article disable all Citrix Application Programming Interface (API) hooks on a per-application basis, this can either be done via the ExlcudedImages key (pre-VDA 7.9) or the UviProcessExcludes key in anything modern.
I tested both out of curiosity and they both worked perfectly fine, the
UviProcessExcludes required a full reboot.
As a quick note, the following string already exists in a default install, so you may want to take this and simply append our new processes to the end:
I am writing them with a simple computer-based Group Policy Preference below
And upon successful run you should see your registry reflect your changes:
Brave and Edge now launch as expected:
Brave uses the concept of shields to protect your browsing experience, below hitting eBay landing page alone shows 8 blocked trackers. I run Pi-Hole to protect my household from this junk and am a massive advocate for DNS based protection in the Enterprise, however it’s nice to see exactly which nasty stuff is going on in the browser locally.
Go and hit a page like ninemsn.com.au and watch your shields start going into overdrive
The browsing experience in Brave (and anything protected by DNS filtering and privacy-based tracking protection extensions) is so much snappier than without.
Brave is just Chromium under the hood so the usual capabilities apply, however, there is no enterprise capability around centrally managing it at the moment, however a few things I like to do below in my own profiles
brave://settings/getStarted (in the URL bar)
- Hide Brave rewards bar
- Show the home button
- Set your Search Engine (Duck Duck Go for me given I am on an anti-advertising rant)
- Set your Downloads if different than default locations
- Set Dark Mode
- Install any extensions you may need (though hopefully, that’s limited)
Both Brave and Microsoft Edge follow the same structure as Chrome for their data pathing for the most part and will both be subject to the same buildup of junk. If you are going to throw these into an environment, it’s worth keeping an eye on data sizes and managing your profiles accordingly. In the example below, I have three profiles in Brave, the default and 2 additional. There is also a system profile.
Browsing around for a few bits and pieces and you can see that the usual “Cache” folder is going to start growing quite quickly
For those using FSLogix, add the following path to your redirections. Remember this is per profile in Brave, Chrome or Edge, so you need to be wary if you are using multiple profiles:
<Exclude>AppData\Local\Microsoft\Edge Dev\User Data\Default\Cache</Exclude>
For Citrix UPM you will need to add the following to your Exclusion list – directories policy
!ctx_localappdata!\Microsoft\Edge Dev\User Data\Default\Cache
Both Brave and Microsoft Edge will throw in their own update services that you will want to deal with:
They will also both throw in the usual scheduled tasks to slap:
Interestingly, and not that I have done any level of extensive testing, but out of the three Chromium-based browsers, Microsoft Edge appears to have the lowest consumption of resources, followed by Google Chrome and then Brave.
The usual rules apply for both Brave and Edge for application publishing
Both apps launch seamlessly and without any obvious issues I can see
Whilst this is not in any way shape or form an extensive guide to deploying these browsers, hopefully, it unlocks the door to allow you some basic testing, and give you a few more options in your tool kit