FSLogix 2201 Public Preview Update 1 is now available

%3CLINGO-SUB%20id%3D%22lingo-sub-3211289%22%20slang%3D%22en-US%22%3EFSLogix%202201%20Public%20Preview%20Update%201%20is%20now%20available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3211289%22%20slang%3D%22en-US%22%3E%3CDIV%20class%3D%22lia-message-subject-wrapper%20lia-component-subject%20lia-component-message-view-widget-subject-with-options%22%3E%0A%3CDIV%20class%3D%22MessageSubject%22%3E%0A%3CDIV%20class%3D%22MessageSubjectIcons%20%22%3EHi%20Everyone%2C%3C%2FDIV%3E%0A%3CDIV%20class%3D%22MessageSubjectIcons%20%22%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-message-unread%20lia-message-unread-windows%22%3EWe've%20just%20released%20FSLogix%202201%20Public%20Preview%20Update%201%20to%20address%20the%20previously%20announced%20issue%20impacting%20customers%20who%20allow%20users%20to%20have%20multiple%20Windows%20sessions%20per%20session%20host.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20recap%20the%20resolved%20issue%2C%20customers%20who%20allow%20users%20to%20login%20to%20multiple%20Windows%20sessions%20per%20host%20encountered%20a%20bug%20that%20allowed%20the%20first%20user%20session%20to%20connect%2C%20but%20additional%20session%20launches%20failed.%20With%20this%20update%2C%20additional%20sessions%20will%20no%20longer%20fail.%26nbsp%3B%20Your%20environment%20was%20impacted%20if%20you%20have%20the%20%22Restrict%20Remote%20Desktop%20Services%20users%20to%20a%20single%20Remote%20Desktop%20Services%20Session%22%20group%20policy%20set%20to%20disabled%20or%20the%20HKLM%3A%5CSoftware%5CPolicies%5CMicrosoft%5CWindows%20NT%5CTerminal%20Services%5CfSingleSessionPerUser%20regkey%20value%20is%20set%20to%200.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3C%2FDIV%3E%0A%3CDIV%20id%3D%22bodyDisplay%22%20class%3D%22lia-message-body%20lia-component-message-view-widget-body%20lia-component-body-signature-highlight-escalation%20lia-component-message-view-widget-body-signature-highlight-escalation%22%3E%0A%3CDIV%20class%3D%22lia-message-body-content%22%3E%0A%3CP%3E%3CSTRONG%3EPreview%20Details%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3ENOTE%3A%20Existing%20public%20preview%20participants%20do%20not%20need%20to%20sign%20up%20again.%20A%20new%20download%20link%20will%20be%20sent%20to%20the%20provided%20email%20address.%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3EYou%20can%20sign%20up%20here%20to%20participate%20in%20the%20Public%20Preview%20here%3A%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Faka.ms%2Ffslogix%2Fpreview%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Faka.ms%2Ffslogix%2Fpreview%3C%2FA%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20release%20can%20be%20installed%20over%20all%20existing%20versions%20of%20FSLogix%20or%20you%20can%20perform%20a%20fresh%20install%20without%20a%20pre-existing%20FSLogix%20version.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EHere's%20a%20complete%20list%20of%20updates%20in%20the%202201%20Public%20Prevew%3A%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSTRONG%3EUpdate%201%20Changes%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EResolved%20an%20issue%20in%20the%20initial%202201%20Public%20Preview%20release%20that%20prevented%20additional%20connections%20for%20environments%20configured%20to%20allow%20users%20to%20have%20more%20than%20one%20Windows%20session%20per%20host.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3E%3CSTRONG%3EPreviously%20Announced%20Changes%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3EFixed%20issue%20where%20the%20FSLogix%20Profile%20Service%20would%20crash%20if%20it%20was%20unable%20to%20communicate%20with%20the%20FSLogix%20Cloud%20Cache%20Service.%3C%2FLI%3E%0A%3CLI%3EThe%20OfficeFileCache%20folder%20located%20at%20%25LOCALAPPDATA%25%5CMicrosoft%5COffice%5C16.0%5COfficeFileCache%20is%20now%20machine%20specific%20and%20encrypted%20so%20we%20now%20exclude%20it%20from%20FSLogix%20containers.%20Office%20files%20located%20outside%20this%20folder%20are%20not%20impacted%20by%20this%20update.%3C%2FLI%3E%0A%3CLI%3EWindows%20Server%202019%20version%201809%2C%20and%20newer%20versions%20of%20Windows%20Server%2C%20natively%20support%20per-user%20search%20indexes%20and%20we%20recommend%20you%20leverage%20that%20native%20search%20index%20capability.%20FSLogix%20Search%20Indexing%20is%20no%20longer%20available%20on%20those%20versions%20of%20Windows%20Server.%3C%2FLI%3E%0A%3CLI%3EWindows%2010%20Enterprise%20Multi-session%20and%20Windows%2011%20Enterprise%20Multi-session%20natively%20support%20per-user%20search%20indexes%20and%20FSLogix%20Search%20Indexing%20is%20no%20longer%20available%20on%20those%20operating%20systems.%3C%2FLI%3E%0A%3CLI%3EFSLogix%20now%20correctly%20handles%20cases%20where%20the%20Windows%20Profile%20Service%20refCount%20registry%20value%20is%20set%20to%20an%20unexpected%20value.%3C%2FLI%3E%0A%3CLI%3EOver%2030%20accessibility%20related%20updates%20have%20been%20made%20to%20the%20FSLogix%20installer%20and%20App%20Rules%20Editor.%3C%2FLI%3E%0A%3CLI%3EA%20Windows%20event%20now%20records%20when%20a%20machine%20locks%20a%20container%20disk%20with%20a%20message%20that%20looks%20like%20%22This%20machine%20'%5BHOSTNAME%5D'%20is%20using%20%5BUSERNAME%5D's%20(SID%3D%5BUSER%20SID%5D)%20profile%20disk.%20VHD(x)%3A%20%5BFILENAME%5D.%22%3C%2FLI%3E%0A%3CLI%3EResolved%20an%20issue%20where%20the%20DeleteLocalProfileWhenVHDShouldApply%20registry%20setting%20was%20sometimes%20ignored.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20active%20user%20session%20settings%20where%20not%20retained%20if%20the%20FSLogix%20service%20was%20restarted.%20This%20was%20causing%20some%20logoffs%20to%20fail.%3C%2FLI%3E%0A%3CLI%3EFSLogix%20will%20no%20longer%20attempt%20to%20reattach%20a%20container%20disk%20when%20the%20user%20session%20is%20locked.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20that%20caused%20the%20FSLogix%20service%20to%20crash%20when%20reattaching%20container%20disks.%3C%2FLI%3E%0A%3CLI%3EFixed%20a%20Cloud%20Cache%20issue%20that%20caused%20IO%20failures%20if%20the%20session%20host's%20storage%20blocksize%20was%20smaller%20than%20a%20cloud%20provider's.%20For%20optimal%20performance%2C%20we%20recommend%20the%20session%20host%20disk%20hosting%20the%20CCD%20proxy%20directory%20has%20a%20physical%20block%20size%20greater%20than%20or%20equal%20to%20the%20CCD%20storage%20provider%20with%20the%20largest%20blocksize%20size.%3C%2FLI%3E%0A%3CLI%3EFixed%20a%20Cloud%20Cache%20issue%20where%20a%20timed%20out%20read%20request%20(network%20outage%2C%20storage%20outage%2C%20etc.)%20was%20not%20handled%20properly%20and%20would%20eventually%20fail.%3C%2FLI%3E%0A%3CLI%3EReduced%20the%20chance%20for%20a%20Cloud%20Cache%20container%20disk%20corruption%20if%20a%20provider%20is%20experiencing%20connection%20issues.%3C%2FLI%3E%0A%3CLI%3EResolved%20an%20issue%20where%20temporary%20rule%20files%20were%20not%20deleted%20if%20rule%20compilation%20failed.%3C%2FLI%3E%0A%3CLI%3EPreviously%2C%20the%20Application%20masking%20folder%20was%20only%20created%20for%20the%20user%20who%20ran%20the%20installer.%20With%20this%20update%2C%20the%20rules%20folder%20is%20created%20when%20the%20Rules%20editor%20is%20launched.%3C%2FLI%3E%0A%3CLI%3EResolved%20an%20interoperability%20issue%20with%20large%20OneDrive%20file%20downloads%20that%20was%20causing%20some%20operations%20to%20fail.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20per-user%20and%20per-group%20settings%20did%20not%20apply%20if%20the%20Profile%20or%20ODFC%20container%20was%20not%20enabled%20for%20all%20users.%3C%2FLI%3E%0A%3CLI%3EResolved%20an%20issue%20where%20the%20Office%20container%20session%20configuration%20was%20not%20cleaned%20up%20if%20a%20profile%20fails%20to%20load.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20HKCU%20App%20Masking%20rules%20leveraging%20wildcards%20would%20fail%20to%20apply.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20where%20FSLogix%20did%20not%20properly%20handle%20logoff%20events%20if%20Profile%20or%20ODFC%20containers%20were%20disabled%20during%20the%20session%20or%20per-user%2Fper-group%20filters%20were%20applied%20mid-session%20that%20excluded%20the%20user%20from%20the%20feature.%20Now%20FSLogix%20logoff%20related%20events%20will%20always%20occur%20if%20FSLogix%20loaded%20a%20container%20for%20the%20user.%3C%2FLI%3E%0A%3CLI%3EFixed%20an%20issue%20that%20caused%20some%20sessions%20configured%20with%20an%20ODFC%20container%20to%20fail%20to%20login.%3C%2FLI%3E%0A%3CLI%3E%26nbsp%3BResolved%20an%20issue%20where%20the%20rule%20editor%20would%20crash%20if%20there%20were%20no%20assignments%20configured.%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3C%2FDIV%3E%0A%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3212057%22%20slang%3D%22en-US%22%3ERe%3A%20FSLogix%202201%20Public%20Preview%20Update%201%20is%20now%20available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3212057%22%20slang%3D%22en-US%22%3EWas%20the%20profile%20deletion%20issue%20addressed%3F%3CBR%20%2F%3ECan%20we%20now%20redirect%20logs%20using%20the%20GPO%20setting%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3249956%22%20slang%3D%22en-US%22%3ERe%3A%20FSLogix%202201%20Public%20Preview%20Update%201%20is%20now%20available%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3249956%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F116512%22%20target%3D%22_blank%22%3E%40Steve%20Downs%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%20after%20tested%20FSlogix%20for%20some%20time%20we%20get%20issues.%26nbsp%3B%3C%2FP%3E%3CP%3EVersion%3A%3C%2FP%3E%3CP%3EFSLogix_Apps_2.9.8089.44141%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESee%20that%20logoff%20freeze%20for%20users%20and%20I%20never%20get%20this%20in%20logs%3A%3C%2FP%3E%3CP%3E%22Begin%20Session%3A%20Unload%20profile%22%3C%2FP%3E%3CP%3EWorks%20if%20admin%20do%20a%20manual%20logoff%20direct%20on%20server%20the%20session%20running.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20help%20for%20this%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft
Hi Everyone,

We've just released FSLogix 2201 Public Preview Update 1 to address the previously announced issue impacting customers who allow users to have multiple Windows sessions per session host.

 

To recap the resolved issue, customers who allow users to login to multiple Windows sessions per host encountered a bug that allowed the first user session to connect, but additional session launches failed. With this update, additional sessions will no longer fail.  Your environment was impacted if you have the "Restrict Remote Desktop Services users to a single Remote Desktop Services Session" group policy set to disabled or the HKLM:\Software\Policies\Microsoft\Windows NT\Terminal Services\fSingleSessionPerUser regkey value is set to 0.

 

Preview Details

NOTE: Existing public preview participants do not need to sign up again. A new download link will be sent to the provided email address.

You can sign up here to participate in the Public Preview here:

https://aka.ms/fslogix/preview

 

This release can be installed over all existing versions of FSLogix or you can perform a fresh install without a pre-existing FSLogix version.

 

Here's a complete list of updates in the 2201 Public Prevew:

 

Update 1 Changes

  • Resolved an issue in the initial 2201 Public Preview release that prevented additional connections for environments configured to allow users to have more than one Windows session per host.

Previously Announced Changes

  • Fixed issue where the FSLogix Profile Service would crash if it was unable to communicate with the FSLogix Cloud Cache Service.
  • The OfficeFileCache folder located at %LOCALAPPDATA%\Microsoft\Office\16.0\OfficeFileCache is now machine specific and encrypted so we now exclude it from FSLogix containers. Office files located outside this folder are not impacted by this update.
  • Windows Server 2019 version 1809, and newer versions of Windows Server, natively support per-user search indexes and we recommend you leverage that native search index capability. FSLogix Search Indexing is no longer available on those versions of Windows Server.
  • Windows 10 Enterprise Multi-session and Windows 11 Enterprise Multi-session natively support per-user search indexes and FSLogix Search Indexing is no longer available on those operating systems.
  • FSLogix now correctly handles cases where the Windows Profile Service refCount registry value is set to an unexpected value.
  • Over 30 accessibility related updates have been made to the FSLogix installer and App Rules Editor.
  • A Windows event now records when a machine locks a container disk with a message that looks like "This machine '[HOSTNAME]' is using [USERNAME]'s (SID=[USER SID]) profile disk. VHD(x): [FILENAME]."
  • Resolved an issue where the DeleteLocalProfileWhenVHDShouldApply registry setting was sometimes ignored.
  • Fixed an issue where active user session settings where not retained if the FSLogix service was restarted. This was causing some logoffs to fail.
  • FSLogix will no longer attempt to reattach a container disk when the user session is locked.
  • Fixed an issue that caused the FSLogix service to crash when reattaching container disks.
  • Fixed a Cloud Cache issue that caused IO failures if the session host's storage blocksize was smaller than a cloud provider's. For optimal performance, we recommend the session host disk hosting the CCD proxy directory has a physical block size greater than or equal to the CCD storage provider with the largest blocksize size.
  • Fixed a Cloud Cache issue where a timed out read request (network outage, storage outage, etc.) was not handled properly and would eventually fail.
  • Reduced the chance for a Cloud Cache container disk corruption if a provider is experiencing connection issues.
  • Resolved an issue where temporary rule files were not deleted if rule compilation failed.
  • Previously, the Application masking folder was only created for the user who ran the installer. With this update, the rules folder is created when the Rules editor is launched.
  • Resolved an interoperability issue with large OneDrive file downloads that was causing some operations to fail.
  • Fixed an issue where per-user and per-group settings did not apply if the Profile or ODFC container was not enabled for all users.
  • Resolved an issue where the Office container session configuration was not cleaned up if a profile fails to load.
  • Fixed an issue where HKCU App Masking rules leveraging wildcards would fail to apply.
  • Fixed an issue where FSLogix did not properly handle logoff events if Profile or ODFC containers were disabled during the session or per-user/per-group filters were applied mid-session that excluded the user from the feature. Now FSLogix logoff related events will always occur if FSLogix loaded a container for the user.
  • Fixed an issue that caused some sessions configured with an ODFC container to fail to login.
  •  Resolved an issue where the rule editor would crash if there were no assignments configured.
9 Replies
Was the profile deletion issue addressed?
Can we now redirect logs using the GPO setting?

@Steve Downs 

Hi after tested FSlogix for some time we get issues. 

Version:

FSLogix_Apps_2.9.8089.44141

 

See that logoff freeze for users and I never get this in logs:

"Begin Session: Unload profile"

Works if admin do a manual logoff direct on server the session running. 

 

Any help for this ?

@AndreBoehm Thanks for share download file.

installed latest version and restarted. and as soon i try to login from Remote Desktop Client. got this massage 

c951909_0-1647522137798.png

We have this issue with previous version as well. kindly let me know the root cause of this issue.

@Steve DownsSo at present a user has Multi-Search configured for Server 2019 and is using an Office Container Only. How does the search database get stored into the Office container, or are you relying on the user storing the search database in their profile management solution?

@c951909 We are Using Citrix and only get issue when users do logoff. Session is stable all time and don't get any reconnect

lots of random local_username left on our servers, we are performing nightly checks. Not a great solution, and seems like a lot of customers have similar issues. I hope these issues can be resolved as it's impacting us, we also have a few random profile issues at logon, where interop with ivanti environment manager is a real issue. These issues are only really seen at scale and I do wonder what kind of performance testing is actually done at Microsoft.

@Steve Downs 

 

We have an issue when we use cloud cache with an destination Azure page blob and a local path that we are unable to sign in if the device doenst have an internet connection.
This issue is also present in the current stable release

CCDLocation string used.

type=smb,connectionString=C:\LocalProfileStore;type=azure,connectionString="DefaultEndpointsProtocol=https;AccountName=azurestorageaccountnamepageblob;AccountKey=SuperSecretAccountKey==;EndpointSuffix=core.windows.net"

 

When we have an active internet connection everything is working fine.

Whitout we are unable to sign in

We have vhdx locks with 2.9.7979.62170 so just tried 2.9.8089.44141. Now users are getting "Er kan niet worden aangemeld bij uw account". Creates a c:\users\local_<user> folder and a c:\users\TEMP folder.

Part of the log:
[23:10:52.577][tid:00001338.000008d4][INFO] Redirections.xml copy success
[23:10:52.577][tid:00001338.000008d4][INFO] Reading profile folder redirections
[23:10:52.577][tid:00001338.000008d4][INFO] Status set to 23: Cannot setup folder redirections
[23:10:52.577][tid:00001338.000008d4][INFO] ErrorCode set to 13 - Message: De gegevens zijn ongeldig.
[23:10:52.577][tid:00001338.000008d4][ERROR:0000000d] Error reading redirections (De gegevens zijn ongeldig.)
[23:10:52.577][tid:00001338.000008d4][INFO] Error. Cleaning up.
[23:10:52.577][tid:00001338.000008d4][INFO] Removed redirection from C:\Users\((<username here))>
[23:10:52.577][tid:00001338.000008d4][INFO] Reason set to 9: Profile load failed
[23:10:52.609][tid:00001338.000008d4][INFO] Detached vhd(x)
[23:10:52.609][tid:00001338.000008d4][INFO] VHD(x) Detach request returning after 31 milliseconds

e: When NOT using redirections.xml the whole FSLogix login process runs fine now. Will try to sort that out, I haven't copied the new admx yet, maybe that helps. Tnx.