similar to: Migration to samba4 ad and sync to openldap.

I'm open to alternatives but need to be up and running 24/7 on the linux side. My boss hates windows more than I do and will likely be looking for a new job if I use windows to administer the the linux side. We only use windows if there is no other way do do something. On 3/19/19 12:08 PM, Rowland Penny via samba wrote: > On Tue, 19 Mar 2019 11:03:12 -0500 > John McMonagle via samba

On 3/19/19 2:52 PM, Rowland Penny via samba wrote: > On Tue, 19 Mar 2019 14:04:27 -0500 > John McMonagle <johnm at advocap.org> wrote: > >> I'm open to alternatives but need to be up and running 24/7 on the >> linux side. >> My boss hates windows more than I do and will likely be looking for a >> new job if I use windows to administer the the linux side.

Christian Thanks for the information. Also thanks to mj. That's sounds promising How did you migrate your data? Did you need to add any schema to samba4 ad? Were in 5 cities and some of the Internet is not 100% reliable. Will need samba4 in each office to make sure they can log in even if the Internet is down. How reliable is the the ad syncing? Does it need a lot of bandwidth? One of the

On Tue, 19 Mar 2019 11:03:12 -0500 John McMonagle via samba <samba at lists.samba.org> wrote: > We are currently running samba3 nt4 domain controllers using > smb-ldap-tools. We want to convert to samba4 ad so we can run new > versions of windows server. Why do you need a newer Windows version ? You state you have no Windows workstations. But you are correct, you need to upgrade,

On Tue, 19 Mar 2019 14:04:27 -0500 John McMonagle <johnm at advocap.org> wrote: > I'm open to alternatives but need to be up and running 24/7 on the > linux side. > My boss hates windows more than I do and will likely be looking for a > new job if I use windows to administer the the linux side. > We only use windows if there is no other way do do something. > > On

We also moved from Samba3/ldap to AD. On the servers we also only use Linux. We had no problem with the move. our mailserver is also cyrus with postfix and also SOGo. Everything works no problems at all. The migration needs to be planned carefully but it is worth the effort. You can still use lam with AD we also use it. Regards Christian Am 19. März 2019 21:41:43 MEZ schrieb John McMonagle via

I managed to do migration using "classicupgrade". Doing tests with debian buster 2:4.9.4+dfsg-4. For the moment using samba internal dns and sub-domain of ad.advocap.org. Had issue forwarding dns if I used main domain. When it comes to real production will use bind that I understand better but don't want to mess with my other dns servers now. Had a w10 box join samba4 ad

On 4/4/19 3:18 PM, Rowland Penny via samba wrote: > On Thu, 4 Apr 2019 14:09:18 -0500 > John McMonagle via samba <samba at lists.samba.org> wrote: > >> I managed to do migration using "classicupgrade". >> Doing tests with debian buster 2:4.9.4+dfsg-4. >> For the moment using samba internal dns and sub-domain of >> ad.advocap.org. Had issue

Wed, 15 Jul 2020 21:49:12 +0100 Rowland penny via samba <samba at lists.samba.org>: > On 15/07/2020 21:30, RhineDevil wrote: > > Wed, 15 Jul 2020 21:08:44 +0100 Rowland penny via samba <samba at lists.samba.org>: > > > > Just a brief explaination, I need to know what fields are different and how to reproduce them if I choose to... let's SUPPOSE > >

Thanks Rowland, I didn't think i was doing all of this in an outdated way (it really makes sense, as much of the tutorials i've followed come from before 2010 and there's barely no recent tutorials regarding these issues). So i'm gonna follow your suggestion. However, how can i deal with the LDAP server? This base is big and it's a mandatory feature i need to implement on

I can see in the docs that a domain rename is not recommended/supported by Samba for an already provisioned domain. However, what I can't work out is if this is not possible during the classicupgrade step either? Does this make any difference, or would it present the same difficulties as renaming an already provisioned Samba AD? It case what I'm asking is not quite clear - I have a

Hello, I have an old 3.6 server to be replaced with a new 4.9 one. They are standalone, using tdbsam backend. I copied system users and group, then /var/lib/samba/*.tdb from the old to the new one. However, obviously the newer samba absolutely doesn't care about my old user database. "pdbedit -L" returns nothing on the new server. Is there some upgrade step I'm missing here?

Hello i have a problem after classicupgrade on ubuntu 14.04/samba 4.3.11 i know this version is not supported, sorry no way for the moment to do ubuntu upgrade... before migration netbios name in smb.conf (irisserv) did not match dns hostname (noordo) so AD was provisionned but with irisserv and there are no servicePrincipalName in irisserv ldap entry... is there a way to fix this? Thank

Am 31.03.19 um 14:08 schrieb Rowland Penny via samba: > On Sun, 31 Mar 2019 13:37:44 +0200 > Patrick von der Hagen via samba <samba at lists.samba.org> wrote: > >> I am running samba as a fileserver, having some users (LDAP backend) >> and lots of files. No machines ever joined this setup. Now I want to >> join some clients, but want to upgrade to AD before I do

Hi Rowland, Fair comment. This is not a new domain and we are migrating to AD. The box in question runs Samba 3.6 (PDC and a physical box) and as such we are not able to directly migrate it. We are adding a Samba 4 box (a VM) , to which will become the new PDC . This box will then be used to migrate to AD. The Samba 3 box will converted as a file server. The confusion in smb.conf is possibly

Thu, 16 Jul 2020 08:15:06 +0100 Rowland penny via samba <samba at lists.samba.org>: > On 15/07/2020 22:17, RhineDevil wrote: > > Wed, 15 Jul 2020 21:49:12 +0100 Rowland penny via samba <samba at lists.samba.org>: > >> On 15/07/2020 21:30, RhineDevil wrote: > >>> Wed, 15 Jul 2020 21:08:44 +0100 Rowland penny via samba <samba at lists.samba.org>: >

Hi, I just want to migrate my Samba PDC (with LDAP backend) to a Active Directory. On the migration page (https://wiki.samba.org/index.php/Migrating_a_Samba_NT4_Domain_to_Samba_AD_(Classic_Upgrade[https://deref-web-02.de/mail/client/IywWde3X0uo/dereferrer/?redirectUrl=https%3A%2F%2Fwiki.samba.org%2Findex.php%2FMigrating_a_Samba_NT4_Domain_to_Samba_AD_%28Classic_Upgrade])) is a section

Hello I used https://wiki.samba.org/index.php/Migrating_a_Samba_NT4_Domain_to_Samba_AD_(Classic_Upgrade) to migrated my old samba 3, i created a dc and a member file server, but on member i can't see id for usernames and groups. This is my smb.conf on dc [global]         netbios name = DC1         realm = LXCERRUTI.COM         server role = active directory domain controller        

Hello, Actually migrating users/groups from samba3 to samba4 (in a separate domaine), i succeeded in importing users/gruops and their attributes. But For a reason i don't know some (a few) groups are not being created, and i get this error: "Failed to create group "MYGROUP" - samldb: Account name (sAMAccountName) 'MYGROUP' already in use! " Searching in ADUC

thank you for the quick reply! Le 17/07/2018 à 12:09, Rowland Penny via samba a écrit : > On Tue, 17 Jul 2018 11:30:43 +0200 > Arnaud FLORENT via samba <samba at lists.samba.org> wrote: > >> Hello >> >> i have a problem after classicupgrade on ubuntu 14.04/samba 4.3.11 >> >> i know this version is not supported, sorry no way for the moment to >>