similar to: Samba migration to a new server

Hi all (and best wishes for the new year to everyone :-) ) I have currently a Samba 3.5.6 server that acts as a PDC and print Server, with tdbsam backend, no LDAP at all. In a very next future, I will have to migrate samba to a new server (a VM actually). This migration will have to be seamless for all users (more than 200 user accounts with more than 200 PC in the domain). The

d2565778 ) it seems that a BDC can be configured only with a LDAP backend. > if not you may have to make the > new > server a PDC. I don't think I can run 2 PDCs on the same Domain , right ? > - Copy the samba private directory (with the tdb files) from the 1st > server to the 2nd server. In effect, this temporarily syncs the two > servers. Is it sufficient ? Do

d2565778 ) it seems that a BDC can be configured only with a LDAP backend. > if not you may have to make the > new > server a PDC. I don't think I can run 2 PDCs on the same Domain , right ? > - Copy the samba private directory (with the tdb files) from the 1st > server to the 2nd server. In effect, this temporarily syncs the two > servers. Is it sufficient ? Do

I'm aware of, at least generally, how one would have done a BDC/Redundant server under OpenLDAP Samba3. However, rolling your own multi-domain-controller was fairly daunting [for me] under Samba3 / OpenLDAP. I've been very interested in Samba4 for the more integrated nature of having LDAP/DNS/Samba all under one roof. [i.e. Fewer places where I can screw it up horribly.] However I'm

Hello all, I've planned to upgrade a Samba DC from 4.6.7 to 4.9.4 . For that I will use the following method : - build a new DC from 4.9.4 sources (on CentOS 7) - join this new DC to the domain - transfer the FSMO roles from the old DC (4.6.7) to the new DC (4.9.4) - replicate the sysvoldir from old DC to new DC - demote the old DC - switch off the old DC Since I prefer to

Hi Folks- I'll start by saying thanks to all the people who have made samba and shared it as open source software. Samba is truly an amazing suite of software. I have a small domain of less than 10 clients which is currently being controlled with a Samba 2.2.5 PDC running on a Compaq x86 server with a very old Suse Linux 8.1 OS. Since setting up this Compaq server, my preferred

For a few days now my primary DC has some issues. I can create users without a problem. But when I try to alter the group membership of users, one of my samba processes crashes (the one listening to the LDAP related ports: 389, 636, 3268, 3269). Also, when I start my backup DC, a few seconds later another process crashes on the primary DC (the RPC related listening to 135 and 1024). I

Hi Moray, ? Thanks for your answer. It could help but only partially. ? The script name logon%u.cmd was a bad example. Actually, a user can log on from WinXP , or Win 7 workstations, and I'like to run different logon scripts depending on the OS . So having logon script = logon%a.cmd in the smb.conf generally works thanks to variable substitution. ? But for user accounts that have been

"Can you please keep the discussion on the lists, so that others can benefit from it? Thanks, Volker" Of course sorry. Now my post again! ----------------------------------------------- EDV Daniel M?ller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 T?bingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: mueller at tropenklinik.de Internet:

We are currently looking at upgrading our PDC which is currently Samba 3.4.7 with OpenLDAP backend for authentication. As it stands we are only wanting to move it to new hardware and possibly run the latest 3.X.X branch. However one of my co-workers suggested why not look at samba 4. We understand it is still in alpha but from what we read it is ready for production use. As some background

Hi folks, I've been tasked with a migration of our servers and, as the subject implies, part of it involves a PDC and BDC that were set up before my time. However, I'm trying to accomplish a little bit more to give myself, the sysadmin, a little bit more automation capability: · Migrate the PDC and BDC both to new servers (part of this I've already done with copying

hi! I'm currently working with my new samba server [samba2.domain.com] which I will use for file sharing and I have an existing samba/ldap [smb/ldap.domain.com] as domain controller which I will use for authentication. below is my smb2.domain.com smb.conf [global] workgroup = domain.com server string = Linux File Server security = SERVER password

Hello everyone, I am operating a migration of samba from 3.0.24 (mysql passdb backend) to 3.5.6 (openldap passdb), samba working as a domain controller (PDC) and file share. The main challenge is to provide a seamless migration for users. For this new version, I am using smbldap-tools 0.9.6, nss_ldap, openldap 2.4. Everything run on FreeBSD 8.2. To get used to samba, I have managed to make

Thank you Rowland for your answer . I reply inline. > > On Wed, 6 Feb 2019 15:20:56 +0400 > henri transfert via samba <samba at lists.samba.org> wrote: > > > Hello all, > > > > I've planned to upgrade a Samba DC from 4.6.7 to 4.9.4 . > > STOP! > > Do not do this directly, reports on here have shown that this will not work. > > You

I think I understand what Active Directory is all about. I understand LDAP and I understand Kerberos. I can see how AD (well, Kerberos actually) enables single-sign-on (I assume it deals in tickets with the Windows clients as standard Kerberos clients do) and can make life easy in a large network (which, IIRC was one of the design goals of Kerberos in the first place). But lets say I have a

Hi everyone, Just trying to find a definitive answer on a problem I have been trying to address for a few months now. I've sifted through the list archives and the closest thing I could find was something about credential caching and it didn't seem to work. What we're trying to do seems simple / normal / common enough that I'm surprised it doesn't just work. We have

Hello, I recently upgraded a network to FC3 from RH9 (I know, I know, behind the times). The network is small: one PDC, one file server. The PDC (Samba, LDAP, DNS, DHCP all on FC3) is running fine. Seamless between linux logins and windows XP. Users can log in, see the shares, mount drives. The second file server is just going to be an NFS and Samba server. The plan is to use security=domain

I've done the net rpc vampire and gotten all the user and machine accounts from the NT server, I've test logged in, checked permissions, set groups, tested some of our odd apps and it all looks good. The problem I'm having is switching the desktops, and keeping the (non-roaming) profiles. I'd like to have it so everyone reboots their computer after the Samba switch over, and then

I am trying to migrate samba from a box with Mandrake 10.1 with Samba 3.0.10 to a new box running CentOS 5.2 with Samba 3.0.28. The two versions of samba are too differnet to simply copy the config and tdb files over to the new box and the Mandrake box won't upgrade past 3.0.10. I could really use some suggestions. Thanks Greg

I have the following setup: PDC: Samba 3.0.37 on Solaris 10 BDC1: Samba 3.0.37 on Solaris 10 BDC2: Samba 3.4.3 on Solaris 10 Samba 3.0.37 is the bundled version of Samba. Samba 3.4.3 is compiled from source. BDC2 is a recent addition to the network. All machine use LDAP as the backend for everything. They use winbind to handle a domain trust with another domain, but otherwise