similar to: Joining a 2022-schema Active Directory

Le Thu, 3 Oct 2024 21:35:04 +0100 Rowland Penny via samba <samba at lists.samba.org> ?crivait: > > Yes, I mean Windows 11 or WIndows Server 2022 machines that are > > registered into the AD. A Win11 PC which isn't AD-connected (but in > > the same IP network) can connect just fine using the server IP > > address and credentials from one of the domain user

On Thu, 3 Oct 2024 22:04:11 +0200 Emmanuel Florac <eflorac at intellique.com> wrote: > Le Thu, 3 Oct 2024 16:20:38 +0100 > Rowland Penny via samba <samba at lists.samba.org> ?crivait: > > > > > > > "smbclient" on Linux connects to the share just fine using domain > > > user credentials. Only domain members can't... > > >

On Fri, 4 Oct 2024 10:11:37 +0200 Emmanuel Florac <eflorac at intellique.com> wrote: > Le Thu, 3 Oct 2024 21:35:04 +0100 > Rowland Penny via samba <samba at lists.samba.org> ?crivait: > > > > Yes, I mean Windows 11 or WIndows Server 2022 machines that are > > > registered into the AD. A Win11 PC which isn't AD-connected (but > > > in the same

Le Fri, 4 Oct 2024 09:27:12 +0100 Rowland Penny via samba <samba at lists.samba.org> ?crivait: > > > > OK, I'll try first the 4.17 version from the backports, and if it's > > not enough I'll upgrade to 4.20. > > I would upgrade to bookworm with Samba from backports, but its your > domain ;-) I've just upgraded to bookworm, I'll check how

Hi, I have tried that too and that did not help either (i.e adding the format type=gpt) The output you requested ``` $ sudo qemu-img info --backing-chain /var/virt/WINDOWS/WIN11 image: /var/virt/WINDOWS/WIN11 file format: qcow2 virtual size: 60 GiB (64424509440 bytes) disk size: 55.1 GiB cluster_size: 65536 backing file: WIN11-BASE (actual path: /var/virt/WINDOWS/WIN11-BASE) backing file

On Thu, Sep 21, 2023 at 10:50:07 +0100, Bhasker C V wrote: > Attaching win11.xml > Please note that this used to work fine. It is failing now on libvirt- > 9.7.0-1 > > On Thu, Sep 21, 2023 at 9:13?AM Peter Krempa <pkrempa at redhat.com> wrote: > > > On Thu, Sep 21, 2023 at 09:05:43 +0100, Bhasker C V wrote: > > > Adding libvirt mailing list > > >

Le Fri, 4 Oct 2024 09:27:12 +0100 Rowland Penny via samba <samba at lists.samba.org> ?crivait: > > > > OK, I'll try first the 4.17 version from the backports, and if it's > > not enough I'll upgrade to 4.20. > > I would upgrade to bookworm with Samba from backports, but its your > domain ;-) Well I've upgraded up to 4.20, but no dice :( No

Hi, I found that the base of Samba 4 DC is different from the base of Windows Server 2008 DC. There are many mistakes when I make the comparison as the result as follows (only parts of reult): samba-tool ldapcmp ldap://WINDC1 ldap://SAMBA4-DC -Uadministrator Password for [EMPRESA\administrator]: * Comparing [DOMAIN] context... * DN lists have different size: 1787 != 1788 * DNs found only in

Attaching win11.xml Please note that this used to work fine. It is failing now on libvirt- 9.7.0-1 On Thu, Sep 21, 2023 at 9:13?AM Peter Krempa <pkrempa at redhat.com> wrote: > On Thu, Sep 21, 2023 at 09:05:43 +0100, Bhasker C V wrote: > > Adding libvirt mailing list > > apologies for cross-posting > > libvirt version: 9.7.0-1 > > > > On Thu, Sep 21, 2023

Adding libvirt mailing list apologies for cross-posting libvirt version: 9.7.0-1 On Thu, Sep 21, 2023 at 8:39?AM john doe <johndoe65534 at mail.com> wrote: > On 9/21/23 09:32, Bhasker C V wrote: > > I am getting an error with libivrt when I create a VM > > > > ``` > > $ sudo virsh create ./win11.xml > > error: Failed to create domain from ./win11.xml >

On Thu, Sep 21, 2023 at 09:05:43 +0100, Bhasker C V wrote: > Adding libvirt mailing list > apologies for cross-posting > libvirt version: 9.7.0-1 > > On Thu, Sep 21, 2023 at 8:39?AM john doe <johndoe65534 at mail.com> wrote: > > > On 9/21/23 09:32, Bhasker C V wrote: > > > I am getting an error with libivrt when I create a VM > > > > > >

Hi everyone, I came across this issue today while upgrading a samba4 AD. The forest/domain level is 2008R2, however the schema partition is actually missing the msDS-isRODC attribute (and probably a few others). It makes the ADUC console to failed on that entry below. Here is the samba log message (which is quite explicit :-) Sep 28 16:55:36 srvads samba[27900]: [2016/09/28 16:55:36.819666,

On Thu, Jul 13, 2023 at 11:47?AM Bo Kersey <bo at vircio.com> wrote: > The patch on Windows Server 2012 R2 that does the same thing as kb5028166 > is KB5028228 > > > ------------------------------ > > *From: *"Philippe LeCavalier" <support at plecavalier.com> > *To: *"Bo Kersey" <bo at vircio.com> > *Cc: *"samba" <samba

For the moment, Samba4 cannot participate as DC with Windows 2019 servers (unless you downgrade to schema 47, the one that comes with Windows 2008R2): https://wiki.samba.org/index.php/AD_Schema_Version_Support The developers are working on Windows 2012R2 support.   So for now, anything above 2008R2 is experimental. On 2019-03-19 11:31 a.m., Rowland Penny via samba wrote: > On Tue, 19 Mar

On 21/04/2023 15:11, E Kogler via samba wrote: > Hi fellow Members!I'm Systems administrator at a school using SAMBA 4 as AD DC. > As you know, WIN11 is at the doorstep and my "old" Samba4 Server (4.9) doesn't serve Windows Servers (Server 2019) very well, > e.g. the latest issue is that the domain administrator cannot access the GPO's or other informations from the

Hi fellow Members!I'm Systems administrator at a school using SAMBA 4 as AD DC. As you know, WIN11 is at the doorstep and my "old" Samba4 Server (4.9) doesn't serve Windows Servers (Server 2019) very well, e.g. the latest issue is that the domain administrator cannot access the GPO's or other informations from the Samba-LDAP (authentication failure ?). I think that it has

On Wed, 28 Sep 2016 17:37:32 +0200 Denis Cardon via samba <samba at lists.samba.org> wrote: > Hi everyone, > > I came across this issue today while upgrading a samba4 AD. The > forest/domain level is 2008R2, however the schema partition is > actually missing the msDS-isRODC attribute (and probably a few > others). It makes the ADUC console to failed on that entry below.

I don't think the problem is the schema. It's more likely a replication problem. Firstly, the Samba schema is only used when you provision a new domain. In this case you have joined an existing Windows domain, so you are using the *Windows* schema. (I think it's actually impossible to provision a Samba domain with the 2008 schema - Samba only supports 2008R2 onwards). Secondly,

Hello, I am trying to use Samba in version 4.7.0 as a replication of an Active Directory running on Windows 2012-R2. For that, I execute the process described on this page: https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory When I run the command to join the domain controller, samba-tool returns the following error: DsAddEntry failed with status

Hi, We have 3 samba 4.9.13 AD DC servers (mercurio1, mercurio2, mercurio7), replicating without error. When we add a W2008R2 as additional DC (mercurio3) replication works fine until 24h pass and it fails. On the samba4 DCs side, the command samba-tool drs showrepl shows no error. On the W2008R2 side the command repadmin /showrepl shows inbound replication error from the 3 samba DCs, and