Forum Discussion
The FSLogix 2201 Public Preview is now available
FSLogix 2201 Public Preview Update 1 has been published to address the issue outlined below. Please read details here.
FSLogix 2201 is now available in Public Preview. This public preview is not recommended for production workloads. Please leverage your standard Microsoft support channels to report issues with this public preview release.
ISSUE IDENTIFIED IN THIS PUBLIC PREVIEW RELEASE:
Your environment is impacted by this bug 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.
We recommend impacted customers not install this public preview or revert back to the current generally available release. We are validating a fix for the issue and will publish an update to the public preview when it is available. Customers not impacted by this issue can continue validating this public preview release.
Preview Details
You can sign up here to participate in the Public Preview:
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 what's new in this release:
- 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.
81 Replies
- alexwilcoxCopper Contributor
SteveDMSFT
Has anyone noticed strange behaviour with OneDrive since installing this? Some users are seeing duplicate OneDrive icons: one working normally and the other showing as not signed in.
The latter is unresponsive and cannot be signed in to
Users can ignore this however we've found that if a new user encounters this they're unable to log in to OneDrive at all
The issue does seem to stay on particular VMs when it manifests but as all of our VMs are built programmatically from a gold image we don't believe there's anything configured incorrectly for those VMs
We found a workaround which involves closing onedrive and then deleting the folder:
'C:\Users\<user>\AppData\Local\Microsoft\OneDrive\Settings'. The sign-in window appears when onedrive is launched but if you close down this window you then get stuck again.
When testing with non fslogix users the OneDrive sign in prompt works reliably- StephanstokeCopper ContributorHi Alex,
We also experience this problem.
The workaround works fine for now. I have already opened a support case for this issue.
I'll mention your workaround to Microsoft, maybe it will help them.
Regards!
- srojas117Copper ContributorI tried upgrading one of our hosts from 2.9.7979 but it didn't go as smoothly as I'd hope. When I tried to logon I was greeted with a flashing taskbar. I could bring up the ctrl-alt-delete screen but was unable to do much after that. Disabling the fslogix service via our RMM let me sign back.
I tried doing a fresh install of this preview version but the result was the same.
The error code in the Operational logs was "creating registry key S-1-21-273264797-2751341861....\software\Microsoft\office(The parameter is incorrect.)
The odd thing is that I have second RDS running the same 2019 OS and it was able to install and run without any issue.
I reverted back in the time being. - StephanstokeCopper Contributor
Hi everyone, We use a server 2019 1809 rds environment in combination with fslogix and onedrive. At the moment we are experiencing the problem that when opening a file from onedrive the following message appears: The cloud operation failed 0x8007017c. the options are then, try again, skip and cancel. if you click on “try again” the file will be opened. when you click on “cancel” the popup window disappears. after that the file opens without any problems and notification. when i put the file back to the cloud the problem comes back and i get the same error. when Fslogix is not running the problem does not seem to arise. as soon as fslogix is active again the problem occurs again. does anyone else have the same problem? I don't only have this with the preview version but also with other Fslogix versions. a reset, clean profile, disabling antivirus/firewall and several reinstalls of onedrive and fslogix didn't help unfortunately. thanks and greetings Stephan
- VissershCopper Contributor
Hi, i have exactly the same. I can reproduce this also on other environments with 2019 RDS.
When you use in onedrive the free/cleanup space (remove cached files). Only on the first time you open a file you got error 0x8007047c. If you got the error, and trie to open the file again, it is working.
When you place you onedrive folder outsite the fslogix problem than everything works fine. Did you find a solutions for this, rather than scripting and setting attributes on folders/files?
Also when using storage sense, you have the same error after cached files are removed.
- StephanstokeCopper ContributorHi Vissersh,
There is currently no solution and I am still working with Microsoft to solve the problem and provide logs for research.
At the moment we have disabled files-on-demand to avoid the error.
In your enviroment, do you have ivanti workspace running?
- Sjaak nullCopper Contributor
StephanstokeDid you solve this issue? I've exact same issue. Was wondering how to fix this issue. Thanks!
- StephanstokeCopper Contributor
Hi Sjaak,
Microsoft is still working on it. Are you experiencing the same problem in a server 2019 enviroment? I just sent some extra log files to Microsoft. I'll keep you and this forum informed.
Our environment:
- Windows server 2019 + latest updates.
- FsLogix Preview update 1 (fix a lot of bugs and is running stable).
- OneDrive latest update (no preview).
- maximilianlinseisenCopper Contributor
Im not absolutely sure but i think we had the same problem until we redirected the %LOCALAPPDATA%\Microsoft\Office\16.0\OfficeFileCache with the redirections.xml file.
- StephanstokeCopper Contributor
Hi, Thanks for the suggestion! Unfortunately this did not solve the problem.
I am currently working with Microsoft on this issue.
As soon as I know more I will announce it here.Good day!
- PdfPeetCopper Contributor
SteveDMSFT We notice that we still have some sessions that do not clean up properly.
The command 'frx.exe list-redirects' shows no open redirects and the .vhdx is dismounted properly.
However, there is "C:\Users\<username>" and "C:\Users\local_<username>" after the user logs of. The "local_<username>" we can remove; but the "C:\Users\<username>" will stay locked untill a reboot.
If the user would logon to the same RDS server again, they will get a "C:\Users\<username>.FSL0" and "C:\Users\local_|<username>.FSL0"; but that causes issues with Outlook OST cache that still excepts the path without .FSL0.
The following rekeys are set:
- HKLM\SYSTEM\CurrentControlSet\Services\FRXDRVVT\Instances\frxdrvvt\Altitude = "138010"
- HKLM\SOFTWARE\FSLogix\Apps\CleanupInvalid Sessions = dword:1
Revent logs:
==
[08:24:59.681][tid:00000dbc.00000c9c][INFO] Unregister app notifications
[08:24:59.790][tid:00000dbc.00000c9c][INFO] Accessing network as user object
[08:24:59.790][tid:00000dbc.00000c9c][INFO] Adjusting symlinks
[08:24:59.837][tid:00000dbc.00000c9c][INFO] Status set to 1: Cannot load user's profile
[08:24:59.837][tid:00000dbc.00000c9c][INFO] ErrorCode set to 1064 - Message: An exception occurred in the service when handling the control request.
[08:24:59.837][tid:00000dbc.00000c9c][ERROR:00000428] invalid string position (Uitzondering in de service bij het verwerken van de besturingsopdracht.)
[08:24:59.853][tid:00000dbc.00000c9c][INFO] Configuration setting not found: SOFTWARE\FSLogix\Profiles\ShutdownOnUserLogoff. Using default: 0
[08:24:59.853][tid:00000dbc.00000c9c][INFO] Configuration setting not found: SOFTWARE\FSLogix\Profiles\RebootOnUserLogoff. Using default: 0
[08:24:59.853][tid:00000dbc.00000c9c][ERROR:00000428] UnloadProfile failed. Version: 2.9.8048.43478. User: Username. SID: S-1-5-21-xxxxxxxxxxxxxx. SessionId: 2. FrxStatus: 1064 (Uitzondering in de service bij het verwerken van de besturingsopdracht.)
[08:24:59.853][tid:00000dbc.00000c9c][INFO] unloadProfile time: 172 millisecondsCheers,
Peter
- SteveDMSFT
Microsoft
PdfPeet, have you opened a support case? If not, could you please do so? That's the best way for us to collect logs and triage the issue. - stefanoscloudCopper Contributor
I have already mentioned this behavior with _local profile not being properly deleted occasionally. As I mentioned in my previous comment, this case was open as Microsoft Technical Support case and got escalated all the way to even examining OS system dump but no solution was found even though it was verified as a bug. The case was finally closed without a resolution. This issue is happening from previous versions for over 1 year now and there is still no official response from Microsoft on why the identified bug has not been resolved yet. In my article (https://stefanos.cloud/kb/how-to-resolve-error-group-policy-client-service-failed-the-logon-access-denied-in-citrix-and-fslogix-environments/) I provide a detailed analysis of the issue and of the troubleshooting steps performed in coordination with the FsLogix support team and product group. Numerous FsLogix users with same issue have contacted me from various countries asking if there any further update I can share with them.
Again, this is affecting many customers and it is very important to have a final resolution. We need your feedback on this, thank you.
- PdfPeetCopper Contributor
For now I've scheduled a simple script that runs every 30 minutes during the nightly hours to:
- Check if there are any users still logged on through RDP
- If not, check if there are any local_ of profile folders still there that shouldn't
- If so:
- Run an "frx.exe list-redirects" and cleanup where needed (doesn't seem to be needed anymore since the 2201 release)
- Run an "frx.exe stop-agent" & "frx.exe start-agent" (this removes the locks from the profile folders; without having to reboot the server)
- Do additional cleaning
- Registry: ProfileList and ProfileServices\References
- Profile folder: take ownership and remove "local_<usersname>" and "<username>" folders
It's not ideal, but it keeps servers clean.
- jshonkCopper Contributor
SteveDMSFT I think we found another issue with this release of FSLogix. This particular issue is a QA environment that FSLogix was upgraded to the TP release. It's a Windows 2012 R2 shared environment (also Citrix 1912 LTSR CU4).
In the FS Logix Event Logs we are now seeing Event ID 26:
Injection failed. [OUTLOOK.EXE] (Access is denied.)
Sessions are now locking up/freezing as a result when affected users are using Outlook.
Joe
- DBR14Iron Contributor
jshonk we've seen issues like that prior to this release. I've been in a dog fight with MSFT support where our AVD hosts with or without 16 users on the host will go to a screaming crawl. 30-60 sec just to launch edge. I see a lot of errors like what you are referencing with Excel and Outlook and then if the user logs off their VHD gets stuck and occasionally I can only dislodge them by rebooting the server. Other times the powershell script works.
- rchan1910Copper Contributor
DBR14 We've had that AVD host performance issue you described a couple of times. when we contacted support they basically tell us to increase VM size which makes absolutely no sense if it happens when 0 users are logged on.
I didn't make the connection that this could be Fslogix related.
- SteveDMSFT
Microsoft
Thanks for reporting that issue jshonk. Would you mind opening a support tocket so we can investigate the root cause?
- kesslersebCopper Contributor
SteveDMSFT When the user logs off the server, we get the following error that the local profile cannot be deleted. I do not know why. 🙂
//
[11:08:32.034][tid:00000ac4.0000292c][ERROR:00000091] RemoveDirectory failure C:\Users\da (Das Verzeichnis ist nicht leer.)
[11:08:32.034][tid:00000ac4.0000292c][ERROR:00000091] RemoveDirectory failure C:\Users\da (Das Verzeichnis ist nicht leer.)
//
- MarcoSuesCopper ContributorDid you check active redirects ?
frx list-redirects
https://docs.microsoft.com/en-us/fslogix/command-line-utility-reference- kesslersebCopper Contributor
MarcoSues Thanks for the answer. After restart the server fslogix works fine.
frx list-redirections output
No redirections are currently active.
Operation completed successfully!Redirections.xml File in the config
<?xml version="1.0" encoding="UTF-8"?>
<FrxProfileFolderRedirection ExcludeCommonFolders="###VALUE###"><Excludes>
<Exclude Copy="0">Videos</Exclude>
<Exclude Copy="0">Saved Games</Exclude>
<Exclude Copy="0">Contacts</Exclude>
<Exclude Copy="0">Searches</Exclude>
<Exclude Copy="0">Citrix</Exclude>
<Exclude Copy="0">Tracing</Exclude>
<Exclude Copy="0">Music</Exclude>
<Exclude Copy="0">$Recycle.Bin</Exclude>
<Exclude Copy="0">AppData\LocalLow</Exclude>
<Exclude Copy="0">AppData\Local\Apps</Exclude>
<Exclude Copy="0">AppData\Local\Downloaded Installations</Exclude>
<Exclude Copy="0">AppData\Local\assembly</Exclude>
<Exclude Copy="0">AppData\Local\CEF</Exclude>
<Exclude Copy="0">AppData\Local\Comms</Exclude>
<Exclude Copy="0">AppData\Local\Deployment</Exclude>
<Exclude Copy="0">AppData\Local\FSLogix</Exclude>
<Exclude Copy="0">AppData\Local\GroupPolicy</Exclude>
<Exclude Copy="0">AppData\Local\Packages</Exclude>
<Exclude Copy="0">AppData\Local\Sun</Exclude>
<Exclude Copy="0">AppData\Local\VirtualStore</Exclude>
<Exclude Copy="0">AppData\Local\CrashDumps</Exclude>
<Exclude Copy="0">AppData\Local\Package Cache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\TokenBroker\Cache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Notifications</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Internet Explorer\DOMStore</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Internet Explorer\Recovery</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\MSOIdentityCRL\Tracing</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Messenger</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Terminal Server Client</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\UEV</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\Application Shortcuts</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\Mail</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\WebCache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\WebCache.old</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\AppCache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\Explorer</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\DNTException</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\IECompatCache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\iecompatuaCache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\Notifications</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\PRICache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\PrivacIE</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\RoamingTiles</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\SchCache</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\Temporary Internet Files</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Windows\0030</Exclude>
<Exclude Copy="0">AppData\Roaming\com.adobe.formscentral.FormsCentralForAcrobat</Exclude>
<Exclude Copy="0">AppData\Roaming\Adobe\Acrobat\DC</Exclude>
<Exclude Copy="0">AppData\Roaming\Adobe\SLData</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft\Document Building Blocks</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft\Windows\Network Shortcuts</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft\Windows\Printer Shortcuts</Exclude>
<Exclude Copy="0">AppData\Roaming\Sun\Java\Deployment\cache</Exclude>
<Exclude Copy="0">AppData\Roaming\Sun\Java\Deployment\log</Exclude>
<Exclude Copy="0">AppData\Roaming\Sun\Java\Deployment\tmp</Exclude>
<Exclude Copy="0">AppData\Roaming\Sun\Java\Deployment\tmp</Exclude>
<Exclude Copy="0">AppData\Roaming\ICAClient\Cache</Exclude>
<Exclude Copy="0">AppData\Roaming\Macromedia\Flash Player\macromedia.com\support\flashplayer\sys\</Exclude>
<Exclude Copy="0">AppData\Roaming\Macromedia\Flash Player\macromedia.com\support\flashplayer\flashplayer\#SharedObjects\</Exclude>
<Exclude Copy="0">AppData\Local\SquirrelTemp</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Teams\Current\Locales</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Teams\Packages\SquirrelTemp</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Teams\current\resources\locales</Exclude>
<Exclude Copy="0">AppData\Local\Microsoft\Teams\Current\Locales</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\Service Worker\CacheStorage</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\Application Cache</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\Cache</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft Teams\Logs</Exclude>
<Exclude Copy="0">AppData\Roaming\Microsoft\Teams\media-stack</Exclude>
</Excludes><Includes>
<Include Copy="3">AppData\LocalLow\Sun\Java\Deployment\security</Include>
</Includes></FrxProfileFolderRedirection>
- Hello Steve,
Has the below FsLogix issue been resolved in this release?
https://stefanos.cloud/kb/how-to-resolve-error-group-policy-client-service-failed-the-logon-access-denied-in-citrix-and-fslogix-environments/
If you read the above article, there has been an active and long engagement with the Microsoft Technical Support escalation team and FsLogix product group on the issue and there was no fix nor any ETA defined. Is this fixed in this release and if not, what is the ETA for resolution? This is affecting a huge amount of FsLogix/MS customers worldwide. It had been identified as bug by Microsoft Support Team and has not been fixed for over a year now.
Kindly waiting on your update,
Stefanos- BrianSSmithCopper Contributor
stefanosevangelou Is there a public roadmap around FSLogix?
- JonathanPitreBrass Contributor
PdfPeet I'm also seeing stuck folders on the C:\Users folder. Can you please share your script ? Upload it to pastebin or github. Thanks!
- jshonkCopper Contributor
SteveDMSFT So far so good, this version seems to be a huge stability improvement over the previous version running on Windows Server 2019.
I have found one issue so far. For some reason, there are two app GUIDs associated with the installation of this version (I verified via registry too):
{06B996DB-0DF9-47C1-8149-8A506DC4D2DD} Microsoft FSLogix Apps
{C4A6234E-D6E3-45F8-B282-8B5C3DBBC289} Microsoft FSLogix Apps
{5F779663-565D-4B04-A0B1-843BE78BDDFC} Microsoft FSLogix Apps RuleEditorJoe
- SteveDMSFT
Microsoft
Thanks for reporting this, jshonk. That's expected behavior. One of those GUIDS maps to the FSLogix service and the other to our separate Cloud Cache service. That said, we opened a bug to rename the Cloud Cache entry.
- MarcoSuesCopper Contributor
SteveDMSFT Any Information about https://docs.microsoft.com/en-us/answers/questions/229309/fslogix-unclean-logoff-causing-locked-files-until.html?page=10&pageSize=10&sort=oldest has been fixed with this Version?
Thanks !
- SteveDMSFT
Microsoft
That thread is long and loaded with incorrect info so I can't say what's been fixed. The thread starts with the suggestion that FSLogix is locking Credentials folders, but FSLogix only applies locks to the VHD/x containers. Something else is causing those locks. The thread also mentions the refCount issue, but that's incorrectly correlated with this issue. The refCount key value mentioned in that thread can be updated by MANY activities not related to FSLogix and FSLogix does not manipulate that value directly. The 2201 public preview implements a fix that cleans up the refCount value when it is left in an incorrect state. To be clear, FSLogix is not putting it in a bad state but that incorrect value is causing issues for FSLogix. For reference, that bad refCount value was also causing issues with non-FSLogix Windows profiles and we implemented the same fix in FSLogix.
- aminhirji595Copper Contributor
I hope fix for RefCount work 🙂