The FSLogix Office 365 Container is a subset of the FSLogix Profile Container feature plus the ability (if acquired) to roam the Windows Search database with the user. Office 365 Containers solve the issues that Office 365 has in a roaming profile environment. Office 365 Containers can be used with any 3rd party profile solution. Also, note that roaming the Search Database in a Multi-user environment has specific Windows OS version requirements documented here. Date / Time stamps are not necessarily updated when VHD writes are complete.
Only two settings are required for the Office 365 Container feature to work: 'Enabled' and 'VHDLocations'. However, there are numerous settings available.
Local User Groups
Two local computer groups are created to control whether or not a user gets a FSLogix Office 365 Container:
- FSLogix ODFC Include List (By default includes "Everyone")
- FSLogix ODFC Exclude List - (Empty by default)
Users and groups (including Active Directory users and groups) can be added to these local groups to control which users will have their profiles in FSLogix Office 365 containers. Membership in the Exclude group overrides membership in the Include group. The following table shows whether a Office 365 container is used based on group membership:
Member of Exclude Group
Not a Member of Exclude Group
|Member of Include Group||Office 365 System Inactive||Office 365 System Active|
|Not a Member of Include Group||Office 365 System Inactive||Office 365 System Inactive|
Automatic Office 365 Container Creation
If a user is logging on and a Office 365 container is not found for the user in any of the folders specified in VHDLocations, a new container is created dynamically. A new folder whose name begins with the user’s SID will be created in the location specified in VHDLocations. A new VHD/X file is created in this folder according to the registry settings specified (SizeInMBs, and so on). The next time the user logs on, this VHD is found and attached.
Profile Container Location
The Office 365 container (VHD file) exists under the location specified by the VHDLocations registry setting. For example, if VHDLocations was set to \\server\share\ODFC, under \\server\share\ODFC there would exist a folder with a name beginning with the SID of the user, and in that folder, there would be a VHD file. The user must have Full Control permissions for this file. This is because the Office 365 VHD is typically accessed as the user that is logging on.
Pre-creating VHD/X Containers
VHD or VHDX files can be created with any tools and put in place on the network for the user’s Office 365 Container. The VHD/X should contain a formatted volume. This can save the time that an initial creation of a VHD would normally consume during logon.
The admin can configure the system to roam the Windows Search database with the Profile container.
If the system is not behaving properly, have a look at this information.