I would counter that with that you should probably should not need/use tweaks in production 
oh please stop being so obtuse and tedious, how else am i going to be able to configure SMB correctly for my env when the UI lacks so may missing SMB options / optimizations
unless you are telling me i am expecting too much from this OS?
i would also counter if i am not supposed to edit a file make it read only and only editable via UI… never give users a hangnail (smb settings are store in the same dataset as AD)
also it was a simple soution - one create a data set, configure active directory, move system data set back to boot pool
this is just a simple matter of outdated check that is pointless, it doesn’t actually care if the system dataset in
thank being yet another forum person who delights in telling people they are wrong rather than every actually helping , why do you spend so much time posting and adding ZERO value to the conversation, genuinely i am intrested to learn what motivate so many of you to spend so much time doing that on the forum
tbh its why i now rarely bother coming here - you are all making such an ‘awesome friendly and inviting community’
AD is “critical” in environments that use it, the point is that it is not critical to the operation of TrueNAS itself, and that’s what the area you want to store AD related data in, critical to TrueNAS itself.
I’m also wondering what exactly AD related you want to store there? AD is either going to be a Windows VM a Linux VM running samba, or maybe samba AD in a container. Those should be stored in an area that is not considered disposable, which the boot pool is for all intents and purposes, if they’re so important.