Chromium Edge: Issues with User data directory

[German]The Chromium Edge browser has nasty problems in the corporate environment when managing a user data directory. When user data directories are enabled, the Chromium Edge cannot be used by the same user on different clients at the same time.

German blog reader Christian S. notified me about this problem with the user data directories on the Chromium Edge at the end of January 2020. I'm going to post it here in the blog to discuss the issue.

Problem: User data directory in Edge

An administrator can define in enterprise environments a user data directory for Chromium Edge, using Group Policy (see the following German screenshot). The browser then stores the user data there.

(Click to zoom)

Actually a nice idea that might allow a user to use Edge on different clients with his stored data via his account. That's the theory, but it doesn't work in practice. Christian told me: Unfortunately there is also a problem with the Edge once the user data directory is configured.

Because the Edge only runs on one client when the user data directory is created. After setting up a user data directory using the Edge group policies (see figure above), Christian made the following observation with the Chromium Edge.

Observation with an active user data directory

Once this policy is in place, the Edge will no longer start simultaneously on two machines with the same logged-in user. Here is an example:

• User 1 at workstation 1: wants to start the Edge -> Edge opens
• User 1 at workstation 2: wants to start the Edge -> process starts and ends immediately (without popup)
• User 1 at workstation 1: terminates the Edge
• User 1 at workstation 2: wants to start the Edge -> Edge opens
• User 1 at workstation 1: wants to start the Edge -> process starts and ends directly (without popup)

So the user data directory is blocked on the second workstation by the Edge running on the first workstation. The Edge Browser is then no longer usable. Instead, the running instance at the first workstation must be explicitly terminated to be able to use the Edge on the second system.

I know roughly the deployment scenario of Christian based on the organization specified in the mail, which I will keep private here. The suggestion: Let the users log off when they have to work with the Edge on the second computer, is not realistic.

Workfolder and UEV also no alternative

The idea of Christian was to use working folders (workfolders). Here his test scenario for this case with workfolders:

• User 1 at workstation 1: Starts and ends the Edge
• User 1 at workstation 2: Starts and stops the Edge
• User 1 at workstation 1: Starts the Edge
• User 1 at workstation 2: Starts the Edge
• User 1 at workstation 1: Exits the Edge
• User 1 at workstation 2: Exits the Edge

Christian told me: Unfortunately, workfolders are no solution here either, because after the above test several backup files have already been created. Furthermore he says: Unfortunately User Experience Virtualization (UEV) is not an alternative here, because the Microsoft Edge runs as a multi-process. Therefore Christian directly excludes this alternative.

Question to administrators in the corporate environment: Is this behavior known or already noticed? If so, how do you solve this problem in your environment?

Addendum: After the post went online that night, Christian sent me the information that the problems yesterday could be recreated with Edge v80.0.361.48. In the meantime he could find out the following.

Question: What about sync support for on-prem accounts?

Answer: Currently Microsoft Edge doesn't support sync for on-prem accounts. We will be adding this support in a future release.

Source: Microsoft Enterprise Sync

Christian wrote: I have currently stopped the test rollout and informed the affected users about the problems. As soon as we have a working solution or the new function is added I will continue the rollout.

Similar articles:
Microsoft's Chromium Edge will be distributed via update soon
Microsoft Chromium-Edge released
Chromium-Edge: Issues and no Auto Update for Enterprises
Edge alt und neu im Side-by-Modus betreiben
Edge and its poor installer security