similar to: classicupgrade migration issues

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

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

On Mon, Mar 7, 2016 at 4:38 PM, Andrew Bartlett <abartlet at samba.org> wrote: > Also just check you have the unix users and groups that you are trying > to upgrade. Do the mapped unix groups need to be added to the new host before attempting the upgrade? There is nothing in the docs regarding that. Am I mistaken in thinking that the AD does not rely on matching or mapped unix groups

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 >

On 26/04/15 23:21, Sonic wrote: > 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

On 18/03/16 14:31, Sonic wrote: > On Mon, Mar 7, 2016 at 4:38 PM, Andrew Bartlett <abartlet at samba.org> wrote: >> Also just check you have the unix users and groups that you are trying >> to upgrade. > Do the mapped unix groups need to be added to the new host before > attempting the upgrade? There is nothing in the docs regarding that. No, I am sure you don't

On Fri, 2016-03-18 at 10:31 -0400, Sonic wrote: > On Mon, Mar 7, 2016 at 4:38 PM, Andrew Bartlett <abartlet at samba.org> > wrote: > > Also just check you have the unix users and groups that you are > > trying > > to upgrade. > > Do the mapped unix groups need to be added to the new host before > attempting the upgrade? There is nothing in the docs regarding

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

How does one create all of the builtin groups for this release? When using tdbsam with previous releases one would automatically get such groups as: System Operators (S-1-5-32-549) -> -1 Replicators (S-1-5-32-552) -> -1 Guests (S-1-5-32-546) -> -1 Domain Admins (S-1-5-21-1832519723-2688400599-3493754984-512) -> domadmin Domain Guests (S-1-5-21-1832519723-2688400599-3493754984-514)

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

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

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

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

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

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/

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:

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

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

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