![]() There are GPOs for management of Edge, but some of them are more preferences than policies. The upshot of this is that when users move sessions between devices, they will have to reset their search provider manually. You can see the protected nature of the registry value that controls the search provider by looking at its name: ![]() ![]() However, the registry value that Edge sets appears to be created with some device-specific variables, making it impossible to roam. I thought it might be possible to get around this issue by setting the user’s home page to Google via GPO, automatically “visiting” the page at application launch and then capturing and persisting the associated registry values. For Chrome and Firefox, though, their default search provider is already Google, but with Edge, unsurprisingly, the default is set to Bing. Most people in enterprise are keen to have Google as their default search provider, and Internet Explorer’s coming with a built-in default set of search providers enabled Google to be set as the default with a simple policy to enable specific registry values.Įdge, though, uses OpenSearch (as do Chrome and Firefox), meaning that to set a search provider, the page must first be visited. It is also incredibly difficult to set policy settings for users within Edge, such as the default search provider. ![]() ![]() The irony is that “Modern” Apps require a legacy approach like logon/logoff scripts to accommodate functions that the user has come to expect. This can be achieved with Group Policy scripts or a user environment management (UEM) solution such as AppSense or RES. Essentially, to persist the user settings users for Edge usually requires running logon and logoff scripts to copy file and registry settings out to a home drive share and then bringing them back in at the next logon. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |