search for: 3ldap

...ing from Samba 3 into the Samba 4 domain (i.e., both LAN and AD-LAN will co-exist in the same network for some time). So the question, how do I do the upgrade to Samba 4 while importing the users/groups from Samba 3 domain in this case? Alternately, how can I import Samba 3 entities from Samba 3LDAP backend *after* creating a separate Samba 4 domain? Also, what's wrong with '--realm=ad-lan.com' ? Thanks. Sincerely, Konstantin

...the Samba 4 domain (i.e., both LAN and AD-LAN will co-exist in > the same network for some time). > > So the question, how do I do the upgrade to Samba 4 while importing > the users/groups from Samba 3 domain in this case? Alternately, how > can I import Samba 3 entities from Samba 3LDAP backend *after* > creating a separate Samba 4 domain? > > Also, what's wrong with '--realm=ad-lan.com' ? The main thing is that the upgrade code ignores it! The classic upgrade is built upon doing just that, upgrading an NT4-style domain to an AD domain using the same workgr...

Hello, Going further with migrating NT4 domain (Samba 3) to Samba 4. Thanks for the previous suggestions. When doing # samba-tool domain classicupgrade --dbdir=/usr/local/samba.LAN/ --realm=ad-lan.com --dns-backend=BIND9_DLZ /usr/local/samba.LAN/smb.conf --option="interfaces=lo ens3" --option="bind interfaces only=yes" I see in stderr the below: Ignoring group

...(i.e., both LAN and AD-LAN will co-exist in >> the same network for some time). >> >> So the question, how do I do the upgrade to Samba 4 while importing >> the users/groups from Samba 3 domain in this case? Alternately, how >> can I import Samba 3 entities from Samba 3LDAP backend *after* >> creating a separate Samba 4 domain? >> >> Also, what's wrong with '--realm=ad-lan.com' ? > > The main thing is that the upgrade code ignores it! > > The classic upgrade is built upon doing just that, upgrading an > NT4-style domain...