ISC DHCP with ldap in AD?

[Alexis]

>> The ldif you got is an OpenLDAP ldif not a Samba4 ldif, if you are
>> trying to convert a Openldap schema to a Samba4 ldif, you need to use
>> oLschema2ldif.
>> What you are trying to do has been tried, there is quite a series of
>> postings about it, if you care to search the mailinglists archives.
>> From what I can remember it failed due to attributes clashing, same
>> names or something similar.
>>
>> Rowland
>>
>>
> As someone who have tried it in the past I can tell you that converting
> the schema is the easy part. The problem is, that the schema used by ISC
> DHCPD conflicts with the AD schema, so if you forcibly load it you can
> have a destroyed domain. In the past (during the alphas) I had a test
> domain where was able to run ISC DHCPD (after loading its schema), by
> renaming two attributes in the default AD schema, but that is highly
> hackish. That renaming was allowed against a Samba AD DC (at an alpha
> version at least) but not with a Win2k8 server, where it complained
> about having a basic schema object, whose rename is impossible.
> I've decided to postpone the integration of our ISC DHCP database into
> AD for now:
> 1. Short term: use OpenLDAP
> 2. Long term: rename all the dhcp... attributes and objectClasses to
> isc-dhcp... and load that schema into AD, patch isc-dhcpd to run with
> the modified schema (at least if you specify ldap-type=ad in the config
> file)
> 
> Regards
> 
> Geza Gemes
I think that topic was worth being investigated a bit more and I learned 
some interesting clue from your comments thank you all.

I suppose I'll stick with the openldap on special port solution.