Forum Discussion
Automate Edge-Favorites Backup as HTML-File
As there is no Solution provided by Microsoft, I created a Script (as a workaround). I published it here: https://github.com/gunnarhaslinger/Microsoft-Edge-based-on-Chromium-Scripts
Elliot Kirk the Export/Import is not running as a system-restore or system-process, it is an Automated (daily) User-Backup running as automated Process executed in User-Context (typically before User-LogOff). But LocalAppData-Folder is not covered in the User-Backup (AppData\Roaming would be) and LocalAppData is way too big to include. Just the Bookmarks should be included.
Current Solution with old EdgeHTML is the Tool EdgeBackup which exactly does this - it can be executed to export the EdgeHTML Bookmarks to an HTML-File and put this HTML-File in the UserDataBackup of the machine.
If the User needs to restore the Bookmarks (e.g. because of moving to a new Computer) this can be done by the User manually. The HTML-File can be restored in any Browser (EdgeHTML, EdgeChromium, Firefox) we use.
Syncing with cloud is not an option, the Networks the Machines are connected to are air-gapped (no direct Ontenet-Access). Browser is used for Intranet-AccessOnly. And even if there would be Internet-Access, our Policy says users must not use these Cloud-Services.
Had_Robinson where did you find something in the script which needs an Update? Just tested with Microsoft Edge 96.0.1054.26 beta and I couldn't spot any problems.
Here is the version I'm running: Version 96.0.1054.29 (Official build) (64-bit)
line 5 in the Script is this: $JSON_File_Path = "$env:localappdata\Microsoft\Edge Beta\User Data\Default\Bookmarks"
On my systems (Win 8 & 10) Bookmarks is stored here:
C:\Users\***\AppData\Local\Microsoft\Edge\User Data\Default
The Edge I'm using is not a Beta, so e.g., line 5 should be: $JSON_File_Path = "$env:localappdata\Microsoft\Edge\User Data\Default\Bookmarks"
Maybe I missed something?
It is a puzzle why MS did not automate backups of Favorites....
- Of course you have to Edit Source- and Destination-Path to your personal requirements. For Edge-prod-Environment the Path is not "Edge Beta" but "Edge". Most of us IT-Pro's are running Beta in addition to Prod/Stable to check out troubles before they hit our users - so I preferred to put in "Edge Beta". But nothing changed since I developed this small script, everything works unchanged like in the first version.