This message was deleted.

I believe the default is 12 retries at 5 second intervals when attempting to attach the vdhx file. Check the status after login located in HKLM\Software\FSLogix\Profiles\Sessions\<UserSID>. If it is 300 then it’s already attached somewhere and probably waits a minute for a release. You can configure the retries and timeout individually

forgot to mention that this was one of the things we changed. We changed it to 2 retries of 5 seconds but made no difference.

Definitely worth checking your FSLogix logs first to see if there are retries or what the gap is in-between the timestamp.

After looking through a log that was sent to me a while back it took less than a second for the 2nd machine to recognize the VHD needed to be read only and attach the RO VHD. I would definitely start with logs and timestamps.

thank you. I will have a look tomorrow when back at work.

Also make sure you use the latest version available. We've see similar behavior which was solved in 2.9.7117.27413

thanks for your help. It turns out we forgot to exclude vhd files in Sophos and that took up quite a bit of time

No problems. Did we speak? SDWAN is a great product. I'm glad you liked the presentation. Thank you.

@Leee Jeffries no we didn't 🙂 I was just listening and taking notes.

Any other queries, feel free.

@Leee Jeffries thank you 🙂

@Csaba Did you just exclude *.vhd from being scanned? or just the VHD location itself?

@Ryan Gallier we added *.vhd and *.vhdx as exclusion but only for the folder where they are supposed to be. We also added

thank you. which folder. On the file server holding the VHDs?

no. On the workstation. Our vhds are located in c:\temp so we excluded c:\temp\*.vhd and *.vhdx#

how do you get the VHDs on the workstation itself? maybe i just don't understand somethign

at login FSLogix is supposed to copy the vhd file to the workstation and mount it. at logout dismount and copy it back to the file share. That is my understanding of FSlogix,

That's not my understanding. My understanding is it mounts it directly over the network.

Attached over the network.

it was one of my colleagues who worked on it, I was just helping out. Will try to confirm

Sorry, I'm 💯 that its network attach. There is no option for a vhd copy. There is a cache but that does cache the entire vhd.

@Leee Jeffries I am sure you know a lot more about it than me. My understanbding is probably wrong but then I don't understand how the C:\temp\*vhd excludion helped 🙂

If you set it up on the workstation itself and had the vhd save in that location it would make sense, otherwise I have no idea. If you could ping over the setting in the form of a gpo report that would be great.

@Leee Jeffries What are the "Best practices" of AV exculsions for FSLogix?

My recommendation is easy , exclude *.vhd / *.vhdx on your endpoints. That should ensure it doesn't have a problem mounting them. For a more secure approach exclude the FSLogix service.

@Leee Jeffries I sent you the report

Having reviewed the GPO report I can see you are using cloud cache with two SMB locations. This is why you have the local cache .vhd. your profiles are network attached with the cloud cache on top of this capturing writes.

ok 🙂 I will need to read more about this as I was just jumping in to help a colleague

No worries. The behaviour is sort of expected in this particular scenario. The FSLogix logs in ProgramData are very detailed so any issues, check there.

thank you

Thanks Leee

No trouble guys, my pleasure