search for: clasicupgrade

Greetings - In an offline-test environment, I just took a first crack at a classic upgrade of our Samba 3.6.9 (389-DS LDAP backend) environment to Samba 4.1.13 AD. Among other issues, I see that we have some group/SID issues to address. From the upgrade output: Could not add group name=guests ((68, "samldb: Account name (sAMAccountName) 'guests' already in use!")) Could not add

...4.5.12-debian (debian 9.4) We copied all tdb-files to the new machine plus the smb.conf plus /etc/group. The old Samba has tdbsam as backend. we use the same domain and hostname on the new DC as it was set on the old system. We are using bind9 as DNS-backend in the new system. The "samba-tool clasicupgrade" was running without errormessages. DNS ist running. We can resolve all host- and service-records. We get a list of all users and groups with "wbinfo -u" and "wbinfo -g". We changed nsswitch.conf to: --------- passwd: compat winbind group: compat winbind --...

...orkgroup' is not the netbios name, it is the NetBIOS domain name. > The workgroup should also not have a dot in it, 'DOMAIN.LAN' looks > suspiciously like a dns and realm name. > Indeed i lacked of precision, purpose of the post was more "change NetBIOS domain name during clasicupgrade". DOMAIN.LAN is the previous NetBIOS domain name (I know about the dots, but it was not set by me at the time), and that's precisely what i try to change during the classic upgrade, for a new name (without dot), like "NEWDOMAIN" > > > [global] > > > >   ...