similar to: Problem with classicupgrade / ProvisioningError

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

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 >

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/

I used to upgrade samba3 to samba4 with almost successful with one problem, administrator can't access. As administrator, by default it is the only user account that is given full control over the system. My query is how to change the administrator password? we have one account which can join to the samba 4 AD based on the migrated data but the problem can't change the administrator or

I'm trying the classicupgrade, and it is crashing out: ERROR(<class 'samba.provision.ProvisioningError'>): uncaught exception - ProvisioningError: Could not add member 'S-1-5-21-305843216-174882882- 1673945419-42545' to group 'S-1-5-21-305843216-174882882-1673945419- 1231' as either group or user record doesn't exist: Unable to find GUID for DN File

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

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 not add group name=Domain Admins ((68, 'Entry CN=Domain

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

When you try to upgrade on a test stand, an error occurs. I do not understand that you need to add ldap, or improve migration script? Before that I tried to version 4.1.7, but the error was the sam root at dc1:~/smb_old# samba --version Version 4.2.2-SerNet-Ubuntu-7.trusty I also modified the file --- ./upgrade.py 2014-10-01 00:00:00.000000000 +0600 +++

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

Hi, During samba 3 migration to samba 4, we receive some errors: /local/bin# samba-tool domain classicupgrade --dbdir=/local/var/dbdir/ --use-xattrs=yes --realm=domain.com --dns-backend=BIND9_DLZ /local/var//smb.PDC.conf --option="interfaces=lo eth0" --option="bind interfaces only=yes" Reading smb.conf Unknown parameter encountered: "share modes" Ignoring unknown

Hi all, I have a problem during classic-upgrade : Importing groups Group already exists sid=S-1-5-21-4023731279-819928261-1073345436-512, groupname=Domain Admins existing_groupname=Domain Admins, Ignoring. Group already exists sid=S-1-5-21-4023731279-819928261-1073345436-514, groupname=Domain Guest existing_groupname=Domain Guests, Ignoring. Group already exists

How do we check the data from Samba4 that the data from Samba3 successfully migrated? I dunno if it successfully migrated coz got these (last part): [root at gaara LiveData]# /usr/local/samba/bin/samba-tool domain classicupgrade --dbdir=/srv/LiveData/var_lib_samba/samba --use-xattrs=yes --realm=kazekage.sura.sandbox.local --dns-backend=SAMBA_INTERNAL /srv/smb.conf Once the above files are

Rowland Penny via samba wrote 2018-09-04 14:24: > On Tue, 04 Sep 2018 10:26:38 +0700 > Konstantin Boyandin via samba <samba at lists.samba.org> wrote: > >> Rowland Penny via samba wrote 2018-09-03 17:12: >> > On Mon, 03 Sep 2018 04:27:07 +0000 >> > "Konstantin Boyandin \(lists\) via samba" <samba at lists.samba.org> >> > wrote:

See inline comments On 18/03/16 20:11, Robert Moulton wrote: > Rowland penny wrote on 3/18/16 12:58 PM: >> On 18/03/16 19:27, Robert Moulton wrote: >>> Rowland penny wrote on 3/18/16 11:48 AM: >>>> On 18/03/16 18:19, Robert Moulton wrote: >>>>> Greetings - On our samba 4 (4.3.3) AD controller I just noticed >>>>> something odd. When I

On 07/03/16 19:04, Sonic wrote: > Sorry for the long post but attempted this several over the past year > with no success but staying on an NT4 domain is no longer viable. Need > to get this resolved so hopefully there will be a clue somewhere in > this montage. > > The current PDC is samba-3.6.25 running on Gentoo using tdbsam backend. > The new AD will be a Debian LXC

I decided to restart the provisioning process. I stopped the samba_server, deleted /usr/local/etc/smb4.conf and /var/db/samba4. I then decided to do an interactive provisioning and this is the result: [root at smb4-1 ~ (master)]# ll /var/samba4 ; ll /usr/local/etc/smb4.conf ls: /var/samba4: No such file or directory ls: /usr/local/etc/smb4.conf: No such file or directory [root at smb4-1 ~

Rowland penny wrote on 3/18/16 1:19 PM: > See inline comments > > > On 18/03/16 20:11, Robert Moulton wrote: >> Rowland penny wrote on 3/18/16 12:58 PM: >>> On 18/03/16 19:27, Robert Moulton wrote: >>>> Rowland penny wrote on 3/18/16 11:48 AM: >>>>> On 18/03/16 18:19, Robert Moulton wrote: >>>>>> Greetings - On our samba 4

Hello, I'm testing samba4. I've setup a small samba3+ldap pdc, and then I tried a classicupgrade, but I can't pass step 4 of the howto. ubuntu at samba4:~/samba4$ /usr/local/samba/sbin/samba -V Version 4.1.0pre1-GIT-899cdc4 ubuntu at samba4:~/samba4$ sudo /usr/local/samba/bin/samba-tool domain classicupgrade --realm=example.com --dbdir=/root/samba /root/samba/smb.conf Reading