similar to: Changing administrator password after Samba4 classic upgrade

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

Hi, I used to upgrade/migrated samba 3.3.10 to samba 3.4.17 with LDAP backend in place, while upgrading the CentOS from 5.5 to 5.9. In place to retain the trust relationship. The users can able to login without re-authentication from existing machines. Tested 3 XPs, and 3 Win7 but it takes 5-8 mins to login compared to 1 win7 that was re-connected (disconnected from domain, restart, then rejoin

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

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 >

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 run 'samba-tool fsmo show' I get an error: >>>> >>>> #

Testing this "classic upgrade" scenario on a test server and have some issues. I'm using the Sernet 4.2.1 packages on Debian Wheezy. I copied the required tdb files and the smb.conf to the new test server (named WHEEZY). Edited the smb.conf to reflect the new host/netbios name of WHEEZY (remember that I want to keep the old PDC in service afterword for file and print sharing duties

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 container running on Debian Jessie using samba compiled from git

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, 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, I used to successfully migrated Samba3 to Samba4 but there are some problems which I can't proceed coz it needs to be re-authenticated the computers/machines previously connected in Samba3. As I observed, using the Windows Remote Administration Tools (Active Directory Users and Computers) under the Computers, the computer name properties in General tab some entries are blanks a) DNS name

Rowland Penny via samba <samba at lists.samba.org> writes: > On Thu, 22 Mar 2018 10:50:35 +0700 > Olivier via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> I am progressing slowly with the migration from Samba3 to Samba4. >> >> I have escaped the bug 13060, now I get to: >> >> Adding groups >> Importing groups

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:

I am attempting to migrate a Slackware server with Samba 4.12.3 from an NT style domain to AD. I have done this about 7-8 times on other servers in the past following the instructions on Samba's wiki. This time however, the upgrade process is failing completely to import any users or groups from the NT domain. I have enclosed below the output of the classicupgrade command - I can't

Hi, I am progressing slowly with the migration from Samba3 to Samba4. I have escaped the bug 13060, now I get to: Adding groups Importing groups Group already exists sid=S-1-5-21-1360262076-8766554542-0991298654-513, groupname=Unix Group Users existing_groupname=Domain Users, Ignoring. Committing 'add groups' transaction to disk Adding users Importing users Committing 'add

Rowland Penny via samba писал 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: > >> Hello, >> >> Going further with migrating NT4 domain (Samba 3) to Samba 4. Thanks >> for the previous suggestions. >> >> When doing >> >> #

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 +++

Hello, I'm running a Samba 4.3.3 install on FreeBSD 8.4 (ZFS) in domain mode with passdb tdb backend. The databases and config files are the current versions of an install that I think started in the 1.9.x version range back in the late 90s (I can't remember exactly--it's been a long time!) and smbpasswd days. I'm now trying to convert to an AD install using the classicupgrade

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 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 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