Blog Post

FSLogix Blog
2 MIN READ

FSLogix v3 Release 25.XX is now in Early Access!

Jason_Parker's avatar
Jason_Parker
Icon for Microsoft rankMicrosoft
Dec 04, 2024

Are you interested in the next release of FSLogix? Join the early access program and help test and provide direct feedback to the product team.

It has been quite some time (about two years) since we released a new version of FSLogix that wasn't just a hotfix. This delay led many to wonder if the product was abandoned or no longer under development. Although it took longer than expected to release this version, we prioritized aligning our product's functionality with other Microsoft products that our customers rely on, such as Microsoft Teams.

 

While this version may not be packed with numerous flashy new features, we have made significant updates and improvements to enhance overall stability. With this release, we are committed to continued investment in our early access program, ensuring that our members can always be at the forefront as we plan for future updates.

Joining the early access program is easy but requires an existing NDA:
  1. Sign up for an NDA with Microsoft
  2. Register to join the Microsoft Management Customer Connection Program (https://aka.ms/joinccp)
    • Submitting a request to join the MM CCP will validate if you have an existing NDA.
    • If you don't have an NDA, you will need to work with your Microsoft representative to sponsor your NDA.

Release Notes

These release notes are considered to be in draft until the general availability release and are subject to change.

What's New

  • Major version change (2 → 3) and updated how FSLogix release names and build versions are defined. In future releases, major releases will increment the major version from 3 to 4 to 5, etc.
    • Example
      • Release name: 25.02
      • Build version:  3.25.211.8452 (3.YY.MMDD.HHMMS)
  • Cloud Cache no longer assumes some failure states are a bad configuration and will now allow customers to test and validate their configurations for redundancy through any method they choose.
  • Microsoft.FSLogix PowerShell module used for Cloud Cache investigation and troubleshooting.
  • When unconfigured, redirections.xml is now removed from the user's profile container.

Fixed issues

  • LocalCache and TempState folders for MSIX packages are now properly cleaned up during sign-out.
  • VHD disk compaction for differencing disks now works the same as disks without a differencing disk.
    • NOTE: Compaction results will still be based on each disk and what space is able to be reclaimed during the optimization.
  • ADMX templates have been updated to allow settings that are enabled by default to be disabled.
  • Sign-in and sign-out optimizations to ensure MSIX settings are properly handled before and after the Windows shell events.

NOTE: This is most notable when reviewing text logs

===== Begin Session: Post Profiles Logon
===== End Session: Post Profiles Logon
===== Begin Session: Pre Profiles Logoff
===== End Session: Pre Profiles Logoff

Feature retirements

  • No support for Windows 7 or Server 2012 R2
  • No support for 32-bit versions of Windows
  • Limited cache for Cloud Cache (aka CcdMaxCacheSizeInMBs)
  • Profile configuration tool
  • VHD application containers
  • Browser plug-in
  • App Rule Set license reporting
  • Java Rule Set Editor
  • frxtray.exe
Updated Dec 05, 2024
Version 4.0
  • vara93's avatar
    vara93
    Iron Contributor
    • LocalCache and TempState folders for MSIX packages are now properly cleaned up during sign-out.

    Hi. Is this problem related to the local_username folder hanging when logging out? Tell us in more detail how you fixed it. You said that this is a problem with other applications, not with FSLogix. I am very glad that after 4 years, you have fixed it.

     

    Jason_Parker 

  • cmarreel's avatar
    cmarreel
    Copper Contributor

    Jason_Parkerextra Enhancement Request for the (near future) : An option (e.g. in the Redirections.xml-file) to ERASE the content of the folder you add to the Redirections.xml file.  If you don't take action the original content of such a folder STAYS in the users' VHDX-fle.  En example: I come to a setup where they suffer with VERY BIG VHDX-files, I analysed the situation and I have ADDED extra (big) folders to the redirections.xml-file.  And the VHDX-files don't grow anymore... but we need a maintenance-moment to 'process' all the profile-containers to ERASE these BIG folders from profile-containers.

    If there would be an option in the Redirections.xml-file so these folders could be emptied before creating the redirection-link.

    Thanks for considering this in a near future-release.

  • cmarreel's avatar
    cmarreel
    Copper Contributor

    Jason_ParkerIn the past I asked the possibility to give end-user-feedback when hoovering over the FRXTray.exe tool to indicate to the end-user if the mount was in READ/WRITE or READ-ONLY mode.  I love to keep my end-users informed, but at this moment an end-users has NO CLUE if his session has RW or RO access to his VHDX-container....

    Is there some kind of equivalent to the FRXTray.exe tool ?  I see it is in the list of retired features ... why stop a good feature ?  And why not enhance it to a small tool with addititional features ?

  • cmarreel's avatar
    cmarreel
    Copper Contributor

    Jason_Parker: Enhancement request (for the new V3) : can we redirect a specific FILE using the "Redirections.xml"-file ?  If I'm correct at this moment we only  could redirect a whole FOLDER.  

  • Confidle's avatar
    Confidle
    Copper Contributor

    Is the OneDrive signin-problem on server 2019 fixed in this version?

    https://www.reddit.com/r/fslogix/comments/1djj3fc/fslogix_x_onedrive_sharepoint_sync_best_practice/

    • ZeroDay2's avatar
      ZeroDay2
      Copper Contributor

      Every monday ours users have to login twice, because OneDrive is stuck in a "Signing in" loop.
      Citrix non persistent VDI,  Server 2019, happens since FSLogix HF4. Im happy to send logs for troubleshooting

      • KjetilS's avatar
        KjetilS
        Copper Contributor

        Same here also. Would be good know if this fixes this. 

  • cfarrington's avatar
    cfarrington
    Copper Contributor

    With the 1001 issues that seemed to plague multiple versions of FSLogix does this new version finally resolve this?

    • Jason_Parker's avatar
      Jason_Parker
      Icon for Microsoft rankMicrosoft

      Hi cfarrington - Can you please provide more details about this "1001" error.  This is not a known issue related to FSLogix that I am aware of. If this is a known issue caused by FSLogix, I would like to better understand it so that we can log a proper bug and prioritize it.

      • Nicholas's avatar
        Nicholas
        Copper Contributor

        Jason_Parker, Please see the "FIX" in this link. https://answers.microsoft.com/en-us/outlook_com/forum/all/outlook-365-app-error-1001-on-rds-environment/e6ae8598-81a0-4859-846a-d9509b246bf4?page=24

        I am in the MSP space and we are also seeing more and more ODFC (office) activation, sign in issues with FSLogix containers. I am currently looking at this issue with a client. It would be fantastic if FSL and Office teams can get together to document actual configuration guidelines for office installs. 

        The question I have for you and the FSL team is this:

        With what MS support provided and what is documented in the "FIX". What should we be setting or best outcome for MS office products in the FSL space? Or is just enabling a default install along with "Roam Identity" sufficent. I read about enabling "Hybrid Join", Single Signon, ADAL, WAM.. so many things to consider. 

        Please read over the "FIX" from MS support and provide feedback for proper Office Enterprise Apps + FSL best practices for roaming identity and roam activation for office.

  • piatti's avatar
    piatti
    Copper Contributor

    Thanks for the major version upgrade.

    >When unconfigured, redirections.xml is now removed from the user's profile container.
    Could you please elaborate on this?
    Does this mean that files or folders excluded by redirections.xml will be removed from the user profile container?

    • swissbuechi_'s avatar
      swissbuechi_
      Copper Contributor

      I don't think so. Please see my explanation below:

      If you configure a path to a redirections.xml, the file will actually be copied to the user profile on every logon. Previously, if you removed the registry configuration to not point to a redirections.xml anymore, the .xml file already copied to the user profile, will persist and therefore stay active. You'd have to manually remove the file from each user's profile container.

      With the new behavior of automatically removing the redirections.xml from the user's profile container, this manual cleanup step is not necessary anymore.

  • FMCUjonesc's avatar
    FMCUjonesc
    Copper Contributor

    We are leveraging the CcdMaxCacheSizeInMBs and frxtray.exe settings. Are there planned alternatives or should we revert those settings before deploying this release, once it goes GA?

    • Jason_Parker's avatar
      Jason_Parker
      Icon for Microsoft rankMicrosoft

      You should stop using CcdMaxCacheSizeInMBs before the product GA's.

      As for frxtray, not sure what part of this tool you used it for, but here is what we recommend:

      • Determine VHD mount status and size using Disk Management console
      • Determine if FSLogix is redirecting the profile path to a VHD use frx.exe list-redirects
      • Review log files by navigating to: %ProgramData%\FSLogix\Logs
      • Review event logs using the Event Viewer console