This message was deleted.
# microsoft-fslogix
s
This message was deleted.
t
Depends on what you are trying to accomplish. If you want FSL profiles (instead of UPM, AppSense, etc.), then enable both. If you just want Outlook / Office, then enable ODFC.
Also depends on whether you want separate profiles - you could put everything in a profile container. Or, if you want to split load / IO, then use both.
n
i did enable both....christian brinkhoff and i are going back and forth on some stuff and he asked why i enabled both, my answer was i thought i had too.
j
Some people do use both
One possible reason is you could blow away the Outlook profile without losing the entire data set
There was quite an active discussion on CTP Slack about this IIRC
n
waiting to see what christian says, just b/c it is technically possible to combine them wouldnt be something i would wanna do
j
There's no multi-user search in the full Profile Container, so O365 container may be needed in XenApp/RDSH scenarios
😲 1
j
I like to use both. The office 365 container is cache and not as important as profile container in my opinion. Especially if using cloud cache. Only need to cover that for profile container.
m
I agree with Jarian. If a user has Outlook OST/multi-user search + their OneDrive in an O365 container that's all cached data and if you need to blow it away/reset it you don't have to worry about killing the user's profile container. Also it gives you the flexibility in your design to have two different file shares/servers and storage volumes for the profile & Office 365 containers
💯 1
m
@James Rankin this statement is new to me,..the documentation does not mention that, right?
j
Dunno, I don't read documentation 🙂
Might be worth checking with Cassondra or someone, I know it's a fluid area
👍 1
j
See bottom
n
christian sent this to me today, honestly for years i thought they went together like pb & j