Home

Search Engine GPO

%3CLINGO-SUB%20id%3D%22lingo-sub-1002085%22%20slang%3D%22en-US%22%3ESearch%20Engine%20GPO%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1002085%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20looking%20to%20implement%20Edge%20for%20a%20customer%20early%20in%202020%2C%20and%20things%20so%20far%20look%20fantastic.%20One%20missing%20piece%20is%20the%20ability%20to%20mimic%20their%20current%20Search%20Engine%20policy%2C%20which%20is%20basically%20google%20by%20default%2C%20but%20you%20can%20select%20Bing.%20This%20is%20easy%20enough%20to%20do%20in%20Legacy%20Edge%2C%20but%20the%20policy%20controlling%20it%20in%20new%20Edge%20(called%20%3CSTRONG%3EManagedSearchEngines%20-%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployedge%2Fmicrosoft-edge-policies%23managedsearchengines%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployedge%2Fmicrosoft-edge-policies%23managedsearchengines%3C%2FA%3E%3C%2FSTRONG%3E)%20could%20not%20be%20more%20complicated.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20JSON%20example%20is%20of%20little%20use.%20It%20would%20be%20great%20if%20we%20could%20start%20by%20exporting%20out%20the%20current%20configuration%20as%20it%20has%20all%20of%20the%20correct%20search%20engines%2C%20and%20we%20could%20just%20modify%20the%20%22is_default%22%20field%20to%20the%20correct%20entry.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20tried%20looking%20for%20this%20configuration%20in%20files%20in%20the%20User%20Data%20folder%2C%20but%20it%20doesn't%20seem%20to%20exist%20in%20an%20unencrypted%20form%20anywhere.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1096381%22%20slang%3D%22en-US%22%3ERe%3A%20Search%20Engine%20GPO%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1096381%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20%22ManagedSearchEngines%22%20GPO%20is%20of%20little%20use%20anyway.%20While%20it%20will%20actually%20add%20the%20configured%20search%20engines%20to%20your%20Edge%2C%20the%20%22is_default%22%20attribute%20is%20completely%20ignored%20(under%20certain%2C%20unknown%20circumstances).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20was%20able%20to%20get%20it%20to%20work%20some%20of%20the%20time%20...%20but%20at%20least%20after%20resetting%20Edge%20back%20to%20defaults%20it%20switched%20back%20to%20Bing%20as%20the%20default%20search%20engine%2C%20not%20what%20I%20have%20configured%20in%20the%20GPO.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%5B%20%7B%20%22is_default%22%3A%20true%2C%20%22search_url%22%3A%20%22%3CA%20href%3D%22https%3A%2F%2Fwww.google.de%2Fsearch%3Fq%3D%7BsearchTerms%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.google.de%2Fsearch%3Fq%3D%7BsearchTerms%3C%2FA%3E%7D%22%2C%20%22name%22%3A%20%22Google%22%2C%20%22keyword%22%3A%20%22Google%22%20%7D%2C%20%7B%20%22is_default%22%3A%20false%2C%20%22search_url%22%3A%20%22%3CA%20href%3D%22https%3A%2F%2Fduckduckgo.com%2F%3Fq%3D%7BsearchTerms%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fduckduckgo.com%2F%3Fq%3D%7BsearchTerms%3C%2FA%3E%7D%22%2C%20%22name%22%3A%20%22DuckDuckGo%22%2C%20%22keyword%22%3A%20%22DuckDuckGo%22%20%7D%20%5D%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1096685%22%20slang%3D%22en-US%22%3ERe%3A%20Search%20Engine%20GPO%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1096685%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F336530%22%20target%3D%22_blank%22%3E%40PaulPrior%3C%2FA%3E%26nbsp%3Btrying%20to%20implement%20the%20same%20on%2079.x%20and%20it%20doesn't%20work%20any%20way%20I%20enter%20the%20details%20so%20it%20is%20broken%20for%20sure%20on%20the%20browser.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fgetadmx.com%2F%3FCategory%3DEdgeChromium%26amp%3BPolicy%3DMicrosoft.Policies.Edge%3A%3AManagedSearchEngines%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgetadmx.com%2F%3FCategory%3DEdgeChromium%26amp%3BPolicy%3DMicrosoft.Policies.Edge%3A%3AManagedSearchEngines%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployedge%2Fmicrosoft-edge-policies%23managedsearchengines%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployedge%2Fmicrosoft-edge-policies%23managedsearchengines%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBoth%20of%20the%20above%20references%20are%20wrong%20or%20not%20working%20any%20way.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20999px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F164254i009977579A57C6A7%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22managedsearchengines.png%22%20title%3D%22managedsearchengines.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1119624%22%20slang%3D%22en-US%22%3ERe%3A%20Search%20Engine%20GPO%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1119624%22%20slang%3D%22en-US%22%3EI'm%20having%20the%20exact%20same%20issue%20here.%20Any%20ideas%20on%20how%20to%20solve%20this%3F%3C%2FLINGO-BODY%3E
PaulPrior
Established Member

I am looking to implement Edge for a customer early in 2020, and things so far look fantastic. One missing piece is the ability to mimic their current Search Engine policy, which is basically google by default, but you can select Bing. This is easy enough to do in Legacy Edge, but the policy controlling it in new Edge (called ManagedSearchEngines - https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#managedsearchengines) could not be more complicated.

 

The JSON example is of little use. It would be great if we could start by exporting out the current configuration as it has all of the correct search engines, and we could just modify the "is_default" field to the correct entry.

 

I've tried looking for this configuration in files in the User Data folder, but it doesn't seem to exist in an unencrypted form anywhere.

3 Replies

The "ManagedSearchEngines" GPO is of little use anyway. While it will actually add the configured search engines to your Edge, the "is_default" attribute is completely ignored (under certain, unknown circumstances).

 

I was able to get it to work some of the time ... but at least after resetting Edge back to defaults it switched back to Bing as the default search engine, not what I have configured in the GPO.

 

[ { "is_default": true, "search_url": "https://www.google.de/search?q={searchTerms}", "name": "Google", "keyword": "Google" }, { "is_default": false, "search_url": "https://duckduckgo.com/?q={searchTerms}", "name": "DuckDuckGo", "keyword": "DuckDuckGo" } ]

@PaulPrior trying to implement the same on 79.x and it doesn't work any way I enter the details so it is broken for sure on the browser.

 

https://getadmx.com/?Category=EdgeChromium&Policy=Microsoft.Policies.Edge::ManagedSearchEngines 

https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#managedsearchengines

 

Both of the above references are wrong or not working any way.

 

managedsearchengines.png

 

I'm having the exact same issue here. Any ideas on how to solve this?