Hello, Outsider
> I apologize for the long delay in my response. We are using standard Unix-based ACL permissions managed via Terminal and the Server app.
This should work
> As I said I have very complex permissions due to the nature of our office and I sometimes have to add entirely new sharepoints; I see on SMBup's GUI that it looks like it requires sharepoints to be created in the interface itself.
No. SMBUp lets you create the shares in SMBUp if you wish to. You can also create them by editing the Samba server config file: smb.conf.
> I recall someone saying that you don't even need to do this portion if you've already set up the fileshares in the Server App; this individual seemed to think that once users were created all that needs to be done is simply unchecking AFP and SMB on the shares in the Server App and SMBup (Samba itself rather) will continue sharing what was already there. Is this correct?
I would be surprised if it is. OS X SMB uses a wholly different way of setting up shares, and samba is unaware of it. Everything that samba does, needs to be done in the samba config.
AFP is unrelated. You can leave AFP enabled and it shouldn't affect anything.
> Again, the environment that I am running the Mac Server in is one that's extremely important to ensure that all of the unknowns have been quantified before deploying any major modifications.
Easiest would be to try it out, I think.
> As a side note, I'm aware that SMBup is simply a GUI for Samba, and using the term "deploy" in my industry (in the ten years I've been doing this thus far) is simply a short term to imply the installation/usage of a new software/hardware implementation. Semantics aside, I appreciate your help greatly.
I've been working in the IT industry for over two decades. I'm aware of the terminology. But it's important for me to have people be extremely clear that the bulk of what they're installing is Samba, to which SMBUp is just a front-end. If you already had samba you could still run SMBUp. The clarification is not about whether the term is correct, but that what you're "deploying" is in reality Samba. You insist that you're trying to have all information clear so I'm making sure that bit of it is also clarified from my side.
It's important because most of the problems people have when installing SMBUp are actually with Samba itself, and unless it's a common problem I already have a FAQ for, I send people over to the Samba help forums for help.