Switch on the RoamingProfileSupportEnabled policy. To enable Chrome Roaming Profile Support: In this scenario, network performance could impact Chrome’s startup time. However, it will enable you to move the Chrome profile into network storage and load it from there. This will also not allow simultaneous sessions from different machines, and it won’t save a user’s concurrent session data. Enabling Roaming Profile SupportĪ second option is to enable the Chrome Roaming Profile Support feature. It’s important to note that this approach will not allow simultaneous sessions from different machines, but it will preserve session data. This should result in faster startup times for Chrome, as less data will be copied when a user signs-on or signs-off. Then, continue using the standard Chrome user profile directory. The administrator might have to do a cleanup of older caches from the user profile folder the first time after enabling this policy as the policy does not remove the old caches. Once the policy configuration has been applied onto the machines, Chrome will start storing the cache directories into the newly defined cache folder location. This policy can be configured either via Group Policy or registry. Once the folder location has been decided, administrators need to configure the DiskCacheDir policy that relocates the cache folders. The user data directory variables can help you specify the best directory for your caches. Caches should still be in the Windows user’s directory, and keeping them in hidden directories can also reduce the risk of the cache being accidentally deleted.Įxamples of such folder shortcuts would be: The VDI administrator will need to identify a folder outside of the Chrome user profile directory where the caches will be stored. One option is for administrators to move the cache folders outside of Chrome’s user profile folder. If you can’t use Google Sync, there are a few approaches that can be used to minimize the backup size. However, there are some environments where this option isn’t suitable for technical or policy reasons. It provides the best experience for both the user and the administrator as users only need to sign in. For users, this can lead to slower startup time for Chrome.Īlthough we’ll cover different scenarios today, Google Sync is still our recommended method for syncing browser profile data between machines. This can result in an increased user profile folder backup time. VDI administrators may prefer to back up the entire Chrome user profile directory, but the more sites a user accesses, the more the size of the cache folder increases, and the number of small files in those folders can become quite large. Chrome stores all of its caches in folders in the user profile directory. This is where data is temporarily stored for faster future site loading, cookies are saved in order to provide seamless authentication on websites, extensions cache various resources, and more. Like any browser, Chrome has cache directories. For example, many ask us how to minimize backup size to speed up user log-in and log-off into the Windows environment and reduce impact on the overall user experience. As a Chrome Enterprise Customer Engineer, I often get asked by administrators of virtual desktop infrastructure (VDI) environments what our best practices are for backing up user profiles.
0 Comments
Leave a Reply. |