similar to: Comprehensive re-write of the classicupgrade HowTo and other changes

Hi i'm actually trying to migrate my samba 3.6 PDC NT-4 domain with openldap as backend to samba4 AD type domain witch bind_dlz so i followed the documentation https://wiki.samba.org/index.php/Samba_Classic_Upgrade_%28NT4-style_domain_to_AD%29 the command : samba-tool domain classicupgrade --dbdir=/root/sambe/ --use-xattrs=yes --realm=mydom.local --dns-backend=BIND9_DLZ

On 21/01/15 13:32, miguelmedalha at sapo.pt wrote: > It is always useful to read the release notes ;-) > > With Samba 4.2, if you want to use the winbind daemon instead of the > internal winbind you have to include: > > server services -winbind winbindd ... > > That is the least of his problems, he needs to fix his smb.conf *BIG* time, he also needs to understand that

> > Then why can the upgrade not contact the ldap server ? I dont know! :( Was ldap running on another computer before ? I installed a temporary openLDAP backend on the new host. Can you post the smb.conf from the old PDC ? the one you are trying to > upgrade from. I sent my smb.conf to your private e-mail. On Thu, May 21, 2015 at 3:08 PM, Rowland Penny <rowlandpenny at

On Mon, Apr 27, 2015 at 4:11 AM, Rowland Penny <rowlandpenny at googlemail.com> wrote: > It sounds to me that you are not going about this the right way, you need to > follow the instructions on the wiki page: > > https://wiki.samba.org/index.php/Samba_Classic_Upgrade_%28NT4-style_domain_to_AD%29 That's the wiki page I used. The LDAP stuff doesn't apply as the current

Hi, We are looking at moving from a Samba NT4-Style domain to Samba 4 AD. We currently have two NT4-style domains set to to trust each other. Is this possible with S4 AD domains? I guess we will probably lose the IDMAP accounting (which was stored in LDAP) when we migrate - am I correct in that assumption? Thanks Alex

Hey guys, I'm thinking of installing a fresh version of samba 4, into a fresh server. I've read the docs, I know I should use samba-tool with classic upgrade option and stuff. The fact is that my original server is almost dead (not really, but..), and using ldapsam as Password backend and I want to migrate it to a new server using AD, and could not find how to do it! As a matter of fact, I

Hi, Just to make sure : I can have the following domains on the same subnet without interfering with each other. Right ? Samba3 PDC : my_domain Samba4 AD DC : ad01.example.com I want to migrate from the first to the second. Thanks, Koenraad.

I would like to take users and theirs SIDs to new Samba 4 DC. Because from what I know if I create new domain with same name and IP as one before with same user names and passwords windows machines which use old domain accounts will create new ones accounts because SIDs won't match. Any ideas how can I do that? I understand that 'domain trust' will be broken when new DC with same

Hello, Currently have (and working for years) a Samba 3 PDC that also acts as a file server and a print server. Would like to migrate the DC duties only (at this time) to a Samba 4 AD on a new box without disturbing user profiles (all SIDs, etc. remain the same), domain member joins etc. Basically somewhat like an upgrade but on a new box with a new name and then demoting the old PDC to a member

Hi Team, I have old running OpenLDAP server, which has 100 users. Now I have install Samba 4.1.15 AD DC, can I migrate OpenLDAP user to Samba ? if yes how any link to start will be great. OR Can I use existing OpenLDAP with Samba 4.1.15 ? Thanks, Vikas --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com

Most of what I've found involves installing from source, which I'm not opposed to for a pilot install but for production I would rather use the distro packages or sernet. Or is this nuts/shortighted/ignorant? At any rate, I'm looking for a good guide for getting it set up as an AD controller, and then migrating my existing samba3+openLDAP+autofs setup to the new platform. Having

I copied all the database files of samba3 as is mentioned in the wiki - The classicupgrade process <https://wiki.samba.org/index.php/Samba_Classic_Upgrade_(NT4-style_domain_to_AD)#The_classicupgrade_process> But if the winbindd_idmap.tdb file is in the folder, the errors occur. See below: Importing idmap database > ERROR(assert): uncaught exception > File

Testing this "classic upgrade" scenario on a test server and have some issues. I'm using the Sernet 4.2.1 packages on Debian Wheezy. I copied the required tdb files and the smb.conf to the new test server (named WHEEZY). Edited the smb.conf to reflect the new host/netbios name of WHEEZY (remember that I want to keep the old PDC in service afterword for file and print sharing duties

Background: A server running samba 3.6.3 on ubuntu 12.04 had a raid controller failure that also corrupted the disks. I set up temporary server by simply installing ubuntu 12.04 and copying over the configuration(/etc/samba, /var/lib/samba passwd shadow groups gshadow) from backup to a reserve workstation and it has worked fine as reserve server. Setup: uses a single server master domain

You're right, man! Sorry! My mistake! I put that file because I read in somewhere about the persistent and temporary files regarding .tdb files. The winbindd_idamp.tbm was on that list, and I think that's why I left it in the folder. :D Another doubt. For the provisioning starts, I had to comment out the line referring to the ldap backend in the smb.conf of samba3. # passdb backend =

Greetings, All! I'm still on the topic, but probably I read too much stuff lately and can't have my head set straight. Situation: NT4 domain, LDAP+Samba 3.6, running under Ubuntu 12.04. The machine is also a network gateway and access (VPN/ssh) server. Target goals: 1. Upgrade to Samba4 (4.1 seems possible). 2. Convert to ADS. 3. Get rid of PAM-LDAP. 4. Retain ability for domain users

Ok. I uncomment that line and put: passdb backend = ldapsam:ldap://127.0.0.1 Error message: Provisioning > smbldap_search_domain_info: Searching > for:[(&(objectClass=sambaDomain)(sambaDomainName=EMPRESA))] > smbldap_open_connection: connection opened > failed to bind to server ldap://127.0.0.1 with > dn="cn=Manager,dc=empresa,dc=com" Error: Invalid credentials

I'm attempting to test the classic upgrade method using the instructions at https://wiki.samba.org/index.php/Samba_Classic_Upgrade_(NT4-style_domain_to_AD). Not wishing to risk any damage to our existing Samba 3 domain I created a new ldap server and imported our domain ldap into it and am using that machine as the source ldap server for the upgrade process. The *.tdb files have been

> > Is ldap running on the computer you are trying to run the classicupgrade > on? Yes. I need to modify other files too? On Thu, May 21, 2015 at 2:39 PM, Rowland Penny <rowlandpenny at googlemail.com> wrote: > On 21/05/15 18:22, Elias Pereira wrote: > >> Ok. I uncomment that line and put: >> >> passdb backend = ldapsam:ldap://127.0.0.1 >> >

Hi, I tried to build samba 4.1.12 in freshly installed CentOS 7 following the descriptions on https://wiki.samba.org/index.php/Build_Samba https://wiki.samba.org/index.php/OS_Requirements yum reports that it does not know the packages xattr, xsltproc, docbook. Configure complains that perl is missing. After adding perl, running configure, make, and make install, there are no man pages