similar to: error adding users to Domain Admins group during classicupgrade

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

On 14/05/2019 08:44, Ruisheng Peng via samba wrote: > Hi, > > I'm trying to migrate a NT4 domain under Samba3 to an AD DC under Samba4 > on a separate server. During the classicupgrade, there were a number > warnings while importing groups: > > WARNING 2019-05-13 15:09:56,728 pid:25284 > /usr/local/samba/lib64/python2.7/site-packages/samba/upgrade.py #299: Could

On Fri, 9 Dec 2016 11:11:56 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > From: "Stefan G. Weichinger via samba" <samba at lists.samba.org> > To: samba at lists.samba.org > Subject: Re: [Samba] Samba on Debian 8; NT4 domain, win10 > Date: Fri, 9 Dec 2016 11:11:56 +0100 > Reply-To: "Stefan G. Weichinger"

I have a new server running CentOS 6.4 x64, which will serve as our new Samba4 server. It is set up in a test environment, and I've copied over the tdb files and the smb.conf file from our samba3 server (Same OS and version). I'm trying to do an in-place upgrade on the copied files, but keep hitting an assert / uncaught exception during the upgrade: # /usr/local/samba/bin/samba-tool

On Fri, Mar 18, 2016 at 4:04 PM, Andrew Bartlett <abartlet at samba.org> wrote: > The upgrade code assumes you run on the same host. I realise now that > folks doing an upgrade use that an an opportunity to upgrade hardware, > and keep old systems as fallbacks, so the assumptions cause trouble. > > Make the new host identical in terms of the data needed to upgrade >

Am 2016-12-09 um 12:21 schrieb Rowland Penny via samba: > On Fri, 9 Dec 2016 11:11:56 +0100 > "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > >> From: "Stefan G. Weichinger via samba" <samba at lists.samba.org> >> To: samba at lists.samba.org >> Subject: Re: [Samba] Samba on Debian 8; NT4 domain, win10 >> Date:

On Mon, 12 Dec 2016 09:04:18 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > Am 2016-12-09 um 12:21 schrieb Rowland Penny via samba: > > On Fri, 9 Dec 2016 11:11:56 +0100 > > "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > > > >> From: "Stefan G. Weichinger via samba" <samba

On 19/03/16 17:16, Sonic wrote: > On Fri, Mar 18, 2016 at 4:04 PM, Andrew Bartlett <abartlet at samba.org> wrote: >> The upgrade code assumes you run on the same host. I realise now that >> folks doing an upgrade use that an an opportunity to upgrade hardware, >> and keep old systems as fallbacks, so the assumptions cause trouble. >> >> Make the new host

Am 2016-12-09 um 11:11 schrieb Stefan G. Weichinger via samba: > Could not add group name=Domain Admins ((68, "samldb: Account name > (sAMAccountName) 'Domain Admins' already in use!")) I think this is my problem (on the old host/pdc): # net groupmap list Domain Admins (S-1-5-21-2777655458-4002997014-749295002-1006) -> root Domain Guests

Hello, I run Samba 3.6.3. on ubuntu server, whre the domain works fine. Hoever when I try to migrate to Samba 4.1 from sernet distribution, I finish with Classicupgrade on the below error. I know it hase to do with bad group mapping, but I am not able to find the mistake. Please help. root at server:/var/lib/samba# samba-tool domain classicupgrade --dbdir=/var/lib/samba.PDC/dbdir/

Hi at all, i´am using samba 4.3.4 as "ad", "migrated by classicupgrade" some time ago from an nt4-domain. By trying samba_upgradedns --dns-backend=BIND9_DLZ i get the following error: Traceback (most recent call last): File "/usr/sbin/samba_upgradedns", line 262, in <module> paths, lp.configfile, lp) File

Am Dienstag, 2. Februar 2016, 09:51:03 CET schrieb Rowland penny: > On 01/02/16 22:24, Markus Dellermann wrote: > > Hi at all, > > > > i´am using samba 4.3.4 as "ad", "migrated by classicupgrade" some time ago > > from an nt4-domain. > > > > By trying > > samba_upgradedns --dns-backend=BIND9_DLZ > > > > i get the

On Fri, Mar 18, 2016 at 2:39 PM, Andrew Bartlett <abartlet at samba.org> wrote: > Exactly. Think about it a little - how can it determine the group > membership, if the users/groups do not exist locally on the host doing > the migration? To clarify then: Do I need both the users and groups on the new host as they are on the old host, or just the groups? Is there any constraint

> I am fairly sure this is your problem, it should be able to find the > KDC on its own DC. Have you checked /etc/krb5.conf, /etc/hosts > and /etc/resolv.conf ? With the BIND server not running, and this krb5.conf: [libdefaults] default_realm = SAMBA.IFA.NET dns_lookup_realm = false dns_lookup_kdc = true ~ samba_dnsupdate cannot find

Is there a way to get rid of all the routes in a routing table ? This is more or less what I do: route add 146.64.80.0/24 192.168.0.100 route add 146.141.0.0 -interface tun1 route add 146.182.0.0 -interface tun1 route add 146.230.0.0 -interface tun1 netstat -rn inet 146.64.80.0/24 192.168.0.100 UGS 0 0 sis0 146.141.0.0/16 tun1 US 0

On Sun, 14 Aug 2016 21:52:43 +0100 Alex Crow via samba <samba at lists.samba.org> wrote: > > > I am fairly sure this is your problem, it should be able to find the > > KDC on its own DC. Have you checked /etc/krb5.conf, /etc/hosts > > and /etc/resolv.conf ? > > With the BIND server not running, and this krb5.conf: > > [libdefaults] >

> I feel I can tell you this without breaking any confidences, the OP sent me their idmap.ldb and the problem boiled down to these three DNs>> CN=S-1-5-32-545> CN=S-1-5-32-544> CN=S-1-5-32-546> > The classicupgrade seems to set these to 'ID_TYPE_GID' instead of 'ID_TYPE_BOTH'.>> RowlandI can confirm this. After changing 'ID_TYPE_GID' to

Hello! I've just built my first samba4 (4.0.5) on an OpenIndiana machine without any problems. But when it comes to the provision step the problems begin. Everything is fine, if I call samba-tool with the --use-ntvfs option. But I want to use samba4 with s3fs because of the support for newer SMB protocol versions. But when I call samba-tool without --use-ntvfs option I got the following:

In addition with Rowlands comment. I suggest you try /etc/hosts add only 127.0.0.1 localhost Now type Hostname -f Hostname -s Hostname -d Hostname -I Are these all correct? > No, Edit resolv.conf domain samba.ifa.net search samba.ifa.net ifa.net nameserver 127.0.0.1 What happens now if you try the above command. Correct? Yes => correct your hosts and resolv.conf No || \/

Dear All, I've recently upgrade from samba 4.1.x to samba 4.2.14 and found that GPO are having issue Specifically when I'm adding new using they *never *got the gpupdate success fully. When I run samba-tool ntacl sysvolcheck or samba-tool ntacl sysvolreset But don't seem to got it fix.. Any suggestion? Thank in advance. #samba-tool ntacl sysvolcheck Processing section