similar to: AD Azure Connect

Hi, trying to revert 4.8.0/1 issues with sambaundoguididx and getting following: Traceback (most recent call last): File "/root/sambaundoguididx", line 66, in <module> db.modify(modmsg) _ldb.LdbError: (32, 'ldb_wait from (null) with LDB_WAIT_ALL: No such object (32)') A transaction is still active in ldb context [0x56060ac2a310] on

Hi all, An update. On 10/26/20 10:24 PM, Andrew Bartlett wrote: > The fact that there is a viable workaround (pass-though authentication) > also seems to be making this harder to fix - because it remains an > annoyance, not a deal-breaker. Today I tried again with these ingredients: - fresh azure tenant - fresh installed AD (samba 4.12.8 sernet) - an azure "custom domain

That is a major bummer. :-( Would it work any better, if I promoted our windows 2012 server to a domain controller? Or would that have all kinds of other side-effects..? (we're currently running three dc's, all samba) One side-effect I can think of: GPO's, in a mixed samba/windows DC...? Any ideas what the requirements on the samba side would be, for samba to be able to

On 14/11/2016 0:43, Andrew Bartlett via samba wrote: > On Fri, 2016-11-11 at 11:42 +0100, mj via samba wrote: >> Hi, >> >> We setup the microsoft azure AD Connect on a windows 2012 server, to >> start using (testing) office 365 in the future. We're running a >> samba >> 4.4.4 AD. >> >> This all worked, in the portal.office.com admin section we

hello our AD domain is hosted by two samba AD domain controllers version 4.12.6 - replication between controllers is fine, no problems. - no schema errors. - no database errors, all fine. - no CPU utilizations - wthout noticeable bandwidth utilization Recently we have deployed Azure AD connector on dedicated windows system (system is domain member server). since this deployment we are observing

Hi Michal, Seems we are doing similar things at the moment: getting samba to work with azure AD. We also see the high CPU usage on the DC that the Azure AD Connect server connected to. Between 70 - 100 percent in our case. We are not seeing any replication issues after azure AD Connect, and I have a script that automatically checks replication every few minutes. I was the one reporting the

We joined one MS Windows 2012 R2 server to our Samba DC fleet and pointed the Azure AD sync tool to that new Windows AD server and Azure password sync is working well now. I don?t have any experience with distribution groups. Good Luck! > On May 4, 2020, at 10:21 AM, Marcio Merlone via samba <samba at lists.samba.org> wrote: > > So, testing samba 4.12 on a Debian buster I found

Hi, We setup the microsoft azure AD Connect on a windows 2012 server, to start using (testing) office 365 in the future. We're running a samba 4.4.4 AD. This all worked, in the portal.office.com admin section we can see that: > Company Name COMPANY > Domains verified 2 > Domains not verified 1 > Directory sync enabled true > Last directory sync last synced 3

just small update: - idfix tool (Directory Synchronization Error Remediation Tool / https://github.com/microsoft/idfix) shows just small issues like empty/missing displayName attrib in some of objects which I have corrected and no more issues present at all. - no errors from AAD connect event viewer: final log message is "Scheduler::SchedulerThreadMain : Completed configured scheduler

G'Day Marcio and gabben, Douglas (CC'ed) is going to try and look into why this doesn't 'just work' with Samba. No promises, but at least a trained eye will look over the process. If you could help him get set up and understand what works and doesn't that will leave him more time for actual debugging. The Azure AD sync feature is a big of an oddity in Samba, because it

On 3/11/23 04:33, Andrew Bartlett via samba wrote: > On Fri, 2023-03-10 at 13:06 -0800, Ray Klassen via samba wrote: >> I'm very interested in this. Can one of the devs elaborate on what has been >> accomplished with this? Specifically, I'd like to know if the support is >> bidirectional -- can azure change passwords in samba ad? > > No, I just fixed the issue

On Fri, 2023-03-10 at 13:06 -0800, Ray Klassen via samba wrote: > I'm very interested in this. Can one of the devs elaborate on what has been > accomplished with this? Specifically, I'd like to know if the support is > bidirectional -- can azure change passwords in samba ad? No, I just fixed the issue where it couldn't pull a password from Samba to Azure AD Azure AD Cloud

The AD connect sync to office365 also works with 4.10.18 i can not test with 4.11.x because on this version there is another bug requarding adding DNS records. so: 4.10.x -> the sync works 4.11.x -> i can not test 4.12.6 -> the sync fails with Errorcode: 0x55 Am Mittwoch, den 30.09.2020, 20:45 +0000 schrieb Heinz H?lzl via samba: > Hi, > > > I have downgraded a DC to

I am trying to track down what happened with the ?kernel-azure? packages that were created by the Virt SIG? I see the last release was August 2020. I also can?t seem to find the sources in the Virt repo (http://mirror.centos.org/centos/7/virt/x86_64/azure/Packages/k/), nor in the CentOS git repo (https://git.centos.org/group/sig-virt). I?m assuming the status is you no longer wish to build the

Hi, we use "Azure AD connect" to sync users from the samba-AD to office365. The synchronization worked fine for about 2 years. Now I get an error when I start a full import: stopped-connectivity - failed-search - timeout - Errorcode: 0x55 I'm not sure if it has happened since upgrading from 4.10.5 to 4.12.6 or if it is due to the increased amount of users. I have to do a

Hi Michal, Thanks for updating, I can confirm your findings on our site. Pass-through auth works nicely here as well. However, when reading the ticket, we understand that Ralph B?hme claims that password-hashes should also work, after making the sync account MSOL_604447e... a member of "domain admins". (instead of keeping the default rights that are granted by the installer, which

Hi, We are (again) looking at syncing our samba AD to the azure AD cloud. I installed a win2016 server domain member server and set it up for syncing, including password hashes, so users can login azure/O365 using their on-prem passwords. We're using microsoft's latest tech: the new "Azure AD Connect cloud provisioning". We made sure to check "password hash sync".

I've made some minor changes to the join document for Azure AD. Specifically, there was a major mistake in the TransportKey definition. If you're working on a join implementation, make sure you pay close attention to the changes. Azure accepts just about any blob in the TransportKey field, and doesn't perform any validation on it. This only becomes obvious when future responses

Hi, We are preparing to migrate our mail server to Azure and would like to integrate it vi AD Connect with our AD - Samba 4.7 upgrading to 4.11 (Thanks Louis!). Anyone willing to share the experience? I see on some not-so-old posts there is a problem syncing password hashes, but since samba is an ever evolving solution I would like to know how are you dealing with this? Thanks and best

Release Announcements --------------------- This is the latest stable release of the Samba 4.11 release series. Changes since 4.11.5: --------------------- o Douglas Bagnall <douglas.bagnall at catalyst.net.nz> * BUG 14209: pygpo: Use correct method flags. o David Disseldorp <ddiss at samba.org> * BUG 14216: vfs_ceph_snapshots: Fix root relative path handling. o Torsten