Blog Post

FSLogix Blog
1 MIN READ

FSLogix release 2105 Public Preview

Philip_McLoughlin's avatar
May 24, 2021

Hi Folks

 

Microsoft is  pleased to announce the availability of the FSLogix Preview release 2105.

 

New Public Preview: FSLogix Release 2105 (2.9.7802.10873)

 

This is a PUBLIC PREVEW release

 

To access please go to this link and complete the following form :

 

FSLogix release 2105 Public Preview 

 

After submitting the form, a download link will be provided.

 

NOTE: A certificate signing update in Windows 7 currently prevents this release from being installed on Windows 7. An upcoming Windows 7 update is expected resolve this issue.

 

The Preview Release contains the following :

 

  • Various updates were made to improve login time.
  • Fixed an issue where users could fail to login if a VHD network location was unavailable.
  • You can now increase the size of an existing VHD(x) by updating the SizeinMB setting.
  • The RefreshUserPolicy setting can now be managed via group policy template (ADMX).
  • The Installed Version of FSLogix is now written to the registry (HKLM:Software\FSLogix\Apps:InstallVersion).
  • Fixed an issue where Type4 printer drivers worked after initial configuration, but not subsequent sessions.
  • Orphaned/corrupt NST files are now cleaned up along with OST files.
  • Resolved a Cloud Cache bug where a second machine accessing the RW disk gets permanently locked out.
  • Fixed an issue compiling AppMasking rules with a destination in HKCU.
  • Fix an issue where FSLogix could cause a deadlock and prevent user connections.
  • Fixed various issues that could crash the FSLogix service.
  • Resolved an issue causing frxshell to not launch on non-English systems

 

 

Updated May 24, 2021
Version 1.0

19 Comments

  • Hi Joachim082810. I think that would be better to install the latest version and if the issue persist, open a support ticket so we can look at the logs when you are reproducing the issue.

  • vara93's avatar
    vara93
    Iron Contributor

    Hi. Please fix this bug.

     

    https://docs.microsoft.com/en-us/answers/questions/462804/fslogix-locked-credentials-folder.html

  • Joachim082810's avatar
    Joachim082810
    Copper Contributor

    Hi Gonzalo_Reyna, yes we are working with that location (type=smb,connectionString=c:\fslogix_cache;type=smb,connectionString=\\***\fslogix_nb$). Also the health providers for register & unregister is set to 1. Any hints? Best Regards Joachim

  • hi DexL66. When you configure CloudCacheLocations you need to consider that the first on the string it is intended to be the closest one to the user. Something that is absolutely correct is that the more locations that you add, you will have more delays as it will need to sync with more locations. The reason of the delay is because the one that performs the synchronization is the client itself, so we will rely on the network speed.

     

    Please look at the following documentation about Cloud Cache: FSLogix Cloud Cache configuration reference - FSLogix | Microsoft Docs

  • RichardDuffySMB's avatar
    RichardDuffySMB
    Copper Contributor

    Does anyone know when the full General Availability release is due for this version?

  • Joachim082810's avatar
    Joachim082810
    Copper Contributor

    When working offline (only first cloud cache location is available on local disk - the second is only available after connection via VPN) the logon results in an endless loop. Can't be there a timeout (< 10 seconds) to check if all cloud cache locations are available and take a retry after login every hour?

  • DexL66's avatar
    DexL66
    Copper Contributor

    I manage a Citrix environment using UPM. I recently started testing the use of FSLogix for profiles to allow the use of the Teams full client. I loved the idea of the cloud cache functionality and a hands off approach to synchronizing profiles across multiple locations without any fuss !

     

    I have Citrix servers in 4 geographical locations: 2 in the US, 1 in Europe and 1 in Asia. When I started testing, I used a single location for the servers and profiles. Everything was looking really promising. However, things fell apart as I tried to implement cloud cache across these 4 distant locations. Here are some observations on how I think things work. I have some suggestions on product enhancements to help my deployment.

     

    The profile container is created on the cloud cache location for first time user. This also seems to be the case with multiple cloud cache locations that the user logon does not complete until the profile is created and synced across all locations. I noticed that my logon times went from 40 seconds using a single location to 3-4 minutes with all four locations configured.

    What if FSLogix created a local container for a new user (fast) and worries about syncing the copies to the cloud cache locations afterwards? 

     

    For an existing profile, I saw similar behavior. The logon times increased significantly as I introduced more cloud cache locations It looks like FSLogix wants all cloud cache locations in sync before completing the logon process.

    What if FSLogix mounts the VHD from the closest cloud cache location in order to speed up the logon time. Then worry about syncing the profiles to all cloud cache locations afterwards. The FSLogix service could perform some simple ping/file transfer actions to determine which cloud cache location responds first.

     

    Maybe I am just out of my mind for trying to sync these large profiles across four distant locations.