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.

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.

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?

It would be great to be able to increase the maximum size of an already existing VHDX-profile without first having to remove the old profile or migrating to a new profile.

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.

In Citrix MCS/PVS environments the cache gets filled too fast, so we need an opportunity to put it the redirected folders on a cache drive.

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.

full automation abilities so everything in FSLogix can be scripted.
This can provide scale around new deployments and a enable the move to a full devops deployment and management of WVD Session Hosts.

With the new model of App Attach, User Profiles and OS Images as 3 separate parts of the whole solution we will need to build at scale and deploy with scripts and templates, which means the need for 100% automation of the solution, end to end.
This requires that everything is scriptable.

it would be great to be able to use the same profile for Windows 10 an Server 2019. The users could use the same profile for their Windows 10 Workstation and Server 2019 Remote Desktop Session Host with the same Settings.

I would like to get the FSLogix client updates delivered via WSUS / Windows updates.

To effectively troubleshoot and manage hundreds of VHDs there should be tooling to list contents to see why it's ballooning, check the startup and desktop folders, selectively delete certain parts, scan for white space then defrag the disk, repair corruption etc. Even when the user is actively using the VHD file. There are some elaborate homebrew Powershell scripts but nothing official.

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.

Currently we have to setup an additional High-Available VM cluster if we want the profile containers to be available in a SLA approved way whenn we use file shares.

It would be great if we could use Azure Storage to host this fileshare instead of an additional (set of ) vm(s).

An option to compact FSLogix dynamic VHDs

As a former Citrix upm customer, is it possible to add registry exclusions like UPM has?

When a container is becoming corrupt we are finding that the VHD/VHDX is stuck on 0MB and is pretty much useless. Rather than troubleshooting/manually deleting the container it would be good if a GPO could attempt to re-create a fresh container on logon rather than mounting the same container that is obviously corrupt.

If a there was a configurable GPO that could for example delete and re-create any container that was <500mb then it would fix the corrupt container itself by re-creating it.

It's not clear how to migrate a lot of on-premise local profiles to FSLogix container. We need tools and documentation about best practice of different kind of migration.

Teams creates directories with SIDS that change and we cannot redirect or exclude