1 Three possible viable approaches:
2 1) TDB conversion approach. Read in TDB dump out LDIF (one-way)
3 - samr.ldb: from tdbsam/smbpasswd, account_policy.tdb, secrets.tdb, group_mapping.tdb, idmap.tdb, privilege.tdb
4 - registry.ldb: from registry.tdb
5 - wins.ldif: from wins.tdb/wins.dat
6 - smb.conf/ea's: generated from the old smb.conf + share_info.tdb
8 (one-way upgrades can be done by using ldbsearch -a on these dynamically
10 Since TDB's are local, there isn't much point in writing back backwards
13 2) samr "mapping" backend (alternative for samr.ldb) (two-way)
14 This would allow users to keep mixed domains containing Samba3 and Samba4.
16 3) The vampire way of doing things (one-way)
18 - Samba4 vampire + server side samsync support in Samba3
19 - unixinfo (\unixinfo)
20 - in Samba4 (client side)
21 - in Samba3 (server side)
22 - winsrepl (thru seperate pipe?)
23 - enum/add shares (\srvsvc)
24 - enum/add registry (\winreg)
25 - enum/add printers (\winreg, perhaps also \spoolss(?))
26 - convert smb.conf (using Jerry's registry hack)
28 (going with a combination of 1 and 2)