similar to: Samba3 to Samba4 Group Migration during classicupgrade

Hey everyone, I was trying to add a second DC to my controller via 'samba-tool domain join' tool. Well, everytime, some error appears, and it says the joining was not possible. I look over the internet, and then, I tried to join the domain again, but this time, to a specific Site... the same error. When I enter the AD tools on windows, for my surprise, I get this:

Hey, I'm testing a migration from samba 3 to samba4. On samba 3 smb.conf, I have and workgroup=EXAMPLE.COM and now, on samba4, after the migration I have workgroup=EXAMPLE and realm=EXAMPLE.COM. My problem is that on workstations already joined to domain, on samba3, are incapable of authenticating/login against the same domain in samba 4 without rejoining the domain. The infrastructure in

Hey, I extend my AD with some new attributes, but I make some mistakes on the way and now I'm trying to modify those wrong attributes entries, like isSingleValued and oMSyntax. I'm following these guide - https://blogs.oracle.com/hariblog/entry/modify_attribute_properties_in_active - to make the changes. I go to LDP.exe, connect and bind to LDAP and try to make the changes on

Hi, Im running a domain controller (AD DC) and file server, on the same machine, with sernet-samba 4.1.14. Right now, I have a process using almost 100% CPU all the time. After 'samba-tool processes' I found that the process is winbind_server. On samba wiki page, they don't recommend using domain controller as file server because winbind issues. I already have other domain

Hi, Yes, I already thought about it. I have the sernet repo installed.. Is possible to yum update and jump from 4.1.6 to 4.1.14 directly, without problems or should I follow some kind of procedure to avoid future problems? Regards, Bruno Andrade. On 12/29/2014 01:46 PM, Rowland Penny wrote: > On 29/12/14 12:02, Bruno Andrade wrote: >> Hi again, >> >> Sorry, I forgot to

Hi again, Sorry, I forgot to include the fd used... 13 -> /var/lib/samba/private/sam.ldb.d/DC=EXAMPLE,DC=COM.ldb 16 -> /var/lib/samba/private/sam.ldb.d/metadata.tdb the others refers to /var/run/samba/winbindd/pipe Regards, Bruno Andrade. On 12/29/2014 11:56 AM, Bruno Andrade wrote: > Hi, > > Here is some output of "strace -ff -p" to the process using ~100% CPU >

Hi, Everybody After issuing the command samba-tool domain classicupgrade --dbdir=/produtos/backup/var/lib/samba/ --use-xattrs=yes /produtos/backup/etc/samba/smb.conf i'm getting an error message regarding access to the ldap database failed to bind to server ldap://localhost with dn="cn=administrator,dc=espmg,dc=lan" Error: Invalid credentials (unknown) Connection to LDAP

Hello Samba list! Well, my situation is quite the same than this one from a previous post: https://lists.samba.org/archive/samba/2017-May/208201.html I have to make a classicupgrade from a Samba 3 NT server to Samba 4 AD, and meanwhile the office name changed, so I would try to profit of this upgrade to change domain name. So far from the different tests i've made, i could run the

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

On 12/05/17 09:10, Marc Muehlfeld wrote: > Hi Sebastian, > > Am 11.05.2017 um 19:39 schrieb Sebastian Arcus via samba: >> 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? > >

On 6/4/2015 9:57 AM, Mario Pio Russo wrote: > guys sorry to take this thread onboard once more, but I still can't get > this sorted. > > I have compiled the latest tarball from samba, 4.2.2 . compilation works > fine and after that I am able to upgrade from samba 3 with the following > command: > > samba-tool domain classicupgrade --dbdir=/var/lib/samba-ccdc1/dbdir/

Hi, I'm going classicupgrade our samba3 to samba4 next weekend, and suddenly realised something: I intent to keep my samba3 PDC machine called 'filehost' as a member server, to only serve files. However, after classicupgrade my new (freshly installed) DC1 will of course have the netbios name from my 'old' samba3 machine. ('filehost') Meaning I end up with two

I have an old Centos5/Samba3.5 domain with LDAP backend that I am attempting to migrate to the latest Samba 4.2 on Centos 7.1. Samba in both cases has been installed using Sernet packages. I had successfully run the classicupgrade process, but in subsequent testing found that in the 3.5 domain all the computer accounts have the posixAccount class and therefore have a uidNumber.

Hello: First, sorry for my English. I'm testing samba4 rc5. I have compiled and installed samba4 and now I'm trying to simulate an upgrade from my samba3 site to my samba4 test installation. I have setup a isolated network and I have replicated server and clients, copied my samba3 ldap contents and tdb files. But, when I run samba-tool classicupgrade following to the docs,

Dear samba list after a classic upgrade i lose the printer drivers uploaded in NT Domain mode the drivers files are still present in print$ share but enumdrivers rpcclient command list no drivers... did i forgot a file in the dbdir during classicupgrade call or this data are not handled during classicupgrade ? Thanx

Thanks for the quick reply Rowland! I see what I did wrong: I edited the smb.PDC.conf on the AD DC server with a new domain name hoping both the AD DC and the existing NT4 PDC would be up and running so I could move clients over one at a time to minimize down time. So that's a no go. Instead of classicupgrade, if I provision the new AD DC with a new domain name, would there be a way to

Hello, I'm talking about re-writing the classicupgrade HowTo since over a year now. :-) Now, after three rainy vacation days, it's finaly done: A complete and comprehensive re-write of the classicupgrade HowTo: https://wiki.samba.org/index.php/Samba_Classic_Upgrade_%28NT4-style_domain_to_AD%29 Some other mentionable documentation changes, I had done during the last week: *

On 05/01/2015 12:03 PM, Rowland Penny wrote: > On 01/05/15 15:29, Steve Ankeny wrote: >> On Samba AD DC most of these enpoint server are already running -- >> >> dcerpc endpoint servers = epmapper, wkssvc, rpcecho, samr, netlogon, >> lsarpc, spoolss, drsuapi, dssetup, unixinfo, browser, eventlog6, >> backupkey, dnsserver, mapiproxy >> >> Use

Hi, I'm having trouble with the classic upgrade. We have three samba servers: Server1: CentOS 5/Samba 3.6 (with smbldap-tools) Server2: CentOS 6/Samba Version 4.2.14-SerNet-RedHat-23.el6 Server3: CentOS 7/Samba Version 4.2.14-SerNet-RedHat-23.el7 Server 1: CentOS 5/Samba 3.6 (with smbldap-tools) Serves our OpenLDAP backend for centralised authentication (LDAP replicated to two other servers

Hi, we might have encountered a possible python 3 bug in samba 4.11. We are using the sernet-samba packages. While the classicupgrade works on centos6 (using python 2) it fails on centos8 (using python3) with a classic python3 bug message: # samba-tool domain classicupgrade --dbdir=pdc-files/ --realm=ad.xxx.de --dns-backend=SAMBA_INTERNAL pdc-files/smb.conf INFO 2019-09-25 06:15:34,366 pid:12017