Forum Discussion
Solved
FSLogix profiles failing on all new hosts all of a sudden
All of a sudden any new host I try to setup is failing to map all users to their network shared FSLogix profile. I have 10 hosts in one pool, 1 host in another pool, and am testing new hosts into a 3...
Just an update for future visitors, the issue is resolved. The registry keys that point to the share path for the profiles wasn't getting updated correctly by the platform server.....
I think this issue is unique to my setup, so the only thing I'd say that might be helpful is check the registry to ensure the correct share path exists: HKLM\SOFTWARE\FSLogix\Profiles
WillCherry Yes, share permissions are open and confirmed from the context of a user. Can access and even rename the FSLogix profile disk image.
WillCherry
Microsoft
Microsoftnorthcide re-read, it doesn't seem to be a permissions issue. can you check how full the storage is? or if it its restricting usage?
WillCherry Profile storage is Azure Files and is no where near any sort of limits.
As a test I renamed the original profile disk image, logged into one of the "new" image hosts and it did not create a new FSLogix profile, but instead logged in locally. But then when I logged into one of the "original" hosts, it created the new profile disk image just as would be expected. After the new profile image was created, logging back in under the "new" image host it would still not log into the FSLogix profile - it still stayed local.
- WillCherry
northcide Please reach out to the fslogix support team, with the limited information here i can't do much, sometimes the issue isn't as obvious, the log you pasted seemed to indicate and issue with the storage location. if the support team can't get it sorted they'll have you gather some logs and escalate it.
Just an update for future visitors, the issue is resolved. The registry keys that point to the share path for the profiles wasn't getting updated correctly by the platform server.....
I think this issue is unique to my setup, so the only thing I'd say that might be helpful is check the registry to ensure the correct share path exists: HKLM\SOFTWARE\FSLogix\Profiles
- WillCherrycheck the actual profile share and check the users vhd. are either of them full?