By default the Profile Container will contain the entire Windows Profile for the user, except for the TEMP (TMP) folder location and the IE Cache folder location. The Windows user profile is comprised of the contents of a specific folder location and some registry information. Typically this folder location is something like, "C:\Users\<username>".
If desired, the admin can specify that certain parts of the user profile not be persisted in the Profile Container and that they be deleted on user logoff. This is done by deploying a redirections.xml which instructs the FSLogix agent to redirect specific folders out of the Container and into the local C: drive where they are removed on user logoff.
When a user logs on and a FSLogix Profile container is connected and used by that user, you will see two additional folders in the C:\Users directory: a "<username>" folder (or some variation) and a "local_<username>" folder. The "<username>" folder is really a link into the Profile Container. FSLogix advanced redirection capabilities make the contents of the Profile Container look as if they really exist at this location. The second folder, "local_<username>", is a real folder on the C:.
At user logoff, the <username> redirect will disappear and the "local_<username>" folder is lazily deleted by the FSLogix service.
The redirections.xml file is used to control what folders are redirected out of the Profile Container to the C: drive. It can also optionally sync the contents of these folders to and from the Profile Container at user logoff and logon respectively.
The redirections.xml file resides in the Profile Container in the <ProfileRoot>\AppData\Local\FSLogix folder
The admin can use the built-in distribution capabilities of the FSLogix agent or any other mechanism to simply place the file into the Profile Container. To use the built-in copy mechanism, use the "RedirXMLSourceFolder" setting. At user logon, the FSLogix agent will copy the redirections.xml file from the specified location (if it exists) and process it immediately. The user must have Read permissions to the file.
Structure of the File
The basic structure of the redirections.xml document is as follows:
<?xml version="1.0" encoding="UTF-8"?>
<Exclude>… another exclude folders… </Exclude>
<Include>… another include folders… </Include>
Folders are relative to the user profile root (That’s why "AppData" is shown in this example).
You can put any number of entries inside the Includes and Excludes tags.
Exclude folders are redirected out of the container to the C: drive and include folders are used when certain folders should remain in the Profile Container. Include entries are used to redirect a folder back into the container when a parent folder has been redirected out of the container.
###VALUE### should be replaced with one of the following values:
0 = No files copied in or out. (Note: the copy tag may be left out entirely and the action will be the same as setting to 0. Only the folder(s) are created on the local_<user_name> directory.)
1 = Copy files to base. Any existing file in an excluded folder will be copied to base.
2 = Copy files back to virtual profile. Any modified file in base will be copied back to profile on user logout.
3 = Files are copied from/to base. Combinations options 1 and 2.
The redirections.xml file is processed at user logon. If the file is updated while the user is logged on, the changes will be reflected at the next logon.