similar to: classicupgrade - resolving group conflicts

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"

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

We have a third party mail system which can write/read accounts to/from AD using ldaps protocol, it works fine with active directory of windows server 2003. When I test the mail system with samba4 DC, I can't disable user from the mail system, because the mail system write 0x800002 (8388610,UF_ACCOUNTDISABLED | UF_PASSWORDEXPIRED) to userAccountControl field of AD/samba4, and samldb returns

Hello, Actually migrating users/groups from samba3 to samba4 (in a separate domaine), i succeeded in importing users/gruops and their attributes. But For a reason i don't know some (a few) groups are not being created, and i get this error: "Failed to create group "MYGROUP" - samldb: Account name (sAMAccountName) 'MYGROUP' already in use! " Searching in ADUC

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

Am 2016-12-01 um 15:41 schrieb Rowland Penny via samba: > Have you altered /etc/resolv.conf, on the DC, to use its own ip as the > first nameserver ? That change seems to have fixed it! I added that now to network config for the VM. klist ok now step by step ;-) thanks

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/

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! Yes already tried this, both he always says that the account already exists even if it does not exist, it affects only dicamicas entries, entries staticas work and replication as well, but as dynamic are troubled by instances in Multiple Sites will have problems ... But some log or command that can help? Thanks Em 30-12-2015 18:38, Rowland penny escreveu: > On 30/12/15 19:57,

Hello! Output of command # 1 record dn: CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=MYDOMAIN cn: {31B2F340-016D-11D2-945F-00C04FB984F9} name: {31B2F340-016D-11D2-945F-00C04FB984F9} Referral # ref: ldap: //interno.mastersonda.com.br/CN=Configuration,DC=MYDOMAIN Referral # ref: ldap: //interno.mastersonda.com.br/DC=DomainDnsZones,DC=MYDOMAIN Referral # ref: ldap:

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

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

The reason why is that simple: the other admin only knows the windows world and that's why it's gonna be risky regarding file services when he creates new users or groups and forgets about the Unix tab. My personal hope is that samba will one day set rfc ids automatically so that these windows guys won't have to care. E.g. it could be an option when provisioning a new domain. It would

I have a Samba problem with eGroupware. Samba 4 is screwing with my eGroupware UIDs causing Havoc. Samba 4 uses the last four Digits of the SID rather than the UID Number. I need to know how to alter my user entry SID so that the last four digits of the SID is congruent with the UID Numbers of my users. To fix this; I need the ability to edit the last digits of the SID. I've tried shutting

Hello all, Having difficulty with setup of samba with FDS backend. Probably some thing simple, but I can't figure it out, any help would be greatly appreciate, Groupmap command fails, abbreviate debug out follows. Peter 2006/03/20 08:56:02, 5] lib/charcnv.c:charset_name(81) Substituting charset 'UTF-8' for LOCALE [2006/03/20 08:56:02, 5]

Hi I am new to linux & Samba. I would like to setup Samba as a domain controller and using Fedora-ds for authentication. I have read some documents from www.samba.org but I am still in the mist. Here is my dumb questions about Samba as follows. 1. Is CENTOS4.6+SAMBA3.0.25 as PDC +FEDORA-DS possible? 2. Is this HOWTO from

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

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

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: