samba domain integration
-
@Uncle-Frank Just for test i put “NULL” then “(NULL)” into “Organizational Unit” in AD configuration without success
-
Bug confirmed and isolated. Ticket has been made here:
https://github.com/FOGProject/fog-client/issues/22
Basic explanation:
For some reason the samba LDAP domain is returning an error code of 1355 instead of 2 or 50 (which correspond to OU errors). On OU errors the client will try using a null OU. I just have to add 1355 to the cases of OU errors. -
@Jbob Hello, does it means that the new client will works now or do i have to wait the new “patched” client ?
Any way thanks for your help -
@plegrand The patch will be applied next release.
-
@Jbob Just for information , as i don’t know if the client have the patch which permit to join samba domain, i made a test today without success.
Same problem. But may be I’ve to wait a little. -
The patch will only be applied on the next official release 0.9.6 or 0.10.0
-
@Jbob thanks for your answer, for the moment i use the 4103 .
Thanks again -
@Jbob is there a date for this new release ?
-
No release date is planned. For now keep using the legacy client. The next release of the client will be v0.10.0 which will include OSX + Linux compatibility.
-
@Jbob said:
No release date is planned. For now keep using the legacy client. The next release of the client will be v0.10.0 which will include OSX + Linux compatibility.
That’s what I’m waiting for!
That is gonna blow minds left and right.
-
Joe Schmitt Senior Developerlast edited by Joe Schmitt Nov 11, 2015, 10:04 PM Nov 12, 2015, 3:57 AM
@plegrand v0.9.6 is released, and this includes the Samba fix. (https://news.fogproject.org/client-v0-9-6/)
-
@Jbob Wonderful !!!
I was waiting for this !!
I’m going to test today and i’ll tell you the result
thanks again !!! -
@Jbob Hello
In first sorry for this long delay
I just made the test today with the latest client. Everything seems to work fine !!