FSLogix profile not loaded causing a local profile on the RDSH.

Maikel Vanmuysen 1 Reputation point
2021-03-17T11:23:05.497+00:00

Hello all,

We are experiencing a random issue with userprofiles in our remoteapp environment.
To describe the environment; We have a high available setup of 2 connection brokers with a collection of 4 baremetal RDSHs.
We use FSLogix (version 2.9.7654.46150) to offload the profiles of the users to a fileshare.

This all went well untill we started getting users that connected to the remoteapp and suddenly had to configure Outlook again. When troubleshooting this issue it was obvious that the VHD file was not loaded and a local user profile was created on the RDSH. This was verified by looking at the sessions on the fileserver, and there was no LOCAL_Username folder for those users in the C:\Users folder on the RDSH

The errors in the Profile Log is the following:
[ERROR:00000050] VirtualDiskAPI::CreateFormattedDisk failed to create vhd(x): ****** (The file exists.)
[INFO] Status set to 31: Unknown status

[ERROR:0000001f] LoadProfile failed. ********. (A device attached to the system is not functioning.)

So FSLogix sees the VHD, it knows it exists, but tries to create an new one anyway while it should be loading the existing profile. When 1 user experiences the issues, the logons of new users on that RDSH all have the same issue. Rebooting sometimes helps, but then the issue occurs again pretty soon after the first few users have connected.

What did we try/troubleshoot;

  • It does not seem to be a permission issue because at the same time antoher RDSH is opening the profiles correctly.
  • While researching the issue, I came by the options: VHDNamePattern, VHDNameMatch, but those options are not configured in our setup, the only setting we have in this part of the FSLogix GPO is: "Swap directory name components" to "Enabled" (GPO settings are found below)
  • Reinstalling or Repairing the FSLogix agent did not resolve the issue.

These are the GPO settings;


FSLogix/Profile Containers
Policy Setting Comment
Delete local profile when FSLogix Profile should apply Enabled
Delete local profile when FSLogix Profile should apply Enabled

Policy Setting Comment
Enabled Enabled
Enabled Enabled

Policy Setting Comment
Profile type Enabled
Normal direct-access profile

Policy Setting Comment
Set Outlook cached mode on successful container attach Enabled
Set Outlook cached mode on successful container attach Enabled

Policy Setting Comment
Store search database in profile container Enabled
Disabled

Policy Setting Comment
VHD location Enabled
VHD location -DFS Path-

FSLogix/Profile Containers/Advanced
Policy Setting Comment
Prevent login with failure Enabled
Prevent login with failure Enabled

Policy Setting Comment
Prevent login with temporary profile Enabled
Prevent login with temporary profile Enabled

FSLogix/Profile Containers/Container and Directory Naming
Policy Setting Comment
Swap directory name components Enabled
Swap directory name components Enabled


Can anyone point us in the right direction as to what we can do to resolve this issue?

Thanks!

FSLogix
FSLogix
A set of solutions that enhance, enable, and simplify non-persistent Windows computing environments and may also be used to create more portable computing sessions when using physical devices.
474 questions
{count} votes

2 answers

Sort by: Most helpful
  1. Андрей Михалевский 2,806 Reputation points
    2021-05-30T00:59:55.21+00:00

    Hello. I have the same problem.

    0 comments No comments

  2. AdAstra_13 1 Reputation point
    2021-06-29T19:28:57.307+00:00

    Just came to say I have the exact same problem- seems to have started recently.

    It is causing our servers to use the local drive space- and running of storage. We use AFS (Azure File Services), with Citrix but the symptoms are the same. There is only one file share- permissions are set globally. Some users have no issue, some users do. But we do see the same; no local_username folder.

    Win2016. We see the problem with published apps only- not so much Desktops.

    EDIT: We found the source of this problem, for us at least. We have a mixture of users launching Published Desktops and Apps. So if the VHD was first accessed on one, it's not able to mount it on the second, resulting in no "local_username". It came down to the VHD access type. We had it set to Read-Write, and have now changed it to "Try for Read-Write first, fallback to RO" and voila....it's working. Read-only profiles are copied to the second app launch, and changes are merged at logoff.

    Working brilliantly now.

    0 comments No comments