A couple of things to consider here:
- UCS uses metapackages to provide appropriate integration and configuration for services like samba.
- Installation of packages should be done with
univention-install
to use the recommended options for apt. - UCS has a concept of server roles. Some packages are only suitable for installation of particular roles.
- For high level installation of services it is recommended to use
univention-app
which takes the server role of the particular system into consideration. e.g.univention-app list
can be used to see what apps are available (and where they are installed in the domain). - To be able to run SMB fileserver services, at least one system in the domain needs to serve as AD domain controller. To achieve that
univention-app install samba4
can be run, e.g. on theUCS Primary Directory Node
. That system is then automatically able to serve files (e.g. the sysvol for GPOs). - Redundancy can be increased by installing the
samba4
app on additional UCS Directory Nodes (of roleBackup
orReplica
). - Pure fileservers (without AD DC functionality) can be joined by installing by running
univention-app install samba-memberserver
on UCS Managed Nodes (aka memberservers). - UCS has a domain management approach that is based on the Unviention Directory Manager (frontend for OpenLDAP) and a Web management interface Univention Management Console. File shares can be configured there and are then persisted in LDAP and replicated into
smb.conf
configuration (via included subfiles) on the respective nodes. Univention Corporate Server for Debian and Ubuntu Administrators — UCS 5.0 for Debian and Ubuntu Administrators may be interesting if new to these concepts.