This message was deleted.

I like the idea of them being segmented incase you need to split them for IO reasons - easy to simply change the path for ODFC for example and have that component moved onto different disk

That's what was suggested to me the other day, and I'm annoyed that I didn't think of it beforehand. So yeah, that's definitely the plan. I just need to figure out if it's worth creating a folder on each share for each user (i.e., \\Server\FSL\Profiles\Panaccio)

Do you mean - throwing both Profile and ODFC into a single share? So that way there is a single subfolder per user which contains both the profile, differencing and ODFC vhd files? I imagine that's valid but we chose to separate for the reasons already mentioned.

No, I'm definitely going to have separate shares - 1 for Profile, 1 for ODFC. I mean within each individual share, so if I browse the Profile share I'll see all files listed directly in there. In QA, I've got them all in a folder for each user, but I don't see the point in going that route now.

I see - depending on your concurrency setting, at logon each user gets a RW.vhdx differencing file created in their profile subfolder. Obv can't have 500 RW.vhdx files in the same folder - so i don't think the product will let you not use subfolders?

No concurrency here. This is only for non-persistent XD users.

So your 'Profile type' setting is set to 'Direct Access' (or 0 in the reg)?

Yeah, I've got the No Containing Folder GPO enabled because using SIDs just looks sloppy to me. Profile type is the default 0, as well.

I'm sure you know this but we changed the naming convention of the folders to something more useful to us - ie. username first so they're in alphabetical order was a good start!

I did, yes, just not a fan of the SID. 🙂

We are all just a SID at the end of the day 🤷‍♂️ I like basics with fslogix, try not to stray too much from standard configs - easy to track and work with IMHO

I was just trying to think of a reason where I'd need the user's SID. I see your point, though.

Probably never my friend, its ugly as a bag of balls 🤦‍♂️

lol

I'm also doing no containing folders and using %username% in vhd location, makes it much more neat and easier to script later on. Most of the compacting scripts are using gci -recurse with *.vhd(x) so it's not an issue so far ,but you never know 🙂

Something I’d like to call out, pay attention to your storage vendor and the number of folders in a folder limit. For Isilon or NetApp it’s ~100,000 folders in a folder