This message was deleted.
# microsoft-fslogix
s
This message was deleted.
j
Only those with the guts to deploy it can tell if it's stable 😉
m
That’s why I ask here!
😄 2
m
If the 3 workdays leading upto easter are quiet, I plan to start our initial test on our own delivery group. If the test goes alright, I will slowly introduce it to the rest of our delivery groups through April. I will let you know how it goes 🤞
❤️ 1
f
I pushed 2210 HF1 to production this week, no issue so far (from 2105, CloudCache). I'm not using the built-in shrink feature yet as we are monitoring logoff processing time to take remediating actions if profile are stuck for whatever reason so this feature create false positive as logoff processing take more time.
d
It seems to be stable so far. We use it in production and deployed it at some of our customers. But I disabled the new features, just to be sure. Who needs roaming of the recycle bin, anyway? Compact of the vhdx is done with the known script once a month.
m
Deploying now in a phased rollout. so far so good. if you use Citrix optimizer be sure to check the disk defrag service. fslogix uses this to compact the vDisk and optimizer had disabled the service on our VDAs. so far the logoff duration has minimal impact by the compaction process.
c
Been testing it with roam recycle bin disabled and install appx packages disabled but thought I would try the disk compaction and had issues with it (session ls stuck on log off and not ending) so won't be using that feature
Been getting Black screen's cant logon with RDP/Console (local creds) and thats with roam recycle bin disabled and the appx packages and disk compaction so deff not stable
Seems to screw up windows explorer as well (constant green bar) i found below article. This 2016 Vdisk wasnt patched for a while and was using Fslogix 1907 so really old. Going to give the KIR a try https://www.reddit.com/r/fslogix/comments/w8ies1/fslogix_failed_to_acquired_logon_lock_on_server/?sort=new
r
I was reading this and was like nice, then I seen @c4rm0 comments. Dang man, I have a POC coming up and will report back to give more use cases. @c4rm0 how does it report with or inside of a VDI/VDA or whatever flavor you are using?
c
tbh i think my issue was the July windows server 2016 cumulative update KB5015808 which was causing my issues (This 2016 server Vdisk was last patched in May 2022). Since applying the KIR to fix KB5015808 its been rock stable but i did also roll back to Fslogix 2201 HF2 to be overly cautious at the same time. I had all the new features Appxpackages/recycle bin roaming/disk compaction turned off so didn't really think it was Fslogix 2210 HF1 causing my issues and they was apparently fixed in HF1
m
I also didn’t have the guts, to try 2210 HF1, yet.
m
We have not had any problems during our inital tests. So as of tomorrow all of our delivery groups will be running 2210 HF1. The new disk compaction feature is currently disabled, but I will start testing it on our delivery group next week. Marco, I will let you know how it goes.
❤️ 1
m
Which of the new features did you disable and which did you enable?
m
Disk compaction and recycle bin roaming have been disabled. The latter mostly because the recycle bin is disabled for our users, so I figured it was better to disable the feature, than having it enabled.
❤️ 1
Have not had the chance to test Disk compaction yet, but we still have not seen any issues so far. I hope to test it next week 🤞
❤️ 1
@Marco Hofmann Disk compaction has now been enabled on our own Delivery Group and my initial impressison is that is works. My own profile got skrunk by 10 GB on first log off and it took around 15 seconds for my session to close entirely. If we run into any problems I will let you know.
❤️ 1
@Marco Hofmann We have not had any problems, so we are going live for the rest of our delivery groups over the weekend. I will update you if we run into problems. If you have not heard anything by Monday 22nd of May, you can safely assume that it is working fine in our environment
❤️ 2