similar to: samba migration from PDC tdbsam to BDC tdbsam

Hello According to NT4 Migration Using tdbsam Backend http://samba.org/samba/docs/man/Samba-Guide/ntmigration.html#id2604610 I would like to transfer PDC settings (users,groups sids) to BDC and later make from BDC PDC machine. I have Fedora Core 7 PDC(hostname serwer) and Centos 5.4 BDC (hostname serwer2) both on tdbsam backends. I have copied smb.conf, passwd,group,shadow,secrets.tdb files

Hi, i have a small problem. I have a production machine which is used as PDC, FileServer, Groupware-Server, Backup-Server. As our data needs are growing more and more we decided to split these machines up, to stay with a more stable system. At the moment i have tdbsam password backend, a running LDAP server (groupware), a running pdc. I want to have 1x machine hosting: pdc, ldap

Hello I need a description how to move painlessly samba from one system to another without re-adding to the domain windows clients. Currently, I have samba Version 3.0.28a-1.fc7 on Fedora 7 and I want to move it on CentOS 5.5 As far as the server hardware remains the same. In addition to changing the system i would like to change new disks and add a new 3ware 9650SE Raid controller (samba

I'm helping out a small office upgrade their NT 4 PDC to Samba. It's a small office of 6 people, so tdbsam is being used. They keep having tape backup issues and other problems, so one of the reasons for the Samba migration is to allow me to SSH into their box and remotely administer it from home on evenings/weekends. Currently I'm testing the move using two dummy machines, and

If I go with the suggestion to just set up a new AD-DC server, how do I move my data to this from the old server (which uses TDBSAM)? Simon On 8/10/20 2:34 AM, L.P.H. van Belle via samba wrote: > > >> -----Oorspronkelijk bericht----- >> Van: samba [mailto:samba-bounces at lists.samba.org] Namens >> Simon Matthews via samba >> Verzonden: maandag 10 augustus 2020 2:27

Hello everyone, the time for me to use a OpenLDAP server is getting closer ( :( yikes..I'm still scared sorta) , I currently have a Samba PDC with tdbsam with 50 users goes fine, our company will grow (doing our best) in this year by a minimum of 25-30 computers, and I've stuided the TOSHARG , and it says that for every 50 computer a bdc is suggested. The questions : 1.how does

I currently have a pure samba domain running off a Suse 9.1 machine. When I installed this domain I wasn't really comfortable with linux or LDAP so I used a tdbsam password file, and as there are only 30 or so users it seemed the way to go in the small amount of time I had available. Well, now I want to add a BDC to the mix I find I need to move to an LDAP backend. I only have two boxes at

Hi, We have an old domain with a samba-3 PDC and LDAP backend in our HQ and two BDC in our branch offices. Since we don't use the domain in our HQ anymore and one of the branches will be moved to our new domain (2003/2008) I'm thinking about decomissioning the PDC and promote both BDCs as PDC for their branch offices and networks. I would also get rid of LDAP. Changing the backend to

Hello, I want to migrate from an old NT4 PDC to a Samba version 3.0.26a. My BDC configuration for migration is [global] workgroup = DOMAIN server string = %h server Samba %v interfaces = eth0, 192.168.1.0/24, lo bind interfaces only = Yes security = DOMAIN map to guest = Bad User passdb backend = tdbsam passwd program =

I have got tdbsam as backend in smb.conf passdb backend = tdbsam When user change password from windows XP file passdb.tdb schould change date because was updated, but I have still the same date IX 18 10:30. [root@serwer private]# ls -al razem 76 drwx------ 2 root root 4096 IX 11 20:25 . drwxr-xr-x 7 root root 4096 XI 2 15:14 .. -rw------- 1 root root 36864 IX 25 07:57 passdb.tdb -rw-------

Hello, thanks for looking over my ramblings... We have an NT4 PDC with and NT4 BDC on 192.168.132.X, these boxes are very very old and overloaded. I am trying to replace them with a nice shinny new Samba box. My problem is that while I am trying to test it out to make sure it plays nice it keeps winning the elections. I find this weird as I have set the box to domain master = no and turned the

Hi. Can anyone give me some help on migrating my Samba PDC from old hardware to a new box? Old hardware is running RedHat 9, with Samba 3.0.2a-1. New hardware is running Fedora Core 4 with Samba 3.0.14a-2. Old (fully working) PDC is using tdbsam backend for passwords. For simplicity, I'd like to do the same on the new one, although I could also move to LDAP it that's what's

On Wed, 28 Sep 2016 16:11:23 +0000 Charish Patel via samba <samba at lists.samba.org> wrote: > 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

On Wed, 28 Sep 2016 11:33:29 -0500 Bob of Donelson Trophy <bob at donelsontrophy.net> wrote: > On 2016-09-28 11:22, Rowland Penny via samba wrote: > > > On Wed, 28 Sep 2016 16:11:23 +0000 > > Charish Patel via samba <samba at lists.samba.org> wrote: > > > >> Hi folks, > >> > >> I've been tasked with a migration of our servers

Hello guys, i just wanted to ask about an idea, if it is feasible (or not). The company i work for (350 users) has 2 branches, that are interconnected with HQ via L2TP (encapsulated in IPsec) tunnels, that are setup in between Mikrotik routers. current setup: 300 users | HQ 192.168.2.0/23 | | Samba PDC + LDAP | | (389 DS) backend | | | | | / \ 30 users /

If you mean regular Microsoft AD, the reason is simple: cost. Management sadly does not want to shell out the money for it. If you mean upgrading the Samba PDC to AD, that is what I want to do but on the new servers as opposed to the current set up. Charish -----Original Message----- From: Rowland Penny [mailto:rpenny at samba.org] Sent: Wednesday, September 28, 2016 12:23 PM To: samba at

As some of you may know, I'm trying to set up Samba BDC on a disk- and fan-less tiny mipsel_CPU router running OpenWRT distribution. I already managed to compile Samba 3.0.21a and OpenLDAP 2.3.18 for it, and they seem to work fine. The problem is, this tiny distribution for routers doesn't seem to have anything like Name Service Switch (NSS), and relies solely on /etc/passwd and

Help... I'm running Samba v3.0.25b, recently upgraded. I use tdbsam, winbindd etc. The Samba machine is a PDC. If the machine is FRED and the domain is HOME, should I set up a machine account for FRED and join that to the HOME domain ? Should the machine FRED have its own domain SID ? Or... is are the machine FRED and the domain HOME one and the same ? Thanks, Chris -- Chris Hall

For the last few years, we have had a NT4 PDC (without a BDC). This week I undertook the process of builing a Samba BDC running Debian linux. This new BDC is running samba version 3.0.7. After setting up the box, I copied all of the user, group, and machine accounts over to the new bdc, using "net rpc vampire". The BDC is up and running and I see everybody authenticating against it.

I was wondering how people sync the roaming profiles in an environment with a PDC and multiple BDCs. Are profiles better stored in another server (a member server) instead of the xDC? I could use rsync from the PDC to the BDC, but that doesn't work the other way around, i.e., when a user logs in via a BDC whatever changes they make won't go back to the PDC. Unless the profile is: - always