Microsoft Profile Containers

With Microsoft Profile Containers Integration, it is possible to redirect Microsoft Profile Containers (formerly known as FSLogix) to a network location. Profiles are placed in VHDX files and mounted at run time.
This integration allows you to manage VHDX Cache roaming in a non-persistent VDI environment from the Ivanti Workspace Control Console.

The Microsoft Profile Container agent must be installed and running on the client computer.
More information on Microsoft Profile Containers can be obtained from the Microsoft website.

This feature is in development. Ivanti kindly invites you to provide feedback.

Where to find Microsoft Profile Containers Integration

What	Where
Setting up integration with Microsoft Profile Containers	Go to Setup > Integration > Microsoft Profile Containers

Configuration

The Settings tab contains the default configuration for all Zones.

• If you Enable Microsoft Profile Containers Integration, this will overwrite existing configuration on the agent.
• Container mode: Select the desired mode.
  • Profile Containers: The entire profile will be included.
  • Office Containers: Microsoft Office applications can be included or excluded individually.
    Regardless of configuration, Windows Search will always be included.
• VHDX location: Specify a shared location (UNC path) where VHDX files will be stored.
  • When including variables in the UNC path, you can only use system variables.
    Example: \\host-name\share-name\%computername%
  • Although Microsoft supports VHDX files as well as the older VHD files, this integration only supports the more modern VHDX files.
  • The UNC path must be accessible from the client computers.
  • Users must have modify permissions for the shared location, so that VHDX files can be written.
• Applications to include: Specify the applications to include in the container. Only available if Container Mode is set to Office Containers.
• Access Control: Specify the users to whom the settings apply. By default, the settings apply to all users.

Workspace exceptions

Please note that when configuring a workspace exception, you should only use machine-based Workspace Containers.