Manage transactional folders 编辑

A transactional folder refers to a folder that contains interdependent files, where one file references other files. The Folders to mirror policy ensures the integrity of transactional folders during profile synchronization. With this policy, Profile Management mirrors the entire transactional folder between the user store and the local user profile.

The Accelerate folder mirroring policy is available with Profile Management 2106 and later.

How the folder mirroring works

Generally, when Profile Management synchronizes user profiles between the user store and the local profiles, it synchronizes only updated files by comparing time stamps. However, in a transactional folder, files in it are associated, and Profile Management must synchronize the entire folder to avoid integrity issues. An example of transactional folders is a folder that contains transaction log files and the corresponding database files. Mixing transaction log files and database files from different sessions can cause transactional integrity issues.

To synchronize transactional folders correctly, Profile Management provides the Folders to mirror policy. When synchronizing a transactional folder to the destination, Profile Management mirrors the folder to the destination by using the following steps:

1. Copies all contents in the folder to the destination, ignoring time stamps.
2. Deletes any additional contents in the destination.

Caution:

Mirroring transactional folders means the “last write wins.” Files that are modified in more than one session are overwritten by the latest update and profile changes might be lost.

Specify folders to mirror

Enable the Folders to mirror policy and specify the folders to mirror.

Let’s take Google Chrome as an example. The bookmark-related files and subfolders in AppData\Local\Google\Chrome\User Data\Default are interdependent and must be processed as a whole during profile synchronization. To achieve this goal, you need to add this folder to the Folders to mirror policy.

You can also exclude files and subfolders from a folder to mirror. In the previous example, the AppData\Local\Google\Chrome\User Data\Default folder also contains files and subfolders unrelated to bookmarks. You can use the Exclusion list – directories and Exclusion list – files policies to exclude them.

Detailed steps are as follows:

1. Go to Profile Management > File system > Synchronization, and then double-click the Folders to mirror policy.

2. Select Enabled.

3. In the List of folders to mirror field, type the list of folders that you want to mirror in the format of relative paths to the user store. Type Enter to separate folders.

   Note:

   This policy works recursively. Don’t add subfolders to the list.

   For example, if you add AppData\Roaming\Microsoft\Windows\Cookies, don’t add AppData\Roaming\Microsoft\Windows\Cookies\Low.

4. Click OK.

5. To exclude certain files and subfolders in a mirrored folder from the mirroring process, follow these steps:

   1. Go to Profile Management > File system, and then double-click the Exclusion list – directories policy or the Exclusion list – files policy.

   2. Specify thee files and subfolders to exclude.

Configuration precedence:

1. If this policy isn’t configured here, the value from the .ini file is used.

2. If this setting is configured neither here nor in the .ini file, no folders are mirrored.

Accelerate folder mirroring

Starting with Profile Management 2106, you can accelerate folder mirroring by enabling the Accelerate folder mirroring policy.

With this policy enabled, Profile Management stores mirrored folders on a VHDX-based virtual disk. Profile Management attaches the virtual disk during logons and detaches it during logoffs, eliminating the need to copy the folders between the user store and the local profiles.

To enable this policy, follow these steps:

1. Under Profile Management > File system > Synchronization, double-click the Accelerate folder mirroring policy.

2. Select Enabled.

3. Click OK.

Configuration precedence:

1. If this policy isn’t configured here, the value from the .ini file is used.

2. If this setting is configured neither here nor in the .ini file, the policy is disabled.