Apr 16 2020 05:54 AM
In our environment, we only use local profiles in Edge. The default path upon initial configuration on the client is “%LOCALAPPDATA%\Microsoft\Edge Beta\User Data\Default”
We noticed that if the profile is removed via settings menu (e.g. for troubleshooting reasons) a new profile is created immediately and a new folder in "User Data" folder called "Profile 1" is created. After a second removal, a folder called "Profile 2" and so on.
On this on-prem local profile scenario, I would prefer to delete and recreate "Default" folder instead of creating a new folders.
We user UE-V to save some files from Edge, e.g. bookmarks. in the UE-V settings file we added the path to the default profile folder. In this case, we would need to add "Profile 1" up to "Profile 9999".
Could this behavior be changed?
Apr 17 2020 02:27 AM
Not the exact the same but quite similar problem here:
Apr 17 2020 03:21 AM
@Joachim_T Thanks for the hint! Just linked to this thread. Maybe the root cause is the same.
Apr 17 2020 03:52 AM
@stesch79 We configured https://docs.microsoft.com/en-us/DeployEdge/microsoft-edge-policies#configureonpremisesaccountautosi... to make default profile not removeable. But we have domain-joined computers/users only.
Apr 17 2020 04:26 AM
@Thilo Langbein Thanks. Yes, if I also change the BrowserSignin from 0 back to 1 (Default) and set ConfigureOnPremisesAccountAutoSignIn the behaviour is as you said, the removal of the profile isn't possible anymore.
Apr 17 2020 04:33 AM
Apr 17 2020 09:28 AM
@stesch79 Yes, but only once. I'm not happy with this, but good.
Apr 20 2020 05:24 AM
In my Eyes this popup is disgusting. It means my servicedesk will be flooded with hundreds of calls from helpless user who think they got hacked because they can see a popup they never have seen before.
We need a "User has to do nothing and not even think" solution
Apr 20 2020 05:53 AM
@Joachim_T From my experience, most users click on any OK button without reading the message. :)
Apr 22 2020 06:59 AM
@stesch79 we ran into the same problem with VMware UEM for profile management solution we use.
Solution we use at our servicedesk:
Rename the Profile x directory to Default, then remove the file "Local State" and the let the user start Edge & log on. After that it is fixed.
reg, Henno
Apr 22 2020 11:15 AM
Apr 22 2020 11:10 PM
@Joachim_T I agree. But we are not close to the root cause of the problem we want to see the scale of the problem and involvement of the ServiceDesk on the issue.
Otherwise one is not fixing the problem but automating a workaround.
reg, Henno
Apr 23 2020 02:59 AM
@Henno_Keers @Joachim_T I think UE-V will never be a good solution for syncing this Edge profile stuff. Microsoft has confirmed that it will enable https://cloud.google.com/docs/chrome-enterprise/policies/?policy=RoamingProfileLocation for syncing Favorites/settings to a local UNC share. That's the solution I wait for.
Apr 23 2020 03:22 AM
@Thilo Langbein that is in relation with this https://cloud.google.com/docs/chrome-enterprise/policies/?policy=RoamingProfileSupportEnabled setting.
But... I have heard, that is the case with Google Chrome too, that enabling this setting, disables "Cloud sync" i.e. login on to your AAD account for synching of your Edge settings.
We found ourselves in the situation that we need both:
So a colleague of mine created a VMware UEM config that does that.
It is not pretty, but it does the job at the moment.
reg, Henno
Apr 23 2020 04:47 AM
@Henno_Keers We don't want our user to login to AAD. Only OnPrem-AD.
So favorites should/could only synced locally.
May 07 2020 08:35 AM
Is there any official statement from Microsoft regarding RoamingProfileLocation?
has been removed...
May 07 2020 11:44 PM - edited May 07 2020 11:46 PM
Last statement (I have) from MS about RoamingProfileSupport. I'm a little concerned about what you found.