Share via

FSLogix Service Hangs on Signout or Shutdown

Anonymous
2024-06-07T21:26:00+00:00

Hello all,

I build a new WinServer 2022 image (thanks New Teams) to use in out VMware environment. SO far everything is looking good, except now I'm noticing that upon shutdown or signout, the FSLogix service hangs ("Please Wait for the FSLogixs Apps Service). This happens on the master and on any RDS pool the image is attached to.

I've checked the registry, and the settings all match our old WinServer 2019 for FSLogixs, so I'm at a loss.

Any help is much appreciated!

Windows for business | Windows Server | User experience | FSLogix

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-06-28T16:52:36+00:00

    Hey Jacen,

    Thank you for your reply. I have been reviewing the information you sent me, thank you.

    A little more background information:

    *We currently use FSLogix successfully in a VMware environment. Basically, a master image is created, then that image is replicated to two virtual RDS servers that the user logs into.

    *The issue I am having is with a new master image built off WinServer 2022. I verified all FSlogix settings in the registry match the current master image (WinServer 2019).

    0 comments
  2. Anonymous
    2024-06-10T03:44:13+00:00

    Hello,

    FSLogix is commonly used to manage user profiles and applications within virtual environments. Could you please specify how you are accessing the server? Are you utilizing Azure Virtual Desktop (AVD)?

    To troubleshoot this issue, consider the following steps:

    1. FSLogix synchronizes user profiles during logoff; hence, it's crucial to review your profile container settings. It's highly recommended to employ a single container configuration for profile containers.
    2. Verify that the user accounts accessing the profile containers have the necessary read and write permissions. If you've implemented cloud cache, ensure that the CCDLocations setting points to the same storage account. For more information, see: Configuration Settings - FSLogix | Microsoft Learn
    3. Ensure that both the FSLogix Apps Service (frxsvc.exe) and the FSLogix Cloud Caching Service (frxccds.exe) are added to the trusted applications list. More information is available at: Services, Drivers, and other Components - FSLogix | Microsoft Learn
    4. Investigate if any firewall rules or network configurations might be interfering with connectivity to the FSLogix profile containers.

    References:

    I hope this helps.

    Regards

    0 comments