If you're on a newer system, you'll have had to make security changes to allow the old-style domain to be joined...
but if you eventually get a "welcome to the xxx domain" you're most of the way there.
Anyway, it would be nice to have some hooks for alternate ways of dealing with this.
I am trying to configure a Linux Debian host to be a Primary Domain Controller which will have Windows hosts in the domain.
I've set up Samba version 3.3.6 according to the short instructions in and verified those settings with https://wiki.samba.org/index.php/Samba_&_Windows_Profiles.
Unfortunately, the former link doesn't say what to do next after configuring samba.
The last MS Operating system that relied on this type of domain was Windows NT (Workstation & Server), but backwards compatibility has been retained thru Windows 2000, Windows XP, and to a lesser extent, Vista.
(Broke, to me, means that there is something you want the system to do that it cannot do now, but that a new version will presumably fix. Dan IT4SOHO Squarespace’s all-in-one platform gives you everything you need to express yourself creatively online, whether it is with a domain, website, or online store.
I've searched a lot and have come up with lots of links, but no real step-by-step that gets me there. For one thing, should I forget about samba 3.6.6 (the latest available with Debian) and get/install version 4.x.x?
The 4.x.x version advertises DC/AD support, but there seems to be plenty of posts where people have gotten earlier versions to work. Switch from workgroup to domain, enter your domain name and click ok.
For clarification and put another way, does this mean Windows 7 or 8 *cannot* natively join a pre-Samba4 implemented PDC domain (without registry changes? Googling on various blogs seems to indicate that the "ancient" domain can do roving profiles, folder redirection, etc. ps, I totally agree with your "if it ain't broke, don't fix it" philosophy!
) Conversely, will XP join to the Samba4 AD/PDC ok, or should I not use XP in testing this setup? ): Provision failed - Provisioning Error: Your filesystem or build does not support posix ACLs, which s3fs requires.