Hi Nicolas, Thanks for your answer. I got more info as well. Basically Azure AD works in a completely different way. To be compatible with LDAP or "legacy" domain join it has the Azure Active Directory Domain Services, the problem here is that this is read-only, not manageable at all, only used for authentication. So basically I don't even have an option to manually add the machine to it, I think the only way is if somehow this object creation can be skipped since the domain join is actually successful. Any thoughts?
Thanks On Wed, 12 Sep 2018 at 13:50, Nicolas Quiniou-Briand via PacketFence-users < [email protected]> wrote: > Hi José, > > On 2018-09-11 05:10 PM, Jose Duarte via PacketFence-users wrote: > > Is this account creation 100% needed? Any way to "precreate" it in Azure > > Portal and avoid this step? > > The man page of the net command (man 8 net on CentOS 7) use to join the > domain says: > > ``` > Join a domain. If the account already exists on the server, and [TYPE] > is MEMBER, the machine will attempt to join automatically. (Assuming > that the machine has been created in server manager) Otherwise, a > password will be prompted for, and a new account may be created. > ``` > > I think you can try to precreate your Computer account in the desired OU. > -- > Nicolas Quiniou-Briand > [email protected] :: +1.514.447.4918 *140 :: https://inverse.ca > Inverse inc. :: Leaders behind SOGo (https://sogo.nu), PacketFence > (https://packetfence.org) and Fingerbank (http://fingerbank.org) > > > _______________________________________________ > PacketFence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users >
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
