Thanks for posting in Q&A platform.
Please understand, due to the environment limitation, it is hard for us to reproduce and analyze this behavior in our lab. Some necessary network traffics should also be collected for further analyzing this issue. However, analysis of log is beyond our forum support level and due to forum security policy, we have no such channel to collect user log information. If this issue is urgent, I would suggest you contact Microsoft Customer Support and Services where more in-depth investigation can be done so that you would get a more satisfying explanation and solution to this issue.
You may find phone number for your region accordingly from the link below:
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
I even tried to manually mount under a local profile, AD Share version worked, but the NAS share version, mounted the VHD, but I couldn't set a drive letter. It seems to be unable to read the partition in the VHD file.
Conclusions (so far):
Its NOT the NAS specifically. I tried all the above on another NAS. Both Synology (all I have), but both different models, and 1 of them is 3 updates behind. So not a firmware issue either. I have tried different SMB settings too.
Specifically, the issue seems that FSLogix, can create the VHD on the NAS, it creates the SID subfolder and everything. It then can't read or mount the partition so it can then save files inside it. I conclude this when I created the new VHD files, the AD version was around 500Mb the NAS version was 140Mb, both should have been exactly the same.
I also copied both AD and NAS created VHD's to the NAS Profile share and tried manually mounting. I mounted both VHD's fine, it even auto-assigned a drive letter and was able to browse.
I have tried the NAS version inside the SID subfolder and next to it. It always mounts and reads fine outside of SID folder, but inside it will work sometimes, and not others.
At this stage, it looks like a permission issue, but 2 things make me question that.
I can read and write to the folder fine, I have ownership and FSLogix creates the folders and permissions.
The VHD works sometimes in the SID folder, pointing that it cant be permissions, I haven't changed any other settings other than moving the VHD and remounting it.
How would folder permissions affect reading partitions from the VHD? I can understand if I couldn't mount the VHD at all etc.
So in conclusion, I know a lot more about the problem, but still not enough to know exactly what it is and possibly fix it. So I know much much more but still know nothing.
Sign in to comment