search for: proxmox_63nfmdcompani

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

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

Hi I tried it but it does not work. I then use: https://github.com/Azure/azure-sdk-for-python This allows to manage my windows azure accounts in a python script. I then create a script that sends the user's password when it changes. It is a system similar to that of "G Suite Password Sync" I use the "Check password script" option in samba. (Valid in the branch 4.5 of

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 can see > that: > > > > > Company Name  COMPANY > > Domains

Microsoft says: "We synchronize the password hashes" Does a samba DC have similar password hashes as a (real) windows DC? Can we somehow allow the AD Connect to access that hash? It would be SO disappointing if we really need all kinds of extra tools to make this work. :-( And Simon, would you be willing to share a bit more on your https://github.com/Azure/azure-sdk-for-python

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

For my script : https://github.com/sfonteneau/script_modify_password_googleapps_and_office365 Azure AD: https://github.com/sfonteneau/script_modify_password_googleapps_and_office365/blob/master/script/office/officepassword.py Another idea: AD refuses to change a password on a clear connection. It may be the same for the consultation of the hash? Have you set up lts or ldaps with ad ? The