https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# microsoft-fslogix
s
This message was deleted.
j
Yeah it's a bit pants
I've been holding off for a while now on updating the version in my Chocolatey repos
a
Enabling 3 new features by default seems to be a bit too much... should have been optional by default then one can choose to enable as and when.... also, I noticed that disabling recycle bin roaming after it was enabled doesn't have an effect as it's somehow being remembered in the user VHDX... still looking to see which reg key can remove the recycle bin redirection... it's PITA
j
Don't forget, a lot of FSLogix GPOs don't write to Policies keys therefore they get "tattooed"
😑 1
a
yup... not great
d
Yes on my latest demo env. I switch back to the good old version 2.9.7349.30108
a
We were on 2.9.7838.44263 and it was working well.. I am switching back to this version
j
Touche @Deyda - my repo
💯 1
d
This is the Stable (Preferred by Deyda) Version from NeverRed^^ No Problems with this ^^
j
And it still handles asynchronous logons....
d
exactly..
a
Tempted now.... it's 2 years + old though....
d
Oldie but goldie ^^
😊 1
r
I find 2.9.7838 pretty darn stable
j
Not sure if it's related but this week I started to see black screens at login in test env. after deleting profile. Noticed run once wrapper executable if I kill that login continues. Didn't troubleshoot that yet thought it might be related to Onedrive. (AVD remoteapp).
j
I've just updated some test boxes to the latest version and all my (test) users now have locked profiles 😡
a
Can't believe this was released as GA
r
you sound surprised....
🤣 1
This is why most of us stay well back of latest... it's everyone/everywhere
2.9.7838 with the Parker/Moyle's shrink scripts is solid.
👍 1
d
My preferred setup ...
a
I have been on that setup and was pretty ok - stupid me thinking new features and fixes will improve things... lol
r
Just remember... QA is GA.
a
Lesson learned
f
Same here 2.9.7838 works fine, tested latest on UAT on release even with all the new features disabled we were experiencing random service crash
👍 1
r
You guys have the older one stored somewhere I can snap it? I been seeing black screens as well on the latest in my testing.
m
@Ray Davis check the release notes: https://learn.microsoft.com/en-us/fslogix/whats-new You can download the previous versions from there
r
Hmm I did, I could only go back so far. Let me look again.
My fault, I was looking for an older verion. I though 2.9.7838.44263 was the 2004 verion sorry.
m
oldest version I see there is 2.9.7838.44263 (2105)
r
Yea, I need this version 2.9.7349.30108
which is 2004 I think
Which I don't see, unless I am missing it lol
m
I still have a 2.9.7654.46150, which I guess must be older than 2105
r
2.9.7349.30108 is 2004. That is the best one. I had it. But can't find it now.
r
@Ray Davis I have the following
DM me if you want a link
j
I have loads of old ones too
r
Tried the latest but reverted back to 2.9.8228.50276.
r
Sweet thanks guys. DMing you now @Ryan Gallier
FSLogix is a love hate relationship at times lol I love it, but when an updates comes out. I ask myself why or what will break.
😂 1
o
Even more problematic is forcing AADHJ essentially by removing any sort of roam for the Microsoft AD Broker plugin content. Another 'feature' by design. similar to async processing going away. FSLogix quickly becoming a dumpster fire
⤴️ 2
r
Unfortunately, I am starting to feel the same way.
m
I'm back from vacation and started planning this month's Master Image upgrades. I was thinking about testing FSLogix 2210 (2.9.8361.52326), but this thread seems a bit discouraging ^^ I think I will skip this for the time being.
👍 4
g
same for me - just wanted to start creating a rollout plan, but this thread makes me thinking. We're at 2.9.8228.50276 without any issues since half a year.
👍 3
a
You are welcome 😬
d
I can confirm that the latest 2210 release is a mess 😠. Don’t update if your current version is stable.
👍 3
r
So from this thread we can conclude that 2.9.7349.30108 is the best, although I've had no problems with 2.9.8228.50276 and some releases before that (apart maybe for some strange behaviour with 365 credentials and of course no asynchronous logon). I however had this problem https://learn.microsoft.com/en-us/answers/questions/229309/fslogix-unclean-logoff-causing-locked-files-until.html?childToView=1128616#comme[…]128616 . And here as well, people are referring to .30108. So basically this software has not improved in about 2 years, rather the opposite since asynchronous logons has been removed. Sad!
j
Yeah Microsoft bought it just to fill a hole in AVD and they've basically let it go to seed since
👍 1
😢 2
r
2.9.7838 with the Parker/Moyle's shrink scripts is solid.
💯 1
r
Stay clear of 2210.
m
We just upgraded a customer to 2210 to potentially fix the black screen issues, but it hasnt made any difference. We are on 2016 though, and looking at it being this: https://www.reddit.com/r/fslogix/comments/w8ies1/fslogix_failed_to_acquired_logon_lock_on_server/ Anyone else using it on 2016 still or are we just old news? 🙂
v
QQ. When you revert back to an older version do you guys also copy back the admx files from that version?
a
Only if GPP settings were removed in a newer version… otherwise you should be fine with latest ADMX providing you keep in mind that extra settings in newer versions will have no effect on your older version of FSLogix
👍 1
r
Main reason I always configure with GPP. Don't have to mess around with updating the ADMX files all the time
⤴️ 1
💯 1
a
Their ADMX is nothing but a bunch of GGPs anyway 😉
⤴️ 1
r
Exactly
c
Just testing 2210 now out in UAT wish me luck 🙂 I disabled the roaming of the recycle bin and the installappx components which seem to be causing issues with black screens so will see how i go
👀 3
11 Views
Open in Slack
PreviousNext
Powered by