Looking for a browser enumeration issue solution. Have a client with mandatory profiles, and gpo assigned extensions for edge. One of the extensions is required for a particular site users will use. The problem is Edge will render the page before the extension is in place , and it then pops an error saying the extension needs to be installed. If you refresh the page it is fine, as the extension is now loaded and ready to go. Since browser profiles can't be stored in mandatory profiles, yay, we can't front load this into the session. Right now I am considering doing a script to launch edge and then close it for a particular subset of users, but looking to see if anyone has seen anything similar. Like a way to tell edge don't load until extensions are all installed and activated, or a background pre-launch option of edge.

Is this for published Edge in XenApp? If so, one solution would be to add those keys into WEM and then use VUEMAppCmd.exe as the published application with Edge in the Paths field, that way Edge doesn't launch until the WEM settings are applied. Unless I'm misunderstanding the issue, like if the keys are there and Edge can't install it quick enough.

Unfortunately, edge is spawned from a link hosted in another published app.

Ah, gotcha. On the pre-launch idea, the only thing I can offer you here is a way to launch Edge and hide it from the user, then close it.

Edge only reads those keys on launch, so it's not a race condition of the keys landing after Edge. Following along as we run into the same issue with our pooled random desktops, as our Document Management System relies on a Chrome/Edge extension. We currently launch Edge/Chrome during our Ivanti WSC splash screen (run once per user).... not the most elegant and I'd love a better solution.

Hi @Jon Bucud Thanks for the kind words! Can you give me a bit more details concerning this issue? I don't think that I fully understand it. Thanks.

Hi @Dennis Span, A race condition when launching Chrome for the first time directly to a URL, where an extension is configured via policy does not get loaded into the users browser on the first load. ie. • Configure Chrome via UEM of choice to install Extension via registry at HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome\ExtensionSettings\extensionID • Publish Chrome, to launch directly to URL 1. User clicks to launch Chrome 2. UEM loads settings 3. Chrome reads registry 4. Chrome begins to load page, but extension is not fully loaded 5. Page responds with required extension is not installed 6. User refreshes, extension is now installed and page loads as expected

@Jon Bucud Hi John. You mentioned an "HKEY_LOCAL_MACHINE policy.. This confuses me, since Chrome extensions are stored on a per-user bassi (in the manifest.json file in the user's Windows profile to be exact). Chrome extensions are not registry keys. They need to be written to the manifest file in order to work. The issue you describe sounds like a timing issue to me. Are you not able to use an actual group policy? https://dennisspan.com/deploying-google-chrome-extensions-using-group-policy/

HKLM vs HKCU was a mistake on me typing it out. But yes, the result of the GPO is the regkey, I mentioned the regkey so we can be policy mechanism agnostic, as others here may use a UEM of choice to apply the above. from your blog;

Now the policy setting is configured. On the next Group Policy refresh the user will automatically receive the required extension. To summarize, this policy will automatically install one or more extensions for all users to whom the Group Policy applies. The installation is executed silently and without user interaction.

This happens when the above reg key is in place, but not in time for that first load. There's a reproducible race condition when a user loads Chrome directly to a URL, and that first page renders before the extension is loaded. @Jeff Riechers I wonder if the "better mouse trap" solution is to load to a splash page with a timed redirect to the target page (splash with meta refresh in there maybe)? Not unlike to how UEMs do session setup... splash page, load settings into user session, then load interactive desktop?

Interesting. I think this site is hosted behind a netscaler. I wonder if that is something I can do as a policy there.....