Does anyone use the more advanced frx commands? What use cases are supported? Hi 👋 We're moving away from the Dynamic Environment Manager by Omnissa, mostly due to heavy vibe coding needs of floating users (npm/pip packages, user installed AI IDEs etc.) and the effect it has on login/logoff times. I was wondering: a) If anyone else is going through the same shift and wants to share it's setup and gotchas b) has anyone made use of commands like frx moveto-vhd, copyto-vhd, create-junction, add-redirect the way I understand these is that a startup script would set these up before users logged in to include folders who are external to the user's profile, exampel given by Microsoft are different drives, folders on C drive. Is this correct? are there any places utilizing these? Thanks in advance 🙏

if you want to include folders in a profile that are not part of the regular profile (i.e. c:\OddFolder\Username or the like) use an FSLogix Redirection Rule to simply redirect it into the profile

Just a hypothetic scenario, never tried if it would work as a migration scenario from DEM to FSL Profile container. 1. you have your normal DEM Profile setup working 2. configure FSLogix profile container and activate it for the Users 3. at next log on container will be created, and all the dem .zip-s processed. (I am just speaking now from the application config migration) 4. so they are now saved in the profile --> vhdx 5. user logs off. 6. disable DEM 7. User logs in only with FSLogix profile container and all the settings Would this work like this?

If you're referring to my method of migration, I don't see any reason why it shouldn't be able to work for DEM as well, obviously modified to suit

@James Rankin I'm also in the process of migrating away from Omnissa DEM, and yes it's a phased approach, 1. user logs in to fslogix profiles enabled vdi 2. a gpo disables all directflex (just in time import method used in DEM) 3. this causes all profile contents to pour and be absorbed by FSL 4. simultansously a DEM admx setting changes a flag that prevent the "personalization" (the profile aspect of DEM) to occur. 5. subsequent logoff and logon does no import and export of profile, mere "user environment" manipulation like shortcuts creation, files copy etc. 6. profile is loaded from FSL, redirection exclude only low integrity location (mask 128)

Not redirections.xml