samba domain integration
-
Hello,
i’m trying to make that after deploy the client automatically integrate samba domain, but i dont really understand how it works ?
is the service which rename and integrate the client, or another process.
If it’s the service i 've got to log on each station to launch service
On the web interface i configure the "Active directory " section without success.
Does someone could explain me how to do that ?thanks for your help
-
I’m not exactly sure what your asking but at the least we need your server os and fog version and the os of the client and which fog client you are using and maybe a more detailed explanation of what you are trying to accomplish.
-
@Joseph-Hales said:
I’m not exactly sure what your asking but at the least we need your server os and fog version and the os of the client and which fog client you are using and maybe a more detailed explanation of what you are trying to accomplish.
It’s simple
He want to join a Samba Domain instead Active Directory Domain 
-
I’m using FOG latest svn version on debian Jessie.
The station is a Windows 7
The fog client is “New FOG Client Service”
I would like that after deployment the station is automatically renamed and automatically integrated into samba domain.
I tested to configure the “Active Directory” section but it’s active directory… not samba
-
Active directory and Samba “AD replicated kinda” Domain should work the same. It’s just ldap requests.
As long as your Samba configuration is setup properly, the same mechanisms you would use for AD should work.
-
@Tom-Elliott it’s not a samba AD (samba 3.6.6 without AD)
then it cant works ? -
I don’t know, never tried to be honest.
-
@Tom-Elliott said:
I don’t know, never tried to be honest.
Hmm just a question does rename and integration are launched Indifferently after capture or deploy or only after deploy?
-
@plegrand said:
@Tom-Elliott said:
I don’t know, never tried to be honest.
Hmm just a question does rename and integration are launched Indifferently after capture or deploy or only after deploy?
Indifferently
-
If you can write a script to join samba then you could get the same functionality with a snapin.
-
@Joseph-Hales said:
If you can write a script to join samba then you could get the same functionality with a snapin.
It’s a good idea, i already use a script after symantec ghost clonage.
But it would be nicer if fog could do that "natively.
But i keep the idea -
Have you Tried doing it “natively”?
-
We use samba without AD (but LDAP!) and domain joining is done via FOG client (Win7/10) without trouble! As Tom said: Domain does not have to be Active Directory…
-
@Tom-Elliott said:
Have you Tried doing it “natively”?
I made a test without success but i’ll try again on monday
-
@Uncle-Frank said:
We use samba without AD (but LDAP!) and domain joining is done via FOG client (Win7/10) without trouble! As Tom said: Domain does not have to be Active Directory…
I’m using samba also with ldap and i’m very interesting . Could you explain me the way you use ?
Does samba integration is made automaticcaly without snapin ?
Thanks for your answer -
@plegrand said:
Does samba integration is made automaticcaly without snapin ?
Yes! I guess you’ve setup samba kind of like this using smbldap-tools and all the rest: http://www.unixmen.com/setup-samba-domain-controller-with-openldap-backend-in-ubuntu-13-04/
Pay attention to the last couple of screenshots. Windows clients join that domain exactly as if they would join an AD! So from the clients’ point of view there is no difference. Use the FOG clients’ AD settings (edit host and then click ‘Active Directory’ on the left menu).
Prerequisites: FOG client installed and working and domain join for that client should work (try by hand at first).
-
@Uncle-Frank said:
@plegrand said:
Does samba integration is made automaticcaly without snapin ?
Yes! I guess you’ve setup samba kind of like this using smbldap-tools and all the rest
Hello,
i’m using samba with ldap without smbldap-tools but i think it’s not a problem.
I can integrate the windows client manually without problem
Can you explain me what fields you use in the “Active directory” configuration?Domain name
Organizational Unit
Domain Username
Domain Password
Domain Password LegacyThanks for your help
-
@Uncle-Frank
i made some tests this morning without success and i’ve got that in the fog.log file :
HostnameChanger Checking Hostname
HostnameChanger Hostname is correct
HostnameChanger Registering host with active directory
HostnameChanger Logon failure: unknown username or bad password, code = 1326
HostnameChanger Activing host with product keyBut i can integrate manually the windows 7 client
Could you help me ?
What client version are you using?
Thanks -
@plegrand I think the better question to be asked is what fog version are you use? Particularly the client version. Are you using the legacy client or the new client?
Have you ensured your passwords (FOG Crypted in the ADPassLegacy vield) and (Plaintext in the ADPass field as it will auto encrypt for you) are correct?
-
@Tom-Elliott May be the problem is because i’ve got some specials caracters into the password ?
