similar to: Samba4, sssd, new users vs. migrated users

Hi all, After classicupgrade my machine accounts are placed in a separate CN=Computers, with objectclasses: - posixAccount - person - organisationalPerson - user - computer Taking my sssd configuration from https://wiki.samba.org/index.php/Local_user_management_and_authentication/sssd, I have this config: ... ldap_user_object_class = user ... Meaning all my computer accounts are included in

Hi, we are still using a setup with openldap + samba3. On the unix systems we are using ldap for authentication, for all windows clients samba is used. When we migrate to samba4 what will happen to the unix clients ? Can they ask the samba4 PDC ? For an update . are there other Howto's as the https://wiki.samba.org/index.php/Samba4/samba-tool/domain/classicupgrade/HOWTO just to get some

Hello, I'm testing a classicupgrade using ubuntu 14.04 lts and the sernet samba packages. I also configured all other servers in the test network to use sssd, leaving the domain controller last, but I see that sssd-ad cannot be installed alongside sernet-samba. I see that this isn't a new problem, lingering at least since December 2013:

Hey everyone... I'm testing samba3 to samba4 migration and I'm having a problem with group migration. Basically, when I run classicupgrade, he keeps warning about group membership. I increase log level and it tells that the group that some users belongs to don't exist. Is there anyway to tell samba classicupgrade to import groups first and then do the rest? Kind regards, Bruno

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 On AD Server : -------------------- We have migrated from S3 to S4 with samba-tools classicupgrade. All is ok : bind9, winbind but getent has a strange behavior. getent passwd doesn't return the same number of records. So a AD user can be not present in the response of getent !!!! it can have a big difference of records returned from a call to another call of getent passwd ... On

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

Hello. I tried the migration from samba3 domain master (pdc) to a samba4. samba4 -V: Version 4.1.0pre1-GIT-2c3a808 I used the wiki entry about samba3 migration as a guide, copied over the data etc. but I have some questions left. fyi - samba3 tdbsam backend. I removed/edited serveral user accounts with Umlauts in Fullname/Displayname. (tdbdump/text editor/tdbrestore) until all user accounts

Here is my smb.conf (on member domain) : idmap config * : backend = tdb idmap config * : range = 2000-9999 idmap config * : schema_mode = rfc2307 idmap config DOMAIN : backend = ad idmap config DOMAIN : schema-_mode = rfc2307 idmap config DOMAIN : range = 10000-999999 winbind nss info = rfc2307 winbind trusted domains only = no winbind use default domain = yes winbind enum users = yes winbind

Hello: First, sorry for my English. I'm testing samba4 rc5. I have compiled and installed samba4 and now I'm trying to simulate an upgrade from my samba3 site to my samba4 test installation. I have setup a isolated network and I have replicated server and clients, copied my samba3 ldap contents and tdb files. But, when I run samba-tool classicupgrade following to the docs,

Sorry Rowland, my mistake. We used this command: samba-tool domain classicupgrade --dbdir=/usr/local/samba.PDC/dbdir --use-xattrs=yes --realm=domain.br --dns-backend=SAMBA_INTERNAL /usr/local/samba.PDC/etc/samba/smb.conf.PDC Sorry about wrong information. 2016-08-29 15:22 GMT-03:00 Rowland Penny via samba <samba at lists.samba.org>: > On Mon, 29 Aug 2016 15:14:07 -0300 > Maiquel

On 12/05/17 09:10, Marc Muehlfeld wrote: > Hi Sebastian, > > Am 11.05.2017 um 19:39 schrieb Sebastian Arcus via samba: >> I can see in the docs that a domain rename is not >> recommended/supported by Samba for an already provisioned domain. >> However, what I can't work out is if this is not possible during the >> classicupgrade step either? > >

Hi Team, *I'm migrating to samba4 (samba 4.0.7) and doing "Upgrading In Place" **and running classicupgrade; *I have installed openldap-devel...as im migrating database from ldap.* * *while doing this am getting the following error message:* # /usr/local/samba/bin/samba-tool domain classicupgrade --dbdir=/samba-backup/ --use-xattrs=yes --realm=mydomain.com/samba-backup/smb.conf

Hi, I am stuck on upgrading the current Samba3 to Samba4, currently used Samba 3.3.10 and upgraded to Samba 3.4.17 still the same problems below. I also try to upgrade the Python 2.4.3 to Python 2.7 still same problems, with the OpenLDAP 2.3.43. [root at ewanko]# /usr/local/samba/bin/samba-tool domain classicupgrade --dbdir=/var/lib/samba/ --use-xattrs=yes --realm=ewanko.local

Hi all. Problems resolved! I found the samba process that was increasing the memory after I ran the netstat from PID and I discovered that the process opened 88/464 tcp/udp port. After I ran tcpdump program in my DC server listening udp 88 port and I found many clients machines sending traffic a lot to my DC server. I blocked the ips from clients machines by iptables and the samba process

On 12/06/2019 15:58, Marco Gaiarin via samba wrote: > Mandi! Miguel Coa M. via samba > In chel di` si favelave... > >> Actually we have pdc with Samba3 for domain and now install Samba4 for migrate the old samba3. My question is, Is possible make a progressive user migration and both environments works together (shared folders, printers, etc). Or the unique option is migrate

Thanks for the answer. > Did you got errors during the classicupgrade? I didn't do classicupgrade. My Samba AD DC was installed from scratch some months ago using the instructions from this page https://wiki.samba.org/index.php/Samba_AD_DC_HOWTO and everything had been working well. I just upgraded some deb-packages with samba to the same version but different buid-release. Regarding

I am upgrading a samba 3 domain controller with an ldap backend to samba 4 via classicupgrade and was wondering... do I need to upgrade our samba 3 file server at the same time or will it continue to work as is for the time being? Also, I have read conflicting opinions about whether I need to run winbindd on the member server (we do currently) given our use of ldap. Could someone enlighten me

On 8/29/2016 2:43 PM, Rowland Penny via samba wrote: > On Mon, 29 Aug 2016 15:31:40 -0300 > Maiquel Consalter <maiquelconsalter at gmail.com> wrote: > >> Sorry Rowland, my mistake. >> >> We used this command: >> >> samba-tool domain classicupgrade --dbdir=/usr/local/samba.PDC/dbdir >> --use-xattrs=yes --realm=domain.br --dns-backend=SAMBA_INTERNAL

On 22/07/2019 10:24, Alfonso Conner wrote: > Hi Rowland, > > Just a curious question. > Since the origin of my AD comes from PDC. If I were to try and do a > classicupgrade, using same IP, same hostname, same realm, will my > windows pc have login issues? > To be honest, I am not entirely sure, you should get the same results every time you run the classicupgrade, so your