https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# microsoft-fslogix
s
This message was deleted.
b
@Nick Panaccio @Peter Robson @Jarian Gibson I opened a support case with Microsoft... Here is their response. “We strongly recommend that you do not do that, dedupe and compression will cause it to not work properly.”
n
Please tell me that they were only referring to dedupe and compression in NetApp only...
b
I copied/pasted their reply.
I’ll find out.
p
They won't able to answer that trust me - as ex FSLogix support engineer
n
That would certainly change things for most of us.
p
I'm sure that only applies to software options
Dedup defo works
Who the support handler ?did they give a KB
b
David Weaver, no KB
p
Let me check my with my colleague Omar in morning and my PC with FSL support notes I have - compression on OST volumes no is a defo David Weaver a good guy he probably asked senior analyst
Ps do.a small PoC with compression enabled
I also check what I wrote for the dell islion install
n
I know I'd appreciate it. Our Profile and ODFC files are all going to be stored on the same share, so if compression is out of the question for ODFC, then I need to make some changes.
p
@Nick Panaccio I would not suggest the same share for the ost and profiles, can I ask what you are storing in the odfc container
b
When I asked if only NetApp had issues. “For FSLogix just compression and dedup in general will cause issues with FSLogix .VHDs.” I’m going to ask if there is a difference between hardware/software or in general.
n
@Peter Robson Office activation, cache, Outlook data and personalization, SharePoint, Skype, and eventually Teams. We haven't moved to O365 yet, so the ODFC isn't going to have the .OST files in them yet.
p
I would suggest a separate share for I/o extra,
n
Gotcha. Now I need to figure out how to estimate .vhdx growth. I assume that the ODFC file is going to outpace the Profile by a good margin.
p
@Aaron Parker did a good article on growth. When I was on support I would suggest to customer (oSt size +50 % for ost rebuild and problems +10 search +10 growth) so I would suggest the same for largest amount of data + growth You can migrate to a large vhd if it filla
n
I have the limit currently set to 10gb, though I hope it never gets anywhere near that. We're limiting the cache to 3 months of mail, which should help.
p
Remember to add the orphaned ost registry key it tides up a lot of crap
👍 1
n
That I do not have enabled, so thanks again.
We also currently don't have search indexing enabled, and it's likely to stay that way for the foreseeable future. Never really had a push by anyone to turn it on, too. Looking at my handy dandy FSLogix growth estimate spreadsheet, it looks as though I was estimating 20% growth in each .vhdx per person, per year, with a 20% growth in the user population annually. My initial estimate was for both containers equaling 750 MB in size, but I know that's pretty high for the average user. So, 200 MB for the Profile and 300 MB for the ODFC initially. We redirect Documents, Desktop, and a number of other folders, which certainly helps.
b
Another reply... “I cant find any documentation about it, we have had tickets with customers having issues that turned out to be from compression an dedupe. I imagine its probably the same regardless of hardware or software. The main issue is slowness and random unexpected errors, you can try it if you want but we would not be able to provide support while that is active.” Guess we need to test with and without.
n
It’d be nice if they collected their data and checked for a pattern.
a
@Nick Panaccio you’re going to hit that 200mb mark on a Profile Container pretty quick. I wouldn’t be surprised if you see that in first login
n
That’s where I got the estimates from. Initial creation and first log off equals a 196MB file, so my estimates start there. My containers are dynamic and limited to 10GB. With normal use, I didn’t see my profile container really growing too much thanks to the fact that we redirect a lot of data, and also don’t save IE nonsense.
@Aaron Parker Peter mentioned that you had an article on growth. Any chance you've got a link to it?
p
Spoke with me colleague and yep compression needs to be off, dedup might work I guess if MS are saying it needs to be off and they won’t support it then you need to do what they say
👍 1
b
Thanks for following up @Peter Robson
I did ask for an official KB article to be authored
n
Thank you. So compression, regardless of hardware or software, need to be disabled?
p
Off
n
I wonder how many people are actually following that guideline. Ironically enough, after questioning our storage guys, I was told that we have compression enabled, but dedupe disabled. They also didn't particularly care for my suggestion that we use beefier file servers, and split the current share into 2 for each container.
p
Multiple shares is best practice but I suppose if it a net app it won’t matter - just be careful that if you log a call with support that you have to have a battle for multiple shares :)
n
Oh, ours isn't NetApp. We're on EMC VMAX... not that it apparently matters here
@Peter Robson You've had good success with the RemoveOrphanedOSTFilesOnLogoff key? Aaron Parker's blog is literally the only other place I can find that referenced the setting.
p
Yes it a registry key.under ODFC. There Times we're outlook doesn't shutdown and that helps with the numerous OST’s created
Also keeps the container size down
n
Unless I'm missing something, it's weird that they didn't just include a GPO toggle for this. Gonna have to use GPP to set it since it's an HKLM key.
2 Views
Open in Slack
PreviousNext
Powered by