Not everyone needs Windows Shares, although most SMB companies do. Pure Cloud servers do not need Windows shares for example. PCs could use eg Nextcloud to sync data.
Must be, otherwise having a second AD would NOT be possible!
(I’m not saying what must be done with the internal firewall of NS to make that work, never tried that…)
That wasn’t an RTFM from you, but you would of course be right. Unfortunately, I often forget to watch the documentaries again after I’ve already done so (in the past).
To be honest, I would prefer having a second AD in my domain, but completly independant of any NS8 cluster.
That way anything AD dependant would still work, even if NS8 has a full cluster error!
Most if not all File Shares are on OpenMediaVault NAS (Mostly VMs!), all OMV are AD integrated.
AD dependant Apps would work too!
PS:
I do plan on creating a HowTo for such an AD, based on Debian and NS8 independant, but intended as a fail over for the AD in NS8, including SysVol and NetLogon Sync…
Might be a few weeks, but when I have the time, I’ll get it done and published online…
Are you talking about an AD slave? That would make a lot of sense. A separate node in the cluster would be a good idea, but the developers don’t seem to see any need for it - at least not yet, or not urgently. A separate node would be fantastic, as long as it is regularly supplied and configured by the NETH8 AD (master).
Any DomainController (DC) can be promoted to be the master.
All other DCs can be removed, as long as DNS is correct, everything will still work!
That’s my vision for the “second” AD.
And that also means it can be in the NS8 cluster, on a different node - or completly independant, a small Debian VM that can run on any Proxmox. As I expect the devs to integrate a second AD sometime in NS8, I’ll concentrate my efforts on an independant AD, capable of carrying any AD needed services until the real master is back online including the whole NS8 cluster.
I plan on including the SysVol and NetLogon sync also.
And WSDD !