[Samba] Ubuntu 20.04 setup

L.P.H. van Belle belle at bazuin.nl
Fri Jun 5 08:54:51 UTC 2020

Hai Greg, 

> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> Gregory Sloop via samba
> Verzonden: donderdag 4 juni 2020 19:17
> Aan: samba at lists.samba.org
> Onderwerp: [Samba] Ubuntu 20.04 setup
> Louis, et al. Hi!
> So, I'm working on a 20.04 setup. 
> I think I'll still use the distro version and not Louis' 
> packages. [No offense Louis - I just need to be sure if 
> (forbid) anything happens to Louis, his packages aren't going 
> to be supported any more, and I'll be on my own for security 
> updates etc. The 20.04 versions are pretty current, and I 
> think will meet my needs for the life of the distro. If not, 
> I can always re-evaluate that at the time.]

Ah, totaly understandable and i get that.  No worries ;-) 
So if i suddenly would get run over with a train, what then
Well, simple switch back to official packages, using these commands.

apt-get remove samba winbind samba-* --autoremove 
apt-get install samba winbind
And your done. ;-) 

You only miss spotlight support then. 

But im lucky, so far i dont see trains here ;-) 

> So, is there anything new in 20.04 I need to be aware of vs 
> 18.04? systemd.resolved seemed to be the biggest "gotcha" previously.
> Anything else that's different in 20.04 I should be aware of?

You can still use that howto yes, i have a new base for 20.04 but not finished.
Cant post it yet. But after today i have 3 weeks vacation, i'll do some howto updating
Since i took the best weeks for vacation.. with rain.. :-( 
and not going anywhere, Its still to soon in my opinion for that. 

> I'm planning on using the 18.04 walk-through you [Louis] did 
> 18mo or so ago - with a few changes to meet my needs. (eg. 
> I'm using internal DNS, not BIND9, etc.)

Well, on that part, if you switch to full systemd setup. 
what i personaly do like, you need to "correclty" remove/switch on ubuntu. 
Or completly remove netplan and all crap that was added and configure systemd-networkd manualy
Or use netplan to configure it and use 
I just dont like netplan so i remove it, thats a choice. 

If you use multihoming/multiple interfaces. 
Dont configure : /etc/systemd/resolv.conf 

Configure DNS and routings withing the needed interface ( can be in mutiple files as look you watch the loading order. ) 
Eth0 (lan) -> DNS samba 
Eth1 (wan) -> DNS internet 

On AD-DC, use ntp, oblicated. (due sntp and AD to distribute time to pc's), 
i dont advice chrony. But again thats personal, chrony should work.

On members, dont install ntp, just not needed, configure systemd-timesyncd point to AD-DC ips. 

And last tips if you use systemd, is optimze your boot process. 
systemd-analyze plot > boot-prosess.svg 
IF you use that and are optimizing the boot process.
Use : systemctl edit servicename 

That keeps everything clean and that avoids touching/adjusting by debian/system suplied files.

Test that a bit, and if you boot setup if perfect. Enable unattended upgrades, yes then you can. 
My boot prio is. 
- wait for network
- enable bind
- enable ntp
- enable samba 

A simple example on smbd ( this applies for all samba services but you need to to it for nmbd smbd samba samba-ad-dc ) 

systemctl edit smbd
After=network.target network-online.target nmbd.service winbind.service bind9.service

All i add here is : bind9.service ntp.service
Save and done.

If you dont use it, fine also but now its always starting correctly if you use bind9 or ntp or not. 



More information about the samba mailing list