If you have users and groups that use the Windows RID as their Unix ID, you should consider changing these before carrying out the upgrade.You should also consider removing any Unix IDs from the 'Well known SIDs', except for the 'Domain Users' group.
To be honest, I've used the apt-get dist-update command only once several years ago and it ended up removing a bunch of packages.The domain is functioning rather well, but they find themselves running into more and more dead ends.Things that a NT4-style domain just doesn't support.It is suitable for upgrading an existing Samba installation, as well as running the migrating on a new server, if you had considered e.g. The classicupgrade is a function built into samba-tool.The intent of this function is to do a full replacement of an existing Samba NT4-style domain. Using Gnu PG, simply download the Samba source distribution, the tarball signature, and the Samba distribution public key.
The Samba distribution GPG public key can be used to verify that current releases have not been tampered with.
For more information, see Build Samba From the Sources.
If you update using packages, read the distribution documentation for information how to update. Start the same daemons as on your previous version: On Samba AD DCs: samba On Samba NT4-style PDC/BDCs: smbd, nmbd On Samba domain members: smbd, nmbd (winbind, if used) On Samba standalone hosts: smbd On Samba AD DCs only: Run the Samba AD DC database check.
The documentation was not very clear about that (at least I didn't find a helpful guide). For example, if you update from 4.4.4 to 4.6.2, read the 4.5.0, 4.6.0, 4.6.1, and 4.6.2 release notes.
Install the latest version over your existing one: If you compile Samba from the sources, use the same configure options as used for your previous version.
On my 16.04 LTS server, I ran 'samba --version" and got back: 4.3.11 When I followed the link in the article to Samba's website, it indicates fixes for some versions, but not for Samba 4.3.11.