|
|
147.
|
|
|
sudo mkdir -p /srv/samba/netlogon
|
|
|
|
|
sudo mkdir -p /srv/samba/netlogon
|
|
Translated and reviewed by
Daniel LeBlanc
|
|
|
|
Located in
serverguide/C/windows-networking.xml:910(command)
|
|
|
148.
|
|
|
sudo touch /srv/samba/netlogon/logon.cmd
|
|
|
|
|
sudo touch /srv/samba/netlogon/logon.cmd
|
|
Translated and reviewed by
Daniel LeBlanc
|
|
|
|
Located in
serverguide/C/windows-networking.xml:911(command)
|
|
|
149.
|
|
|
You can enter any normal Windows logon script commands in <filename>logon.cmd</filename> to customize the client's environment.
|
|
|
|
|
You can enter any normal Windows logon script commands in <filename>logon.cmd</filename> to customize the client's environment.
|
|
Translated and reviewed by
Daniel LeBlanc
|
|
|
|
Located in
serverguide/C/windows-networking.xml:914(para)
|
|
|
150.
|
|
|
With <emphasis>root</emphasis> being disabled by default, in order to join a workstation to the domain, a system group needs to be mapped to the Windows <emphasis>Domain Admins</emphasis> group. Using the <application>net</application> utility, from a terminal enter:
|
|
|
|
|
With <emphasis>root</emphasis> being disabled by default, in order to join a workstation to the domain, a system group needs to be mapped to the Windows <emphasis>Domain Admins</emphasis> group. Using the <application>net</application> utility, from a terminal enter:
|
|
Translated and reviewed by
Daniel LeBlanc
|
|
|
|
Located in
serverguide/C/windows-networking.xml:922(para)
|
|
|
151.
|
|
|
sudo net groupmap add ntgroup="Domain Admins" unixgroup=sysadmin rid=512 type=d
|
|
|
|
|
sudo net groupmap add ntgroup="Domain Admins" unixgroup=sysadmin rid=512 type=d
|
|
Translated and reviewed by
Daniel LeBlanc
|
|
|
|
Located in
serverguide/C/windows-networking.xml:929(command)
|
|
|
152.
|
|
|
Change <emphasis role="italic">sysadmin</emphasis> to whichever group you prefer. Also, the user used to join the domain needs to be a member of the <emphasis>sysadmin</emphasis> group, as well as a member of the system <emphasis>admin</emphasis> group. The <emphasis>admin</emphasis> group allows <application>sudo</application> use.
|
|
|
|
|
Change <emphasis role="italic">sysadmin</emphasis> to whichever group you prefer. Also, the user used to join the domain needs to be a member of the <emphasis>sysadmin</emphasis> group, as well as a member of the system <emphasis>admin</emphasis> group. The <emphasis>admin</emphasis> group allows <application>sudo</application> use.
|
|
Translated and reviewed by
Daniel LeBlanc
|
|
|
|
Located in
serverguide/C/windows-networking.xml:933(para)
|
|
|
153.
|
|
|
Finally, restart Samba to enable the new domain controller:
|
|
|
|
|
Finally, restart Samba to enable the new domain controller:
|
|
Translated and reviewed by
Daniel LeBlanc
|
|
|
|
Located in
serverguide/C/windows-networking.xml:944(para)
|
|
|
154.
|
|
|
You should now be able to join Windows clients to the Domain in the same manner as joining them to an NT4 domain running on a Windows server.
|
|
|
|
|
You should now be able to join Windows clients to the Domain in the same manner as joining them to an NT4 domain running on a Windows server.
|
|
Translated and reviewed by
Daniel LeBlanc
|
|
|
|
Located in
serverguide/C/windows-networking.xml:956(para)
|
|
|
155.
|
|
|
Backup Domain Controller
|
|
|
|
|
Backup Domain Controller
|
|
Translated and reviewed by
Daniel LeBlanc
|
|
|
|
Located in
serverguide/C/windows-networking.xml:966(title)
|
|
|
156.
|
|
|
With a Primary Domain Controller (PDC) on the network it is best to have a Backup Domain Controller (BDC) as well. This will allow clients to authenticate in case the PDC becomes unavailable.
|
|
|
|
|
With a Primary Domain Controller (PDC) on the network it is best to have a Backup Domain Controller (BDC) as well. This will allow clients to authenticate in case the PDC becomes unavailable.
|
|
Translated and reviewed by
Daniel LeBlanc
|
|
|
|
Located in
serverguide/C/windows-networking.xml:968(para)
|
