Can OMV adverise a single Network Share, but subfolders have different permissions (How to simulate a Windows Network Share setup)

1st Official Post
    • New

    Newbie to OMV, but very seasoned Microsoft Windows administrator.


    I am replacing an solid home server (Windows Server 2008 VM on a VMware ESX host on Dell enterprise hardware). Yes, it is no longer supported and a security risk, thus the OMV install...


    I built a Raspberry Pi 5 have have used the scripted OMV install for Raspberry OS Lite (Debian). I have begun the Docker install and I am following the newbie guides on omv-extras.org (I will install Docker containers for the apps currently running on the Win2K8 server and will use OMV SMB/CIFS for the shared data on this network).


    My Windows clients and groups all are operating in a workgroup. The clients have identical local user accounts which map exactly to the Windows server local user accounts and groups. The passwords and character sensitive usernames match. I'm replicating the setup on OMV.


    After reading the wiki.omv-extras.org and docs.openmediavault.org it seems as if my single SMB share with different subfolder permissions is not an eligible configuration. So many warnings about avoiding ACLs and just keeping things simple. For the end-user (my family) they have grown accustomed to simple, indeed. One share. They browse up and down a list of subfolders for home directories, household directories, music, photos, etc., with appropriate read-only, no access, or read-write as necessary.


    Also, my Docker container apps will need to have access to some of the subfolders, I assume dedicated "appuser" user accounts can be granted appropriate access along with the Windows users.


    Can I create JUST ONE top-level network share on OMV in the SMB/CIFS service, but set Linux (local) Shared Folder permissions all from within the OMV GUI? I would rather not fiddle with CLI and "void the warranty" of OMV. If so, I can't find this use case in the documentation. I'd rather not retrain my family (and break their shortcuts) to nine or ten new SMB network shares just to fix what is a very easy, simple permissions setup under Windows server...



    Want this: (one SMB network share "data") - Microsoft "whack \" is deliberate)Not this: (12 shares!)
    data\
    data\business
    data\financial
    data\pictures
    data\household
    data\downloads
    data\music
    data\fing
    data\george
    data\barb
    data\jenny
    data\ben
    data\mike
    		business
    financial
    pictures
    household
    downloads
    music
    fing
    george
    barb
    jenny
    ben
    mike




    P.S. I have searched this forum and can't find a similar question.

  • ryecoaaron

    Approved the thread.
    • New
    • Official Post

    if you browse the network in windows, you would see the server in either situation. In the situation you want, the user would have to select share and then the folder. If the omv situation, the user would just pick the "folder" which is a share. So, literally one less double click. shares and folders even look the same. Using the omv situation would simplify the permissions A LOT. You would have to use command line and/or ACLs to make different permissions with the one share situation and you would fight OMV's design in almost every direction.

    omv 8.0.6-1 synchrony | 6.17 proxmox kernel

    plugins :: omvextrasorg 8.0.2 | kvm 8.0.2 | compose 8.1.2 | cterm 8.0 | borgbackup 8.0.2 | cputemp 8.0 | mergerfs 8.0 | scripts 8.0.1 | writecache 8.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • New
    • Official Post

    Furthermore, at the file system level, you can still maintain the same folder organization. You can even create a shared /data folder to facilitate some server administration configurations, such as backups, etc. But there's no need to share /data with Samba.

    • New
    Quote from geoperkins

    I am replacing an solid home server (Windows Server 2008 VM on a VMware ESX host on Dell enterprise hardware). Yes, it is no longer supported and a security risk, thus the OMV install...


    I built a Raspberry Pi 5 have have used the scripted OMV install for Raspberry OS Lite (Debian).

    Does this mean your Pi5 is the replacement for the Dell enterprise hardware or just a test-bed for trying things out? Is the Dell up to the task of running a Linux server is what I'm trying to say?

    I can't help wondering if you would be better off using something like AlmaLinux, Rocky, Debian or OpenSUSE instead of OMV. I think that's what I would do. I am not knocking OMV in the least, I think it's fantastic but maybe not the right thing for you.

    Quote from geoperkins

    Can I create JUST ONE top-level network share on OMV in the SMB/CIFS service, but set Linux (local) Shared Folder permissions all from within the OMV GUI? I would rather not fiddle with CLI and "void the warranty" of OMV. If so, I can't find this use case in the documentation. I'd rather not retrain my family (and break their shortcuts) to nine or ten new SMB network shares just to fix what is a very easy, simple permissions setup under Windows server...

    I wondered if you could improve the shared folder situation by setting up home folders for each family member (ie NOT under the data folder). The experts here would know better than me about that.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login