May 26 2022 12:44 PM - last edited on Jul 21 2022 03:12 PM by Eva Seydl
May 28 2022 06:25 AM - edited May 28 2022 06:31 AM
Hi @msft_jasonparker are you / is the FSLogix team the aware of any similar reports that Office Containers hosted on Windows Server 2019/2022 (File Server, SMB 3) causes the underlying ReFS 3.4 / 3.7 volumes to become RAW after a BSOD or causing other write issues on the volumes?
Curiously, all other ReFS volumes on the same server hosting FSLogix User Profiles are not affected.
This only happens with Office Containers at a customer, every ~30 days.
Due to the fact we cannot reproduce it outside of this "schedule" we could not successfully open a support ticket with the FSLogix Team.
May 28 2022 09:30 AM - edited May 28 2022 09:31 AM
Hello, does this fix only fix these two issues?
May 30 2022 02:32 AM
Is it possible that you somehow broke the static download url for the latest fslogix?
We always download the latest agent via "https://aka.ms/fslogix_download" via Invoke-Webrequest because the AVD base image is always not maintained and has an old fslogix release installed.
Since the hotfix release it does not work anymore.
May 31 2022 07:58 AM - edited May 31 2022 08:00 AM
I am not aware of this issue, and this is the only report that I know of. My best recommendation would be to have the FSLogix support tool downloaded (https://aka.ms/fslogix_support_tool) and then when the BSOD occurs, collect the dump and logs from the system and then open a case. An engineer can analyze the crash data and logs.
May 31 2022 03:33 PM
Jun 01 2022 06:30 AM
Jun 01 2022 09:52 PM
Changing the log path location with the FSLogix GPO setting has been broken for many releases now.
Changing it via a GPP registry works fine.
Can you guys please address it in the next release?
Jun 02 2022 12:39 AM - edited Jun 02 2022 12:47 AM
Yes we need this too for our automatic sessionhost deployment! We need the direct "latest" download url back, pls !
Jun 02 2022 11:37 PM
Thanks for your guidance @msft_jasonparker.
One last question about the procedere.
The BSOD doesn't happen on the Windows Server 2022 system where FSlogix is installed, but where the Office Containers reside.
Also we cannot yet identify which User might cause the issue.
So running the tool on the fileserver would be still helpful?
Jun 03 2022 07:10 AM
Hello, Fslogix 2201/Windows 2016
I encounter a bug where the vhdx disk does not mount,
in which log should I look for more details?
Jun 03 2022 03:40 PM
Jun 09 2022 08:55 AM
Jun 09 2022 09:11 AM
Jun 09 2022 09:16 AM