This message was deleted.
# microsoft-fslogix
s
This message was deleted.
k
And Windows SOFS as well
j
There be a few nasties in 2210 to be wary of - check out the forums on Microsoft - many satisfied customers 🤦‍♂️
j
I had confirmation this time last year from Microsoft support that CC + CA was opened as a bug with the product team by Jim Moyle. Wonder what happened to that?
j
😶
j
Yep I'm staying away due to the Office credential issue, I assume we need to recreate our Citrix machine catalogs as Hybrid Joined to get around it. I just noticed it was flagged during the public preview, but went out unfixed. Assuming its classed a bug? https://techcommunity.microsoft.com/t5/fslogix/office-credentials-not-saved-between-sessions/m-p/3672669
j
Doesn’t look like a bug - looks like it’s by design so far…
And you won’t need to recreate your catalog, just use GPO and AzureAD connect to sort out the hybrid stuff
j
its always been a hot mess , especially with FAS breaking the Primary Refresh Token. Somewhere I think i read something that a Hybrid join machine catalog may work better in this respect.
j
The new CA stuff should resolve the PRT problem but it’s not as pretty as one would like, I can’t keep up with what works and doesn’t and where it explodes @Shane Kleinert and @Oz Zy are all over it with active projects in that space
j
I'm not up to date either - this article suggests an update is required to each VDA OS. https://www.julianjakob.com/citrix-fas-azure-ad-cba-with-primary-refresh-token-prt/
j
I need to retest latest but last few versions CA and CC was still an issue
n
I had so much hope for FSL when Kevin was running that ship, years later I still haven't migrated to it off of good ol' UPM. Not sure if I ever will at this point with all the horror stories. Maybe there's hope for citrix containers in the future with 1 throat to choke. My ticket with M$ on FSL took them 3 years to resolve with v4 printer drivers....
o
Yea, its obvious MS bought it to fulfill a need for pushing AVD and put it in a corner at that point. Sort of 'on your own' approach with it as MS support obviously doesn't focus on it.
r
It's sad. an excellent product that was bulletproof before. Now it seems like swish cheese. Unless you deploy older versions. 2205 HF1 from what I'm told is ok.
Fix Fslogix lol