We have been struggling with managing Edge in a non-persistent, randomly assigned VDI environment with persistent user layers for many months. The issues started when Edge was included with Windows 10. We currently are on build 21H2. We frequently have users with different versions of MS Edge on their VDI, and we occasionally have users that have side by side errors when launching it. Also, users occasionally see their Edge settings missing (like extensions and favorites.) We have tried a multitude of combinations of local and domain GPOs as well as service and task management to try to control the problem, but it hasn’t worked.
Citrix has finally helped to address the issue with this support article.
App Layering: How to configure Edge in an App Layering Environment (citrix.com)
However, the article does not explain what the expected behavior of a machine built with these rules should exhibit.
We have machines that are built to the exact specifications of the article but it seems like Edge is not optimal. For the most part, it seems like the Edge version is properly controlled by the version included in the OS layer, which is good. In this case, v101.0.1210.53 is what we expect to be installed and it is correct.
The services’ startup types match “disabled,” which is what is prescribed in the Citrix article on the machine.
Also, the scheduled tasks are disabled as they are supposed to be.
Finally, this is the content of the file at "C:\Program Files\Unidesk\Uniservice\UserExclusions\EdgeExclusions.txt"
The problem behavior is as follows. If users go to about:edge, they get an UAC prompt asking for admin credentials. Our users don’t have admin rights by design.
When the user cancels this prompt, Edge throws an error.
The questions are:
1. Is this expected behavior for a machine built to the specs of the article?
2. And, if so, how can we suppress the error and hide the UAC prompt?
Question
Brad Pelletier
We have been struggling with managing Edge in a non-persistent, randomly assigned VDI environment with persistent user layers for many months. The issues started when Edge was included with Windows 10. We currently are on build 21H2. We frequently have users with different versions of MS Edge on their VDI, and we occasionally have users that have side by side errors when launching it. Also, users occasionally see their Edge settings missing (like extensions and favorites.) We have tried a multitude of combinations of local and domain GPOs as well as service and task management to try to control the problem, but it hasn’t worked.
Citrix has finally helped to address the issue with this support article.
App Layering: How to configure Edge in an App Layering Environment (citrix.com)
However, the article does not explain what the expected behavior of a machine built with these rules should exhibit.
We have machines that are built to the exact specifications of the article but it seems like Edge is not optimal. For the most part, it seems like the Edge version is properly controlled by the version included in the OS layer, which is good. In this case, v101.0.1210.53 is what we expect to be installed and it is correct.
The services’ startup types match “disabled,” which is what is prescribed in the Citrix article on the machine.
Also, the scheduled tasks are disabled as they are supposed to be.
Finally, this is the content of the file at "C:\Program Files\Unidesk\Uniservice\UserExclusions\EdgeExclusions.txt"
The problem behavior is as follows. If users go to about:edge, they get an UAC prompt asking for admin credentials. Our users don’t have admin rights by design.
When the user cancels this prompt, Edge throws an error.
The questions are:
1. Is this expected behavior for a machine built to the specs of the article?
2. And, if so, how can we suppress the error and hide the UAC prompt?
Link to comment
4 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now