Hi team, I used to override the SMB options of each share when deploying CORE (recycle bin option with a different name and folder). On SCALE this doesn’t seem to be allowed. Will this work in a future version?
Thanks. The standard recycle capability is not sufficient for many raisons.
I manage several hundred network shares and I use the recycle bin overloaded options to handle different cases. It is common for share administrators to modify the smb4.conf to adapt business cases with these options: vfs_recycle Additionally in SCALE: (recycle:exclude = LIST, recycle:exclude_dir = LIST, recycle:maxsize = BYTES …)
In addition, the default options do not seem optimal to me. For example:
This option places the user’s deleted file in .recycle/DOMAIN/USERNAME. I think this is not good because for a common share with several users, users have to look in which folders the deleted file is. Believe me, my users are not very good at IT. My users are French and want the recycle:repository to be called “Corbeille”. By default it is .recycle. However, if we put a dot in front of recycle, Windows hides the folder and users do not see it, this forces them to display hidden folders but we do not like that.
In short, before we could overload the additional parameters of the shares and today this does not seem to be the case. I know it is more complicated for the middleware but as a share administrator it is really useful. From my point of view, it is a regression.
Thank you very much. I can open a Jira ticker if necessary.
We touch on this in this thread which you may find interesting.
Having the ability to tweak/add SMB parameters within the UI is very useful and in my opinion I agree it’s a regression from CORE. I appreciate it can lead to unknown outcomes however perhaps a warning that says ‘USE AT YOUR OWN RISK’.