[debian-edu-commits] [Debian Wiki] Update of "DebianEdu/Documentation/Stretch/HowTo/NetworkClients" by WolfgangSchweer

[Debian Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Debian Wiki" for change notification.

The "DebianEdu/Documentation/Stretch/HowTo/NetworkClients" page has been changed by WolfgangSchweer:
https://wiki.debian.org/DebianEdu/Documentation/Stretch/HowTo/NetworkClients?action=diff&rev1=10&rev2=11

Comment:
replace aptitude (which isn't installed by default) w/ apt, and dist-upgrade w/ full-upgrade.

  
  A diskless workstation runs all software locally. The client machines boot directly from the LTSP server without a local hard drive. Software is administered and maintained on the LTSP server (inside of the LTSP chroot), but it runs on the diskless workstation. Home directories and system settings are stored on the server too. Diskless workstations are an excellent way of reusing older (but powerful) hardware with the same low maintenance cost as with thin clients. 
  
- LTSP defines 320MB as the default minimum amount of RAM for diskless workstations. If the amount of RAM is less, the machine will boot as thin client. The related LTSP parameter is {{{FAT_RAM_THRESHOLD}}} with the default value 300. So if (for example) the clients should only boot as diskless workstations if they have 1 GB RAM add {{{FAT_RAM_THRESHOLD=1000}}} to lts.conf (or set this in LDAP). Unlike workstations, diskless workstations run without any need to add them with GOsa², cause LDM is used to login and connect to the LTSP server.
+ LTSP defines 320MB as the default minimum amount of RAM for diskless workstations. If the amount of RAM is less, the machine will boot as thin client. The related LTSP parameter is {{{FAT_RAM_THRESHOLD}}} with the default value 300. So if (for example) the clients should only boot as diskless workstations if they have 1 GB RAM add {{{FAT_RAM_THRESHOLD=1000}}} to lts.conf (or set this in LDAP). Unlike workstations diskless workstations run without any need to add them with GOsa², because LDM is used to login and connect to the LTSP server.
  
  '''LTSP client firmware'''
  
@@ -114, +114 @@

  
  For performance and security considerations it might be desired to set up a separate main server which doesn't act as LTSP server. 
  
- To have ltspserver00 serve diskless workstations on the main (10.0.0.0/8) network, when tjener is not a combined server, follow these steps:
+ To have ltspserver00 serve diskless workstations on the main (10.0.0.0/8) network, when the main server is not a combined server, follow these steps:
  
-  * copy the `ltsp` directory from `/var/lib/tftpboot` on ltspserver00 to the same directory on tjener.
+  * copy the `ltsp` directory from `/var/lib/tftpboot` on ltspserver00 to the same directory on the main server.
-  * copy {{{/var/lib/tftpboot/debian-edu/default-diskless.cfg}}} to the same directory on tjener.
+  * copy {{{/var/lib/tftpboot/debian-edu/default-diskless.cfg}}} to the same directory on the main server.
   * edit {{{/var/lib/tftpboot/debian-edu/default-diskless.cfg}}} to use the IP address of ltspserver00; the following example uses 10.0.2.10 for the IP address of ltspserver00 on the main network:
  {{{
   DEFAULT ltsp/i386/vmlinuz initrd=ltsp/i386/initrd.img nfsroot=10.0.2.10:/opt/ltsp/i386 init=/sbin/init-ltsp boot=nfs ro quiet ipappend 2
  }}}
-  * set the symlink in {{{/var/lib/tftpboot/pxelinux.cfg}}} on tjener to point to {{{/var/lib/tftpboot/debian-edu/default-diskless.cfg}}}.
+  * set the symlink in {{{/var/lib/tftpboot/pxelinux.cfg}}} on the main server to point to {{{/var/lib/tftpboot/debian-edu/default-diskless.cfg}}}.
  
  As an alternative, you could use {{{ldapvi}}}, search for 'next server tjener' and replace tjener with ltspserver00.
  
@@ -245, +245 @@

  
   * Configure this machine to run a printer in lts.conf (default location: {{{/opt/ltsp/i386/etc/lts.conf}}}, see the LTSP manual {{{/usr/share/doc/ltsp/LTSPManual.html#printer}}} for details.
  
-  *  Configure the printer using the web interface {{{https://www:631}}} on tjener; choose network printer type {{{AppSocket/HP JetDirect}}} (for all printers regardless of brand or model) and set {{{socket://<LTSP client ip>:9100}}} as connection URI.
+  *  Configure the printer using the web interface {{{https://www:631}}} on the main server; choose network printer type {{{AppSocket/HP JetDirect}}} (for all printers regardless of brand or model) and set {{{socket://<LTSP client ip>:9100}}} as connection URI.
  
  === Upgrading the LTSP environment ===
  
@@ -253, +253 @@

  
  {{{
  ltsp-chroot -a i386  # this does "chroot /opt/ltsp/i386" and more, ie it also prevents daemons from being started
- aptitude update
+ apt update
- aptitude upgrade
+ apt upgrade
- aptitude dist-upgrade
+ apt full-upgrade
  exit
  }}}
  
@@ -267, +267 @@

  ltsp-chroot -a i386
  ## optionally, edit the sources.list:
  #editor /etc/apt/sources.list
- aptitude update
+ apt update
- aptitude install $new_package
+ apt install $new_package
  exit
  }}}
  
@@ -286, +286 @@

  
  == Connecting Windows machines to the network / Windows integration ==
  === Joining a domain ===
- For Windows clients the Windows domain "SKOLELINUX" is available to be joined. A special service called Samba, installed on the main-server tjener, enables Windows clients to store profiles and user data, and also authenticates the users during the login.
+ For Windows clients the Windows domain "SKOLELINUX" is available to be joined. A special service called Samba, installed on the main server, enables Windows clients to store profiles and user data, and also authenticates the users during the login.
  
  /!\ Joining a domain with a Windows client requires the steps described in the [[DebianEdu/Documentation/Stretch/HowTo/Samba|Debian Edu Stretch Samba Howto]].
  
- Windows will sync the profiles of domain users on every Windows login and logout. Depending on how much data is stored in the profile, this could take some time. To minimise the time needed, deactivate things like local cache in browsers (you can use the Squid proxy cache installed on tjener instead) and save files into the H: volume rather than under "My Documents".
+ Windows will sync the profiles of domain users on every Windows login and logout. Depending on how much data is stored in the profile, this could take some time. To minimise the time needed, deactivate things like local cache in browsers (you can use the Squid proxy cache installed on the main server instead) and save files into the H: volume rather than under "My Documents".
  
  ==== User groups in Windows ====
  
@@ -304, +304 @@

  
  FIXME: It would be even better to first/also explain user groups for Windows  with GOsa² (and then show an example for the command line)
  
- If you want to check user groups on Windows, you need to download the tool {{{IFMEMBER.EXE}}} from Microsoft. Then you can use this for example in the logon script which resides on tjener in {{{/etc/samba/netlogon/LOGON.BAT}}}.
+ If you want to check user groups on Windows, you need to download the tool {{{IFMEMBER.EXE}}} from Microsoft. Then you can use this for example in the logon script which resides on the main server in {{{/etc/samba/netlogon/LOGON.BAT}}}.
  
  === XP home ===
  
- Users bringing in their XP laptops from home can still connect to tjener using their skolelinux credentials, provided the workgroup is set to SKOLELINUX. However, they may need to disable the Windows firewall before tjener will appear in Network Neighbourhood (or whatever it's called now).
+ Users bringing in their XP laptops from home can still connect to the main server using their skolelinux credentials, provided the workgroup is set to SKOLELINUX. However, they may need to disable the Windows firewall before the main server will appear in Network Neighbourhood (or whatever it's called now).
  
  === Managing roaming profiles ===
  
@@ -326, +326 @@

  
  /!\ '''Note''' The examples are outdated since in wheezy kerberos was configured for samba too!<<BR>>
  
- You might find an example smb.conf in your preferred language delivered by the installation on tjener under `/usr/share/doc/debian-edu-config/examples/`. The source file is in English and is called `smb-roaming-profiles-en.conf`; look for a file with the appropriate code in the filename (the German translation, for example, will be named `smb-roaming-profiles-de.conf`). Inside the config file are a lot of explanations which you should have a look at.
+ You might find an example smb.conf in your preferred language delivered by the installation on the main server under `/usr/share/doc/debian-edu-config/examples/`. The source file is in English and is called `smb-roaming-profiles-en.conf`; look for a file with the appropriate code in the filename (the German translation, for example, will be named `smb-roaming-profiles-de.conf`). Inside the config file are a lot of explanations which you should have a look at.
  
  ==== Machine policies for roaming profiles ====
  
@@ -346, +346 @@

  
  ==== Global policies for roaming profiles ====
  
- By using the legacy Windows policy editor (`poledit.exe`), you can can create a Policy file (NTConfig.pol) and put it in your netlogon share on tjener. This has the advantage of working almost instantly on all Windows machines. 
+ By using the legacy Windows policy editor (`poledit.exe`), you can can create a Policy file (NTConfig.pol) and put it in your netlogon share on the main server. This has the advantage of working almost instantly on all Windows machines. 
  
  For some time, the policy editor standalone download has been removed from the Microsoft web site, but it's still available as part of the ORK Tools. 
  
- With `poledit.exe` you can create .pol files. If you put such a file on tjener as `/etc/samba/netlogon/NTLOGON.POL` it will automatically be read by Windows machines and temporarily overwrite the registry, thus applying the changes.
+ With `poledit.exe` you can create .pol files. If you put such a file on the main server as `/etc/samba/netlogon/NTLOGON.POL` it will automatically be read by Windows machines and temporarily overwrite the registry, thus applying the changes.
  
  To make sensible use of `poledit.exe` you also need to download appropriate .adm files for your operating system and applications; otherwise you cannot define many settings in `poledit.exe`.
  
@@ -405, +405 @@

  FIXME: describe roaming profile key for the global policy editor here
  
  ==== Disabling roaming in smb.conf ====
- If, perhaps, everyone has their own dedicated machine, and nobody else is allowed to touch it, editing the Samba configuration will let you disable roaming profiles for the entire network. You can alter the `smb.conf` file on tjener, unsetting the "logon path" and "logon home" variables, then restart samba.
+ If, perhaps, everyone has their own dedicated machine, and nobody else is allowed to touch it, editing the Samba configuration will let you disable roaming profiles for the entire network. You can alter the `smb.conf` file on the main server, unsetting the "logon path" and "logon home" variables, then restart samba.
  
  {{{
  logon path = ""