Forum Discussion
FSLogix - Profile can not load
Rauke7492 i doubt its a registry setting issue; looks like it's an issue with how the storage account is set up. did you set up AADS authentication and ensure that the azure ad user has Storage File Data SMB Share Contributor rights under access control (IAM)?
- benjamink9Mar 04, 2020Copper Contributor
Rauke7492 and i have owner permissions.
- Rauke7492Mar 05, 2020Copper Contributor
The storage account is in a different Azure region than the VM.
- Slava_TruduJul 30, 2020Copper Contributor
We are using Horizon "floating" VDI pool and I am configuring FSLogix profiles for them to be saved into a share in the azure cloud storage account. I have stored the Access key for the storage account via PS script in the template image. When the cloned VDIs are created in the "floating" pool, I also run a script via GPO in a "computer configuration" to store the same access key and, in addition, another GPO ( that is linked to a security group that the user is a member of) fires a scheduled task where the mapping to a file share in that storage group is created.
What happens: I have my profile .VHDX file created from one of the floating VDIs, but on subsequent logins, where different VDIs are used (since it is Horizon's floating pool), I am not able to attach to that profile again. Other users can't even create that profile and the error is always the same:
FindFile failed for path: \\xxxx.file.core.windows.net\shareXX\username_SID.VHDX (the target name is incorrect). Even though, the mapped share opens without prompting a user for credentials.
What is going wrong in that process? Can Azure support chime in?
Slava
- Rauke7492Mar 05, 2020Copper Contributor
unfortunately did not work
- Rauke7492Mar 04, 2020Copper Contributor
I'll give myself ownership tomorrow morning, but that's not for the normal user. On the first VM, everything runs without problems
- benjamink9Mar 04, 2020Copper Contributor
Rauke7492 ok, well i had the same issue as you're having, and it was fixed by me adding the permissions under access control (IAM) and also under configuration > AADDS enabled.