similar to: Migrating to new domain

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

I had previously tried to migrate our PDC to a new machine by simply copying the config over and such. That failed miserably but luckily the various home servers (BDC's in samba speak I think) took up the slack. So after much debate, this weekend we moved the PDC back to the original machine. We never moved LDAP off of the original machine, as only samba functions moved. I now know I did

We are currently setting up a new domain with samba 3.5.10 and openldap 2.4.23 (based off of Centos 6.3). The current domain is running older versions, 3.4.7 and 2.4.15 respectively. We are changing domain names also. There is alot of layout changes and the way it works. One change we are implementing is combining all the BDC's/home servers into one and moving them to the PDC. On the old

Hello all, We have just concluded a very drawn out test of our domain that is having some trust relationship problems with Windows 7 desktops. Here is a breakdown of our setup: roark PDC running samba 3.4.7 (also has OpenLDAP) on VLAN 2 archives3 BDC running samba 3.4.7 (also has OpenLDAP) on VLAN2 arrowhead BDC "home server" running samba 3.4.3 on VLAN 9 archives4 BDC

We are migrating all of our users from the current domain to a new one we created. In this process we are moving them from roaming profiles to local. What would be the best practice to accomplish this? I can find plenty of writeups on how to do the opposite. Also we will be doing some extra folder redirection. Currently we only redirect their my documents to the server. On the new system we plan

I am looking to move our current Samba primary domain controller to a new machine. The current machine is EOL, running Fedora 11 (old), and had way too many services on it to start with (mail, dns, samba, mysql replication, primary ldap, etc). I am looking to move to a Xen domu with either Fedora 13 or Centos 5.5. What my question is is this: what should I look for when I migrate the samba

We are currently using samba and openLDAP to enable our users to have roaming profiles on our domain network. We have one primary domain controller and 7 "home servers" at the various locations that serve the profiles and such. The problem is that randomly various users are unable to load their profile and windows just gives them a temporary profile. This mostly happens on vista

I am about to be migrating mail servers and have a few questions. First a little background: Old mail server: Fedora 11 dovecot-1.2.11-3.fc11.x86_64 installed from yum repo mbox mail format OpenLDAP authentication 250+ users New mail server: Fedora 13 dovecot-2.0.1-1_118.fc13.x86_64 installed from atrpm rpm file Maildir mail format OpenLDAP authentication 250+ users I plan to use dsync on the

Hello, Currently our mail server is setup to use postfix and dovecot, which is fine except it is setup to use mbox format mail. That and procmail as we need to move to sieve but that is a different issue. I have searched until blue in the face and cannot find a 100% working solution that doesn't require alot of manual interaction to move the mail boxes from mbox to maildir. I have

Hi all, We currently have a Fedora 11 machine (about to be upgraded to Fedora 15 though) running Samba 3.4.7 as our PDC and multiple BDC "home servers" running various versions of samba and OS. What I am needing is a fail proof way to migrate the PDC function off the current machine and onto another new fresh install. Currently our PDC is also the home server for one of our

We recently migrated our install from an ancient fedora 11 install of samba and openldap to a centos 6.3 setup with its openldap and samba. The domain has been totally recreated from scratch as the person that did the previous setup has not been employed here in many years. After fighting with shares for a while we mostly got them fixed and working. However the biggest issue now is when our GIS

Hi all, I have a BDC which uses the LDAP backend of my PDC. Unfortunately all the users who log-in in the morning and who are processed by this BDC, do not get their logon script executed. The BDC logs this error message: [2013/05/24 07:28:11.946577, 2] auth/auth.c:304(check_ntlm_password) check_ntlm_password: authentication for user [foobar] -> [foobar] -> [foobar] succeeded

I'm in the process of building a Samba PDC for my office, and I have a couple of questions. We have three regional offices connected via VPN. We'd like to have network browsing across all three network, with a single login. I was going to do a Samba machine with an LDAP backend on the same machine. So would it be advisable to have the PDC at the main office and BDC at each of the regional

Hi, I was wondering if a Samba BDC should be able to create users and computer accounts when connecting to a LDAP PDC server? Should the add scripT lines be included in a BDC's smb.conf file? Normally, as far I know, BDC should just log on users. Or am I wrong? Thanks,

Hi, I want to set up SaMBa PDC and BDC with LDAP. I read the TOSHARG2, but don't understand something: >Samba-3 cannot participate in true SAM replication and is therefore not able to employ >precisely the same protocols used by MS Windows NT4. A Samba-3 BDC will not create >SAM update delta files. Ok, I understand until that, but: >It will not interoperate with a PDC (NT4 or

Hello! I want to create BDC with smbpasswd backend, just because I run ldap master on the same machine as PDC and I don't think that using ldap backend will be far better for me. Only thing I don't understand: I read in howto: <quote> Machine Accounts Keep Expiring This problem will occur when the passdb (SAM) files are copied from a central server but the local Backup

Hi, I installed a SaMBa PDC and a BDC. When I log in to an XP client with a new user, sometimes I get the initial profile settings from the netlogon share, but often from local. When I get the local default settings, it is not syncronized to the server at logout. Even if I get the new profile from the server, on the same client, next time, with a new user, I get the new profile from local. I

I have a RH 7.2 PDC which uses DHCP for 2 machines on the network. My Win9x machine as a client/BDC just in case and uses a static IP. If the PDC goes down. I have to put in or take out the PDC's gateway IP and was wondering if there was a way to get ONLY the info I need from DHCP to the Win machine. To attempt to clarify, when the PDC is up, it will assign its gateway IP to the BDC (since it

Choose Ldap authentification, Ldap-Properties fill in your Ldap-Server = and Search-Base. Copy the files from the old server to the new with rsync. Stop samba/ldap on the old server Start ldap start samba on the new. And you are running. In my case I moved my samba from an old sidux to viruell centos5.5 on windows 2008 Server. =20 ----------------------------------------------- EDV Daniel

Hai, ? Just a quick question, maybe simple, but im not all there with my head.. ( hard night )... And last night my Samba 3 PDC decided to start dying..? the disk are dying..? :-(( so im a bit in a hurry.. I have 2 BDC's also in the old NT4 domain?running atm, was it a simple, down the PDC and set the bdc smb.conf to master? Its a ldap based network, and the ldap is on all my servers