Ability to redirect specific directories to one or more specific VHDX containers. Taking the existing functionality of O365 and Profile containers but empowering administrators to define exactly which paths should be redirected and to which custom containers. Paths might be global paths such as C:\Program Data\ and would need to allow for per user abstraction/virtualisation of those directories as App Masking redirection rules provide currently.

It would be really handy if the fslogix agent would be able to perform a shrink or cleanup action on the container, either during logon or log off to help keep vhdx's to as small as possible.

Using redirections.xml to exclude folders such as cache and temporary folders. In case you exclude a folder in the xml file, only data added to the folder after the exclusion will not be kept in the profile container. But old data in an existing profile container will stay there. Then you need cleanup scripts to do that part. Why not be able to do that from redirections.xml?

Migration scipts for roaming profiles (or Citrix UPM) are discontinued. I need something to prepare migration for 600 users. Manual migration is just not possible.

The Tray Tool shows profile status and all the logs, but the status indicator at the top is ONLY for Profile status. I think there should be two status indicators, one for Profiles and one for Office Containers. Ideally the tray tool could read which component(s) are enabled and show status for only the enabled Container(s).

Allow redirected folders (Desktop, Downloads, Documents, etc) to be stored in a separate container that way the profile can be "reset" or deleted without loss of data. This would also hybrid on-prem/azure environments easier as you could leverage cloud cache for folder redirection as well.

This request is to all an administrator to specify data, that is outside of the profile, to be included in an existing container, most likely the Office Container.

As an example, an organization has a line of business application that stores user information in a folder such as c:\LOBAppName\LOBUserData. There is a desire that this data roam with the user in non-persistent environments.

Make it visible to the End-Users when hovering over de systray-application in WHICH mode te Profile-container is mounted. At the moment this is not possible to see if this is in ReadWrite-mode or Read-Only mode. And this can be important to know for the end-user.
I assume the application knows in which mode it is working, so it must be easy to make this available via a tool-tip when hovering over the systray-application.
Thanks,
Chris Marreel

In other words "how to restrict standard users to basic view?"

Users could view other users logoff time in the operational view.

Besides disabling frxtray completely is there any workaround like permissions on a registry key?