similar to: Upgrade to Alfa13

On Sun, 08 Apr 2018 13:34:52 +0200 Kris via samba <samba at lists.samba.org> wrote: > W dniu 2018-04-08 12:49, Rowland Penny via samba napisał(a): > > On Sun, 08 Apr 2018 12:31:26 +0200 > > Kris via samba <samba at lists.samba.org> wrote: > > > >> I should try this command sooner. Now I have made full backup and > >> something is missing: >

Hi everyone samba --version Version 4.0.0alpha19-GIT-c9ef087 Tricky installation. Existing alpha 18 git Had to run make twice. OK with that now. But none of the commands would work. samba, samba-tool. . . All gave errors e.g. samba-tool Traceback (most recent call last): File "/home/steve/bin/samba-tool", line 26, in <module> from samba.netcmd.main import cmd_sambatool

Hi! I have recently upgraded samba4 to the latest GIT build. I have run upgradeprovision according to upgrading-samba4.txt instructions. All seems to be well, but when i try to access Group Policy Objects from gpmc utility on windows i get the following error message: --------------------------- Group Policy Management --------------------------- The permissions for this GPO in the SYSVOL folder

Hi All, Does anyone know if there's a Samba 4 to Samba 4 migration process? Sounds weird, but it has a logical reason: I've a several-year-old S4 implementation, from an early Alpha (10 I think?) that hasn't been in the best of shape of late - when S4 4.0.0 arrived, I accidentally upgraded using my normal "git pull; ./configure; make; make install" procedure and instead of

On Sun, 08 Apr 2018 12:31:26 +0200 Kris via samba <samba at lists.samba.org> wrote: > I should try this command sooner. Now I have made full backup and > something is missing: > > [root at dc ~]# cd /opt/samba-4.7.6/bin > [root at dc bin]# ./samba_upgradeprovision --realm=DOMAIN.NET.PL -U > Administrator > Traceback (most recent call last): > File

W dniu 2018-04-08 14:06, Rowland Penny via samba napisał(a): > On Sun, 08 Apr 2018 13:34:52 +0200 > Kris via samba <samba at lists.samba.org> wrote: > >> W dniu 2018-04-08 12:49, Rowland Penny via samba napisał(a): >> > On Sun, 08 Apr 2018 12:31:26 +0200 >> > Kris via samba <samba at lists.samba.org> wrote: >> > >> >> I should try

OK, there has got to be a way to work with this thing other than wiping the Domain every time an error pops up. Trying to resolve problems I did a git upgrade and: setup# /usr/local/samba/sbin/upgradeprovision Which provided the unhelpful: Found 3 domain controllers, for the moment upgradeprovision is not able to handle upgrade on domain with more than one DC, please demote the other(s)

I have the latest samba4 4.2 git running on centos6.4 but when I originally provisioned it I didn't include the --use-rfc2307 for AD posix attributes. I'd like to map certain AD users to unix users so should I do a samba-tool upgradeprovision --use-rfc2307 to add this option?

Originally I had a Win 2003 DC. I added a samba 4.0.0 DC to the domain, allow full replication to take place and then transferred all the roles to the samba 4.0.0 dc. Finally I removed the Windows DC from the domain. Everything has been working well. Today I upgraded from samba 4.0.0 to 4.0.3 and ran samba_upgradeprovision --full. Initially this was failing in update_present throwing an exception

Hello All I noticed same minor imperfection on Samba4 How To page. Installation on CentOS6. I did as below : For RedHat 6.x: $ yum install gtkhtml setroubleshoot-server setroubleshoot-plugins policycoreutils-python libsemange-python setools-libs-python setools-libs popt-devel libpcap-devel sqlite-devel libidn-devel libxml2-devel libacl-devel libsepol-devel libattr-devel

1) samba-tool dns add dcmsc.test.inc test.inc test.inc MX 'mail.test.inc 10' 2) samba-tool dns query dcmsc.test.inc test.inc test.inc MX 3) [root at dcmsc caiman]# samba-tool dns query dcmsc.test.inc test.inc test.inc MX Password for [administrator at test.INC]: Name=, Records=1, Children=0 MX: mail.test.inc. (5) (flags=600000f0, serial=10, ttl=0) Name=_msdcs, Records=0,

Samba 4.7.10 is unwilling to find my pyldb-util v 1.2.3 Checking for system pyldb-util (>=1.2.3 <=1.2.999) : not found ERROR: System library pyldb-util of version 1.2.3 not found, and bundling disabled Building of Samba 4.7.9 in the same environment works flawlessly. What goes wrong in Samba 4.7.10 with detection of pylab? Regards, Thomas

An embedded and charset-unspecified text was scrubbed... Name: memory_profiler.txt URL: <http://lists.samba.org/pipermail/samba/attachments/20170330/f5d10ac9/memory_profiler.txt>

Version 4.0.0alpha18-GIT-e75c436 Ubuntu 11.10 Built now with make clean ./configure.developer make make install samba -i -d3 gives this: ldb: unable to stat module ${PREFIX}/modules/ldb : No such file or directory ldb_wrap open of privilege.ldb samba: using 'standard' process model Unknown process model 'standard' my $PREFIX should be /usr/local/samba I think. The path is

26.05.2024 13:13, Andrew Bartlett wrote: > On Sat, 2024-05-25 at 14:25 +0300, Michael Tokarev via samba wrote: >> Hi! >> >> I'm trying to find where various components of samba belongs to and where they're used. >> There are quite a few files with unknown purpose. For example, a cpython library >> (python code which is to be linked to from a C program)

Hai Andrej, Oeps, Sorry, my mistake 4.6.x needs at least 1.1.29. But you can upgrade to 4.6.x ;-) Check again and if that problem then still exists, then i think you can better ask this one in the samba-technical list. Or if Rowland knows something more about this. One tip, wait untill tomorrow or the weekend, there wil be a new release due to the regression bug. There planning is to be

> Yes, that is what has happened. It will be in the samba 4.9 git tree, > but because no version increment was done builds on systems that have > ldb from the system will fail. My version of ldb is "libldb-1.3.4-1.el7.x86_64", which I suppose is the stock CentOS 7.6 version. The first time I buiIt with "--without-ad-dc". I just built it again as AD-DC and the

The two systems I'm referring to are on different domains, different locations. No connection whatsoever except me being the one administering both. According to oEMInformation the server was provisioned by 4.3.3. I just checked the Samba log file and it seems that version 4.7.4 was running before the update. I'm now looking at the logs right before the upgrade and indeed, there have

Hello, I'm trying to take a box from 4.4 to 5.0 and doing it via binary yum upgrade. I'm following the procedure at: http://lists.centos.org/pipermail/centos-announce/2007-April/013660.html for taking a 4.x box to 5. I've removed any unneeded rpms, and confirmed the state of the system. I downloaded and installed centos-notes-5 and ran an rpm -Uvh centos-release-5 which

Hello, we have a single DC after a clssicupgrade and we need to extend the schema. So we created a attrib.ldif with all our attributes and a object.ldif to add the attributes to the "CN=User" Object. We tested the two ldif-files on a DC with only a few users and groups and it works fine. Then we did the classicupgrade (same NC as the test-system) we have more then 30.000 users