Cannot create bookmarks in Firefox via Firefox GPO
Hi Support, I would like to deploy Firefox bookmark via GPO. I downloaded policy_templates_v1.4 from GitHub and running Firefox Quantum ESR 60.5 (64-Bit) on Windows 10 1703 64bit OS. The GPO template is imported to a client system C:\windows\PolicyDefinitions. I added Bookmarks in the local group policy but Bookmark didn't display when I launched Firefox. Please advise.
Thanks,
Kent Liu
edit: removed your data from public display, since the only thing it will attract are spam bots. you will be notified per mail once somebody replies to the thread. (philipp)
Wot philipp
Wšě wotmołwy (12)
Did you use fully qualified URLs for your bookmarks?
I modified to use FQDN URL but still no luck.
Can you go to about:config and create a string pref called browser.policies.loglevel and set it to "debug"
Then the JS console (Ctrl+Shift+J) should tell us what is going wrong...
GPOParser.jsm:HKEY_LOCAL_MACHINE WindowsGPOParser.jsm:44 GPOParser.jsm:{
"Bookmarks": [ { "Title": "Homefront", "URL": "https://homefront.wsgc.com", "Favicon": "", "Placement": "menu", "Folder": "WSI_WEB" } ]
} WindowsGPOParser.jsm:45 GPOParser.jsm:HKEY_LOCAL_MACHINE WindowsGPOParser.jsm:44 GPOParser.jsm:{
"Bookmarks": [ { "Title": "Google", "URL": "https://www.google.com/", "Favicon": "", "Placement": "toolbar", "Folder": "" } ], "Homepage": { "URL": "www.google.com", "Locked": 0 }
} WindowsGPOParser.jsm:45 PoliciesValidator.jsm:checking @[object Object]@ for type array PoliciesValidator.jsm:41 PoliciesValidator.jsm:in array, checking @[object Object]@ for type object PoliciesValidator.jsm:60 PoliciesValidator.jsm:checking @[object Object]@ for type object PoliciesValidator.jsm:41 PoliciesValidator.jsm:checking @Google@ for type string PoliciesValidator.jsm:41 PoliciesValidator.jsm:checking @https://www.google.com/@ for type URL PoliciesValidator.jsm:41 PoliciesValidator.jsm:checking @@ for type URLorEmpty PoliciesValidator.jsm:41 PoliciesValidator.jsm:checking @@ for type string PoliciesValidator.jsm:41 PoliciesValidator.jsm:checking @[object Object]@ for type object PoliciesValidator.jsm:41 PoliciesValidator.jsm:checking @www.google.com@ for type URL PoliciesValidator.jsm:41 Enterprise Policies:Invalid parameters specified for Homepage. EnterprisePolicies.js:138 BookmarksPolicies.jsm:"Bookmark to add: https://www.google.com/" BookmarksPolicies.jsm:160 Error: Error(s) encountered during statement execution: no such table: moz_hosts Stack trace: handleCompletion@resource://gre/modules/Sqlite.jsm:807:25
Sqlite.jsm:645:52
BookmarksPolicies.jsm:Error: Error(s) encountered during statement execution: no such table: moz_hosts Stack trace: handleCompletion@resource://gre/modules/Sqlite.jsm:807:25
Console.jsm:503
Key event not available on some keyboard layouts: key=“i” modifiers=“accel,alt,shift” id=“key_browserToolbox” browser.xul GET XHR http://detectportal.firefox.com/success.txt [HTTP/1.1 200 OK 16ms] GET XHR https://aus5.mozilla.org/update/3/GMP/60.5.0/20190124141046/WINNT_x86_64-msvc-x64/en-US/esr/Windows_NT%2010.0.0.0.15063.1563%20(x64)/default/default/update.xml [HTTP/1.1 200 OK 249ms] POST http://ocsp.digicert.com/ [HTTP/1.1 200 OK 23ms]
any suggestions?
Is it possible that this profile was used on an older version of Firefox and then used on a new version of Firefox?
I test out policy_templates_v1.3 and policy_templates_v1.4 on Firefox 60.2.0.esr (64 bit) but same result.
Sorry, I mean an older version of Firefox, not the template.
This error:
Error: Error(s) encountered during statement execution: no such table: moz_hosts Stack trace: handleCompletion@resource://gre/modules/Sqlite.jsm:807:25
usually happens when I profile has been used on older and newer versions of Firefox.
Can you try this on a fresh Firefox profile?
I ran the command on Firefox and it restarted Firefox. However I still didn't see the bookmarks.
Which command?
My recommendation is to use about:profiles to create a new profile. Then switch to that profile and see if the bookmarks apply.
Thanks for the suggestion. Recreate profile seems to fix the problem. How can I fix the issue in a mass rollout?
Sorry, I don't have a good answer here. This shouldn't be a problem in a mass rollout because this only happens if you upgrade and then downgrade.
We are introducing downgrade protection in Firefox 68 to prevent this in the future.