This message was deleted.
# citrix-vad
s
This message was deleted.
j
Citrix recommends their own profile solution šŸ˜„ Microsoft recommends only using the FSLogix profile container.
šŸ’Æ 1
ā¤“ļø 1
b
Citrix also recomends using FSLogix. I dont know where I got the idea to use FSLogix + O365 from a Citrix site 😦 They are not in production. Is it difficult to remove? Or just disabling the GPO will be enough?
j
disable the O365 container and delete the Office containers, that's it
next Outlook launch will be slower since the OST will rebuilt itself
it will also reduce by half the number of files open on your file server
that can't be a bad thing
b
What do you mean by this?
j
each user will mount one VHDX instead of 2
d
Well- if you're a fan of including your Outlook cache in your backups by all means put it in your profile. But to your question, up until recently FSLogix was the higher performing option and many Citrix consultants including myself recommended evaluating it. WEM even has some methods to help manage it, so there is a good... synergy... there. BUT: People often mistake a recommendation to evaluate and compare to a recommendation to use, however.
s
i chose to separate the two due to space and backup/restore constraints. Not going to worry about OSTs in DR, online mode ftw.
d
I haven't played with it yet, but it does appear that UPM is letting us get waaaay more granular these days as to where things can be stored. I haven't tested dedupe yet but I'm excited to do so, exactly for active-active concerns I'm seeing in the world lately.
ā˜ļø 1
h
In Fslogix, Login time is pretty much fast compared to CPM as AVHDX file is getting attached
m
UPM also has VHDX containers available as an option nowadays.
🤘 1
j
Don't forget, FSLogix tattoos the Registry - on persistent devices the settings that drive it will stay until you delete them
UPM containers is overtaking FSLogix, the only thing IMO FSLogix has going for it is maturity. Breaking OneDrive on older versions was the end of FSLogix for me
šŸ‘ 1
h
Thank you @Marco Hofmann.. for the info something new to me
n
Want another reason to go CPM container? You won't have to deal with MS Support.
šŸ“£ 1
b
I would go with Citrix WEM but they don't have access
j
UPM doesn't require WEM
b
But it works way better
j
Debatable
this 1
n
We use WEM to apply CPM here and it works fine, but if I had my way I would be using a Studio policy.
I don't see any benefit to adding another broker in between those settings getting applied or not.
m
I would like to jump in and ask a question regarding UPM Container vs FSLogix, which haunts me for a while: (Ps.: I have never used UPM container, just following the debate here in Slack and reading all the changelogs) How am I supposed to switch and manage versions? With FSLogix I was independent of the VDA version. For so many reasons (not relevant for that discussion), most of my customers are still on 1912 CU3, yet still on a recent FSLogix version. Or in other words, I have a very mixed CSP VDA environment, yet all have the same FSLogix version. Now first, I don't know how I could ever switch from FSL to UPM in an up- and running environment, and I guess I shouldn't. But even if I would start a new project next week, which I do, I would decide for 2203 CU3 and that would cut me from the latest features like OneDrive support I guess. So I guess on 2203 UPM is still not attractive enough to ditch FSL? But UPM is tied to the VDA afaik. I know I could upgrade UPM manually to a higher version, but I guess that would get me unsupported? Unsure about that one. But if I would need to stay on a lower version, like we all do with FSL sometimes, I think I couldn't, so UPM might block my VDA upgrades if there might be an issue through the upgrade? I'm very unsure about the tight integration between the VDA and UPM, leaving me unsure about the stability and supportability from my side as a partner.
n
My guess is that you'd have to run the latest CPM on your 2203 VDA.
Stability I wouldn't worry about personally, but support is another issue. Citrix could easily say 'go back to 2203 CPM and test to see if it fixes your issue'.
j
FSL to UPM migration is easy. UPM is not tied to the VDA version
m
Migration: How so? You leave me confused šŸ˜„ Version: How would that be possible? I exclude UPM from the VDA setup and install my preferred version afterwards?
j
Yes, you can install UPM separately
m
I know, but it never came to my mind, that I can leave it out, during the initial VDA setup.
j
To migrate FSLogix profiles you need to change the folder structure slightly and then simply copy the VHDX
🤯 1
•Create folder structure and ACLs •Remove FSLogix settings completely •Copy container across •Rename it to ProfileContainer.vhdx in the UPM folder •Mount it •Rename the ā€œProfileā€ folder in the root to ā€œProfilesā€ •Log on with UPM container enabled
šŸ‘ 1