Google Chrome Bookmarks not persisting each session may be the result of several factors. This may differ between Non-persistent VDI as well as physical or with ProfileDisk in use.
The goal of this article is to outline some possible known scenarios and solutions to address.
Problem:
Users Google Chrome bookmarks do not persist between sessions.
Symptom:
There could be a few reasons for Chrome bookmarks to not restore, the below is some possible symptoms or scenarios.
**Here is an example scenario where the Chrome Bookmarks are missing but ProfileUnity actually did restore them from Archive.
1. User login with Chrome version 86 profile and bookmarks are restored
2. During session Chrome auto updates to version 87
3. At logoff Chrome 87 version of profile is saved in Archive
4. Next login Chrome version 86 (as the default version on system) loads but archive from previous logout was 87
5. Chrome rejects the newer Profile version as it's from a version is has not yet been upgraded too.
** In addition there can be scenarios where Chrome auto update is not an issue but the user is opening Chrome on desktop before any Chrome post login archive restore is completed. In early versions and Chrome portability rule, the rule was set to post login for restore. This can be set to restore during login versus post.
**Its possible if the user logs in and has a incorrect or bad bookmarks file, the logoff could overwrite the current archive. In a case like this (once you have addressed whether issue is auto update or perhaps post login issue) you might have to restore an archive from back to re-insert into the system. You can add Portability Retention as outlined below
Possible Resolution(s):
Chrome as a FlexApp or using Chrome in the Parent image
If Chrome is a Flexapp or if you add Chrome to the parent image you will want to turn off auto updates. You can find more information here on how to accomplish via GPO.
https://support.google.com/chrome/a/answer/6350036?hl=en
General Portability Rule to adhere too.
1. Check and make sure your Chrome portability rule is set to "NOT" be post login.
2. Adding Retention for portability. In your config under the Main module at the bottom. there is an option to add the number of archive to retain as an option or allowing for restore of a previous archive.
From help bubble in ProfileUnity main module section
Portability Archive Retention:
The maximum number of copies of user portability settings to keep. A user's portability settings are saved at session logoff. Copies of archives and manifests will be saved to a Retention folder under where user settings are stored. Any or all of the copies may be used as a restore point to restore a user's settings to a previous state. The default is 0 which will not retain any archives.
Physical/ProfileDisk
In conjunction with the above, for Physical and ProfileDisk, make sure the portability rule for Chrome (in general) is set to restore only once with a local tracking path.
Product: ProfileUnity
Product Version: 6.8.x