similar to: AD DC as KVM guest on file server host?

The most dramatic disadventage of kvm guest is block device I/O, so I wouldn't recommend to virtualize file server if it is not necessary. In my case on host ntpd configured as source for virtual dc, and bind9 configured as type=slave for zones hosted on dc, (make shure that srv records in _msdcs.mysambadomain.local are resolving when virtual dc is down) and smbd fileserver with

Is kvm I/O realy disadventage? I use samba file server as kvm guest (LVM storage pool) in some setups and disn't notice any problems. Sequential read/write speed isn't noticeably different from non-virtualized samba host. Did I miss something and should expect sudden trouble? In a letter dated Tuesday, December 27, 2016 2:12:59 MSK by Andrei Petrov via samba wrote: > The most dramatic

helo Miguel. i have a fiew production sites, where samba file servers running their dc as kvm guests. No problems so far. Pay attention for dc time sync on startup. Shutdown (not suspend) guest on host shutdown. Make shure that appropriate dns server is available for host and guest dc on startup. 26 дек. 2016 г. 18:07 пользователь "Miguel Medalha via samba" < samba at

Am 21.02.2016 um 19:32 schrieb Miguel Medalha: > I didn't change the source in any way. tar xf to the /root directory > is all I did. I did "make clean" a number of times. The catalog file > is in the expected place. /root/bin/default/docs-xml/build/catalog.xml in your case. > The documentation build always fails with "failed to load external > entity

On Thu, 2018-09-13 at 14:41 +0100, miguel medalha via samba 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 line does not contain the

I have a particular AD domain which, due to hardware- and OS-related issues, is still at version 4.8.12. It is finally possible to upgrade the system. If I add a new version 4.19 DC to the domain, will it replicate correctly from version 4.8.12, or will I need to upgrade in phases, from major version to major version? The current DCs would then be removed from the domain and scrapped. Any tips,

Demotion of a AD DC fails with the following errors: If I explicitly select a partner server with the "--server=" option the error is: Deactivating inbound replication Asking partner server [selectedDC] to synchronize from us Error while demoting, re-enabling inbound replication ERROR(<type 'exceptions.UnboundLocalError'>): uncaught exception - local variable

Am 22.02.2015 um 02:18 schrieb Andrew Bartlett: > On Sat, 2015-02-21 at 20:05 +0000, Miguel Medalha wrote: >> I just came to the conclusion that the rid backend has been very much >> underappreciated. Too much mental inertia about how things used to be >> made? >> >> After strugling for two days to configure a member server against a >> Samba Active Directory

29.12.2016 19:01, Filippe LeMarchand пишет: > Is kvm I/O realy disadventage? I use samba file server as kvm guest > (LVM storage pool) in some setups and disn't notice any problems. > Sequential read/write speed isn't noticeably different from > non-virtualized samba host. Did I miss something and should expect > sudden trouble? No you shouldn't. What I meant is: of

Hi guys, I've migrated from Samba NT4 to Samba AD, joined other Windows DC's to the domain and then demoted my Samba DC. I am not being able to login from client computers with the error stated on the subject. I've tried everything, from making sure replication is OK, client DNS configuration also. Registry modifications from prior Samba NT4 domain were reverted in the client. Are

I just came to the conclusion that the rid backend has been very much underappreciated. Too much mental inertia about how things used to be made? After strugling for two days to configure a member server against a Samba Active Directory with the ad/RFC2307 backend, I turned to the rid backend and voil?! all my problems are gone. Having to manually edit uids/gids in UNIX Attributes under RSAT

Maybe the output of 'samba-tool fsmo transfer --help' should include the -U parameter... > (...) if you enter 'samba-tool fsmo transfer --help' it prints amongst > the output: > > --role=ROLE?????????? The FSMO role to seize or transfer. > ??????????????????????? ....................... > ??????????????????????? ..................... >

On two Samba 4.4.2/4.4.3 member servers, "samba-tool ntacl get --as-sddl" gives the following error: ERROR: Unable to read domain SID from configuration files Which configuration files is it referring to? Without "--as-sddl" the command gives a correct output. It would be nice to get the permissions in sddl format... The same command works as expected on two AC DCs.

On Tue, Mar 13, 2018 at 09:08:36PM +0000, Miguel Medalha via samba wrote: > > > On 13-03-2018 19:22, Karolin Seeger via samba-technical wrote: > > ======================================================== > > "It is time that we all see gender as a > > spectrum instead of two sets of > > opposing ideals. We should stop > > defining each other

On Tue, Mar 13, 2018 at 09:08:36PM +0000, Miguel Medalha via samba wrote: > > > On 13-03-2018 19:22, Karolin Seeger via samba-technical wrote: > > ======================================================== > > "It is time that we all see gender as a > > spectrum instead of two sets of > > opposing ideals. We should stop > > defining each other

02.12.2017 2:16, mj via samba пишет: > - power off the old DCs > - reize fsmo roles, cleanup the database, etc why not to transfer roles while old DC are online? > - add new 4.7.2 DCs using their old names/ips > - remove the temporary DC why not simply add new DCs to current production domain? I'm thinking about way to upgrade too, but using "separated environment"

On 30/04/16 20:31, Andrew Bartlett wrote: > On Sat, 2016-04-30 at 16:35 +0100, Miguel Medalha wrote: >>> In any case, I found and fixed the issue you hit last week, the >>> patch is at https://bugzilla.samba.org/show_bug.cgi?id=11882 The >>> syntax error should then go away (bug I have a patch for that as >>> well, it is on samba-technical if you are

Hi, Hi, I'm having trouble transferring FSMO roles "DOMAINDNS" and FORESTDNS with below showing: samba-tool fsmo transfer --role=domaindns ERROR: Failed to delete role 'domaindns': LDAP error 50 LDAP_INSUFFICIENT_ACCESS_RIGHTS - <00002098: SecErr: DSID-031523E0, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0 > <> root at samba4-dc:~# samba-tool fsmo transfer

On Fri, Jan 23, 2015 at 01:08:31PM -0800, Jeremy Allison wrote: > On Fri, Jan 23, 2015 at 10:05:44PM +0100, Markus Doits wrote: > > > > On 23.01.15 19:57, Miguel Medalha wrote: > > > I am using Samba 4.1.16 with smb2/3 and symbolic links are working alright. > > > > > > Following the smb.conf man page, I use: > > > > > > unix extensions

On 23.01.15 19:57, Miguel Medalha wrote: > I am using Samba 4.1.16 with smb2/3 and symbolic links are working alright. > > Following the smb.conf man page, I use: > > unix extensions = no > wide links = yes > > Unfortunately this still does not work for me - can you really make a symbolic link ("ln -s ...") when you are connected with smb2/3? Does