Forum Widgets
Latest Discussions
Recycle Bin Corrupt upon login - shot self in foot :(
In setting up multiple AVD Host Pools (replacing Win10 with Win11) I figured I'd do better in locking down the Storage Account > File Share that's setup to host the FSLogix user profiles. Silly me. Suffice to say, when users log in, they're presented with a corrupt recycle bin message. My old Win10 environments didn't involve touching the root of the Azure file share volume and I never had such issues. Repeating the same with a new Win11 and applying the steps as documented here: https://learn.microsoft.com/en-us/fslogix/how-to-configure-profile-container-azure-files-active-directory?tabs=adds#set-ntfs-permissions, also does not present the recycle bin issue. Interestingly, deleting and recreating the File Share (meaning default ACLs), does NOT fix the issue which is rather perplexing. The hosts for each of these AVD builds reside in our on-prem AD. The GPOs in effect are the same for each, barring the VHDLocation policy. If I add a user into the "FSLogix Profile Exclude List", they don't have the issue. Remove them and they have the issue. Not that I've touched system drive root perms, but that tells me all is well with the system drive and their respective recycle bin folders. I increased the logging level to the max, but the Profile log doesn't note any errors. A side-by-side comparison using the same user logging into the 'healthy' environment vs a corrupt bin environment doesn't reveal anything either. I know I've provided very little specifics with the environment settings, but I figured there's something obvious I'm overlooking. I'm ready to be taught a lesson! I'd rather not have to rebuild these 4 environments. Thanks in advanceSolvedRedlimey69Apr 02, 2025Copper Contributor169Views0likes1Comment[FSLogix & Citrix] How to save the profile data of account2 that was startet within my account1?
Hello, i am starting Citrix Workspaceapp with account1 which uses FSLogix. Within the Citrix workspace app i start a Citrix app with account2 in another user context. If possible, how can i configure FSLogix which is aware of account1 to save account2 as a FSLogix profile, too? Thanks in advance and kind regards BerndSolvedBernd_RothSep 02, 2024Copper Contributor448Views0likes4Comments2210 HF4 still broken on Server 2019 and new Teams
Hi Everyone, so, I assume everyone's been testing the new 2210 HF4 this morning/last night? I've got two Citrix Session Hosts, Server 2022 and Server 2019 Both of them have the latest FSLogix installed, and they share the same GPO for the FSLogix configuration. They've also got a common redirections.xml file for both Servers. Logging into a Session host creates both a normal profile folder and a local_<user> folder for redirected folders/files For testing, I've been deleting the vhdx files between tests on each server, so there's no potential issues using a profile container between the two different OSes. Also, I've only got a single profile container configured - I'm not using an Office container I've also got the latest new Teams installed on both servers. Server 2022 was installed via the bootstrapper and Server 2019 was installed via DISM as per the recommended method. Server 2022 - when i log in to this OS using a test account configured for FSLogix, and start new Teams, everything is fine. When i log off, both the user profile and local_<user> folders get deleted. Server 2019 - Doing exactly the same operation on this server, after starting new Teams, then logging off, the local_<user> folder fails to get deleted. The error message in the FSLogix operational logs are "Error removing directory: C:\users\local_<xxxx>\AppData\Local\Microsoft\IdentityCache\1\UD\.... The process cannot access the file because it is being used by another process)" Note that the location under AppData\Local\... can change between different tests as there are a lot of different files locked and this is the first file FSLogix came across during the logoff process. Running sysinternals Handle64.exe shows that the files are open by "System" (pid = 4) Also, I can't delete the folders manually as administrator after the user has logged off either, unless i reboot the server. This issue only occurs after I've run new Teams for the first time. If i start clean without a profile container, log in, start Word, Excel, Outlook, etc, but don't start new Teams, the issue doesn't occur. Once I've started Teams, even if i shut it down, the local_<user> folder can't be removed/deleted. Anyone else experiencing this?SolvedKen_ZMay 15, 2024Brass Contributor6.6KViews1like34CommentsLatest FSLogix and New Teams - how to get that working reliably
Hi Everyone I've spending a long time earlier this year getting Teams and Office working reliably with FSLogix, I'm now trying to get the new Teams (23306.3308.2524.1744 as of posting this message) working reliably between Windows 10 desktops using FSLogix (for hotdesking requirements). I used the following article to deploy the new Teams to a set of test desktops running Windows 10 22H2 x64 and FSLogix 2.9.8612.60056 https://learn.microsoft.com/en-us/microsoftteams/new-teams-bulk-install-client I logged in as a test user, started the New Teams from the Start Menu (got a GPO stopping it auto-starting) and it sets itself up correctly. It them reports that there is a newer version and I upgrade it to 23306.3308.2524.1744 After that, the upgrade message no longer appears I then log off, and log onto another test desktop. Again starting New Teams from the start menu and it appears to go through the same initialisation / configuration routing, but reports the new version (23306.3308.2524.1744), and also says that there is an upgrade available. If I perform the upgrade, it downgrades the version to the version that was originally installed on that desktop, not the new version that was upgraded to the the other desktop. Is this a bug in Teams or an issue with FSLogix/misconfiguration in redirections.xml? Has anyone successfully deployed the New Teams with FSLogix? One excellent point with the new Teams is that the horrendous bloating of the profiles are a thing of the past now. Regards Ken ZSolvedKen_ZNov 21, 2023Brass Contributor44KViews0likes26CommentsNeed FSLogix 2201 hotfix 2 - 2210 breaks things
Hello, ms or anyone else who might have it, we need FSLogix 2201 (2.9.8228.50276). If anyone has the file or if MS could actually publish more than just the last two releases, thanks! Also, why on earth would you only publish the last two releases ??@MS? What the heck...Solvedst84Sep 22, 2023Copper Contributor1.3KViews0likes4CommentsFSLogix 2210 with hotfix 2 (black screen and hangs)
Since HF2 we've been experiencing lot's of black screens. Install Appackges Setting is off, but despite this setting fslogix hangs for many minutes. [16:17:57.450][tid:00000e14.00007c78][INFO] Configuration setting not found: SOFTWARE\FSLogix\Profiles\InstallAppxPackages. Using default: 1 [16:17:57.450][tid:00000e14.00007c78][INFO] Session configuration wrote (DWORD): SOFTWARE\FSLogix\Profiles\Sessions\S-1-5-21-zzzzzzzz\InstallAppxPackages = '1' [16:20:27.638][tid:00000e14.00007c78][ERROR:800706be] AppxPackage installation error: (Kan RPC niet uitvoeren.) In this case the example hangs for 2,5 minute. Is there anyone who is experiencing this too?SolvedKleinVuurSep 21, 2023Copper Contributor5.3KViews0likes3CommentsFSLogix and Virus Scans
For individual terminal servers, we always set up a weekly virus scan on Sundays in order to subsequently detect viruses that were not detected with the real-time check. Now with the server farm and FSLogix, this is no longer the goal, since the VHDXes of the users are not connected during the virus scan on Sundays and the Outlook mailboxes and also the local documents of the users are not connected. Is there already a solution to be able to check the private data of the users by a virus search?SolvedVolker_BuschJul 11, 2023Copper Contributor946Views0likes2CommentsCorrect update order of FSLogix servers and policy definitions
I have not found the exact procedure for updating FSLogix either here in the forum, in the FX Logicx documentation or on Google. I just find that I should just install the latest version on the servers over the existing version. But when I update the policy definitions on the DC (fslogix.admx & fslogix.adml)? Before installing the new version on the session hosts or after? Is that how i have to update? 1) Install the latest program version on all session hosts and then shut down the server. 2) Updating the policy definitions and adjusting what should be done. 3) Restart session host Or this: 1) Update of policy definitions 2) Install the latest program version on all session hosts and then shut down the server. 3) Adapting the policy definitions to new wishes 4) Restart session hostsSolvedVolker_BuschJul 11, 2023Copper Contributor963Views0likes2CommentsFSLogix Profile Logs not created
Hi guys we have installed the latest version of FSLogix and disabled the Recycle Bin Roaming in the GPO. We discovered that we still have a Black Screen of about 20 Seconds when we login into a Citrix CVAD 2203 LTSR CU2 Server, which has Server 2019 installed on it. I wanted to check the Profile Logs but discovered that the logs are not showing the latest logins. When we restart the service it creates a new log successfully. We have configured the FSLogix client to create log files on drive D. Can anyone guide me what could be the issue? Thanks and best regards, MarcSolvedmarckuhn1975Apr 28, 2023Copper Contributor1.7KViews0likes3CommentsSystem cannot find the path specified, failing to create VHD
I have been going in circles trying to figure out why FSlogix is failing to find the path to create the VHD. If a user has access to the VHD storage location after they log in why is FSLogix failing to create a VHD for them? To sum up the issue: New install, Win10 Azure Virtual Desktop with Azure Files share for storing VHD. FSLogix settings controlled by Group Policy, confirmed they are being set in local registry Have tried several accounts, same results FSLoigx reports that the path cannot be accessed But the user can open the path and create files/folders. Running latest FSLogix release Screenshot of errors: From the FSLogix troubleshooting page with what I have done to figure this out. Compare the current values of Status, Reason, and Error to the documentation https://docs.microsoft.com/en-us/fslogix/fslogix-error-codes-reference. What the logs are reporting - status 6, reason 5, error 3 6 = There was an error determining the path to the VHD/X file. 5 = five is not listed in the documentation 3 = The system cannot find the path specified. Verify all prerequisites have been met As far as I can tell I have met all prereqs Is the https://docs.microsoft.com/en-us/fslogix/configure-profile-container-tutorial? Yes Do you have a valid file system location in the https://docs.microsoft.com/en-us/fslogix/configure-profile-container-tutorial? I can copy the path from the logs, the one that I have set via group policy, and put that in explorer and it opens up the folder without error. Does the user have appropriate permissions to the VHD(X) file on the file server? I can also create files and folders in the location defined to store the VHD Is the user a member of the local FSLogix Profiles Include group and NOT a member of the FSLogix Profiles Exclude group? Is a member of include and not a member of exclude Does a local profile already exist for the user? No local profileSolvedjimatbutlerMay 24, 2022Copper Contributor6.7KViews0likes1Comment
Resources
Tags
- FSLogix17 Topics
- PROFILE container2 Topics
- VDI2 Topics
- New Teams2 Topics
- citrix2 Topics
- FSLogix issues2 Topics
- cloud1 Topic
- office 3651 Topic
- containers1 Topic
- virtualization1 Topic