1 |
On Tuesday, March 22, 2016 02:29:12 PM Stefan G. Weichinger wrote: |
2 |
> Yesterday I hit samba bug id 11538 at a customer. |
3 |
> |
4 |
> https://bugzilla.samba.org/show_bug.cgi?id=11538 |
5 |
> |
6 |
> We still run stable samba-3.6.25 on gentoo there, with a basic NT4-style |
7 |
> domain. Simple use case, just users/passwords, no logon scripts, no |
8 |
> server based profiles ... |
9 |
> |
10 |
> Now I consider upgrading to samba-4.2.9 (~amd64) to maybe get around |
11 |
> that bug and in general improve support and compatibility with more |
12 |
> recent versions of MS Windows (first w10 clients coming up ...). |
13 |
> |
14 |
> Does anyone in here has done that, how clever is it to stay with |
15 |
> NT4-domain in combo with samba-4.x ? |
16 |
> |
17 |
> I just want to keep the steps small, I understand that an AD-based |
18 |
> domain will be the way sooner or later. |
19 |
> |
20 |
> Any stability or performance issues with samba-4.2.9 in gentoo? |
21 |
> |
22 |
> Thanks for any feedback on this, Stefan |
23 |
|
24 |
First: I have not migrated to Samba 4 myself yet. As I simply refuse to |
25 |
support Office 365 (I use my own mail+groupware server) I am unlikely to hit |
26 |
that bug. |
27 |
|
28 |
But, when I do get around to migrate to Samba 4.x, I would migrate to a full |
29 |
AD environment. I am still checking a few options myself as I am using |
30 |
OpenLDAP extensively for a variety of configuration settings and merging that |
31 |
into an AD-style LDAP tree will take time. |
32 |
|
33 |
-- |
34 |
Joost |