similar to: Centos 7 samba 4.6.0 packages

I know how to build samba but what I am not as familiar with is creating rpm packages. I was hoping to find the "official" CentOS version to start with. On 03/15/2017 02:57 PM, Miguel Medalha via samba wrote: >>> Any Samba 4.6.0 packages (including src packages) >>> available for Centos 7 yet? > https://wiki.samba.org/index.php/Build_Samba_from_Source > >

I hope that someone here can give some advice on the following: I have a Samba based Active Directory. A CentOS 7.6 machine runs as a file server and hosts the Windows user profiles for all the Windows workstations. Now management has decided that they need a Windows server for a couple of administrative applications, which need MS SQL Server. That would be the only role of this Windows.

I was permitted too. But you were faster. :-) Possibly it's also worth to mention here: https://wiki.samba.org/index.php/Samba_AD_management_from_windows I don't have a computer right now and it's difficult/not so comfortable to edit with a mobile. Am 14. Februar 2015 00:11:08 MEZ, schrieb miguelmedalha at sapo.pt: > >> Full ack! +1 >> >> Regards >> Tim

> Full ack! +1 > > Regards > Tim > > Am 12. Februar 2015 22:12:45 MEZ, schrieb Miguel Medalha > <miguelmedalha at sapo.pt>: >> >> I am using a Samba 4.1.16 as an Active Directory domain controller. >> >> After a lot of time complaining to myself that my users' properties >> sheet in ADUC did not contain the Unix Attributes tab, it

Oh! It's works. Thanks a lot. God bless you all. --- Gilberto Nunes Ferreira (47) 99676-7530 - Whatsapp / Telegram Em qui., 30 de mai. de 2024 ?s 10:40, miguel medalha <medalist at sapo.pt> escreveu: > For a GPO to work, both "Authenticated Users" and "Domain Computers" must > have "Read" rights. > > On a Policy Object, go to

>> Did you think to run 'samba-tool domain tombstones expunge --help' ? No, I didn't, I just assumed that the message "'samba' will remove them daily, 'samba-tool domain tombstones expunge' would do that immediately" would mean exactly that :-). It worked now. Thank you!

> On 04 Jun 2016, at 22:14, Miguel Medalha <medalist at sapo.pt> wrote: > > >> Can someone therefore please explain to me what exactly these GPO >> restrictions are that Samba can't handle? I'd also appreciate if someone >> could list which other GPO I cannot set successfully using RSAT. > > It seems to me that the FAQ is pretty clear. The

On Fri, 10 Aug 2018 13:20:15 +0100 "miguel medalha" <medalist at sapo.pt> wrote: > > > > By default, every AD user is a member of 'Domain Users' and so, > > > > when you use the 'rid' backend every Unix user gets the group as > > > > their primary group. > > > > > > > The only way to change this is by using

On Fri, 10 Aug 2018 14:32:01 +0100 "miguel medalha" <medalist at sapo.pt> wrote: > > >having a particular group > > > set as "Primary group" > > > How are setting the 'primary group' ? > > The 'primary group' had been set a long time ago, when the system was > created. It had been set with ADUC, under the

On Tue, 07 Aug 2018 22:43:23 +0100 Miguel Medalha via samba <samba at lists.samba.org> wrote: > > By default, every AD user is a member of 'Domain Users' and so, > > when you use the 'rid' backend every Unix user gets the group as > > their primary group. > > > The only way to change this is by using a version of Samba >= 4.6.0 > > and

Hi, is there a "How to" for upgrading a DC from 4.2.10 Sernet packages to Samba 4.4.2 self compiled on a debian system? I think there are two options? Replace the sernet file: 1. Compile Samba (https://wiki.samba.org/index.php/Build_Samba_from_source) with the paths given by smbd -b 2. make install But what happens to the sernet packages/repository handled by the package manager?

On Thu, 13 Sep 2018 14:41:54 +0100 miguel medalha via samba <samba at lists.samba.org> wrote: > Hello > > In one of my DCs, when I run ./configure for Samba 4.9.0, it fails > with the following message: > > Checking for lmdb >= 0.9.16 via header check : not > found Samba AD DC and --enable-selftest requires lmdb 0.9.16 or later > > My ./configure command

> > Finally 'browseable' is redundant on a Samba AD DC, there is no > browsing on an AD DC. > Well, sometimes you just *have* to do some file serving out of an AD DC. It happened to me. In that case, if you don't have "browsable = yes" on a share, that share will not appear in the Computer Management applet in Windows and you won't be able to set its

Let me be the first (maybe): CentOS 5.2 is here (at least): http://mirror.chpc.utah.edu/pub/centos/5.2/ Thank you all who worked on it! -------------- next part -------------- No virus found in this outgoing message. Checked by AVG. Version: 8.0.100 / Virus Database: 270.4.1/1513 - Release Date: 22-06-2008 7:52

I am using a Samba 4.1.16 as an Active Directory domain controller. After a lot of time complaining to myself that my users' properties sheet in ADUC did not contain the Unix Attributes tab, it finally occurred to me that I should look again into Windows 7 >> Control Panel >> Programs and Features >> Turn Windows Features on and off. Lo and behold, there it is: under

On Thu, 13 Sep 2018 16:17:20 +0100 "miguel medalha" <medalist at sapo.pt> wrote: > > >> It might help if you tell us what your actual './configure' was ? > > >> Something else might be pulling in the requirement for lmdb. > > Here it goes: > > ./configure -j 8 --with-systemd --with-statedir=/usr/local/samba/var >

On Fri, Dec 1, 2017 at 7:38 AM, Miguel Medalha <medalist at sapo.pt> wrote: >>> Could someone recommend good Linux software RAID primer. It would >> be good if it has good coverage of monitoring and dealing with failures. > > https://raid.wiki.kernel.org/index.php/Linux_Raid +1 and practice recovery scenarios using VMs with virtual disks. -- Arun Khan

> (...) By default a samba AD DC sets the login shell for all > Active Directory user accounts to /bin/false. The only way I've found to > change this, is to override that globally with the "template shell = > /bin/bash" option in smb.conf, which enables it globally for all Active > Directory users (probably not desired). Using RFC2307 you can give each user its own

Thanks. I did read that. Maybe my understanding is wrong. I thought that by adding the samba service, everything that shows as samba would be enabled. 445, 139, etc didn't have samba so I added them with --add-port. Is that not an accurate assumption? Do I need to open each of those ports individually rather than allowing the service? The only thing I don't see is: tcp 0 0

Hi, This way don't works too. root at samba4-dc:~# samba-tool fsmo transfer --role=forestdns -Uadministrator Password for [EMPRESA\administrator]: ERROR: Failed to add role 'forestdns': LDAP error 53 LDAP_UNWILLING_TO_PERFORM - <000020AE: SvcErr: DSID-03152BF7, problem 5003 (WILL_NOT_PERFORM), data 0 > <> root at samba4-dc:~# samba-tool fsmo transfer --role=domaindns