[debian-edu-commits] [Debian Wiki] Update of "DebianEdu/Documentation/Stretch/GettingStarted" 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/GettingStarted" page has been changed by WolfgangSchweer:
https://wiki.debian.org/DebianEdu/Documentation/Stretch/GettingStarted?action=diff&rev1=5&rev2=6

Comment:
fix typos; thanks victory.

   1. Add users with GOsa²
   1. Add workstations with GOsa² - thin-client and diskless workstation can be used directly without this step.
  
- Adding users and workstations is described in detail below, so please read this chapter completely. It covers how to perform these minumum steps correctly as well, as other stuff that everybody will probably need to do.
+ Adding users and workstations is described in detail below, so please read this chapter completely. It covers how to perform these minimum steps correctly as well as other stuff that everybody will probably need to do.
  
  There is additional information available elsewhere in this manual: the [[../Features|New features in Stretch|]] chapter should be read by everyone who is familiar with previous releases. And for those upgrading from a previous release, make sure to read the [[../Upgrades|Upgrades]] chapter.
  
@@ -174, +174 @@

  
  Machine management basically allows you to manage all networked devices in your Debian Edu network. Every machine added to the LDAP directory using GOsa² has a hostname, an IP address, a MAC address and a domain name (which is usually "intern"). For a fuller description of the Debian Edu architecture see the [[../Architecture|architecture]] chapter of this manual.
  
- Diskless workstations and thin-clients work out-of-the-box when connected to the main network. Only workstations with disks '''have''' to be added with GOsa², but all '''can'''.
+ Diskless workstations and thin-clients work out-of-the-box when connected to the main network. Only workstations with disks '''have to''' be added with GOsa², but all '''can'''.
  
  To add a machine, use the GOsa² main menu, systems, add. You can use an IP address/hostname from the preconfigured address space 10.0.0.0/8. Currently there are only two predefined fixed addresses: 10.0.2.2 (tjener) and 10.0.0.1 (gateway). The addresses from 10.0.16.20 to 10.0.31.254 (roughly 10.0.16.0/20 or 4000 hosts) are reserved for DHCP and are assigned dynamically.
  
  To assign a host with the MAC address 52:54:00:12:34:10 a static IP address in GOsa² you have to enter the MAC address, the hostname and the IP; alternatively you might click the {{{Propose ip}}} button which will show the first free fixed address in 10.0.0.0/8, most probably something like 10.0.0.2 if you add the first machine this way. It may be better to first think about your network: for example you could use 10.0.0.x with x>10 and x<50 for servers, and x>100 for workstations. Don't forget to activate the just added system. With the exception of the main server all systems will then have a matching icon. 
  
- If the machines have booted as thin clients/diskless workstations or have been installed using any of the networked profiles, the {{{sitesummary2ldapdhcp}}} script can be used to automatically add machines to GOsa². For simple machines it will work out of the box, for machines with more than one mac address the actually used one has to be chosen, {{{sitesummary2ldapdhcp -h}}} shows usage information. Please note, that the IP addresses shown after usage of {{{sitesummary2ldapdhcp}}} belong to the dynamic IP range. These systems can then be modified though to suit your network: rename each new system, activate DHCP and DNS, add it to netgroups, if needed; reboot the system afterwards.
+ If the machines have booted as thin clients/diskless workstations or have been installed using any of the networked profiles, the {{{sitesummary2ldapdhcp}}} script can be used to automatically add machines to GOsa². For simple machines it will work out of the box, for machines with more than one mac address the actually used one has to be chosen, {{{sitesummary2ldapdhcp -h}}} shows usage information. Please note, that the IP addresses shown after usage of {{{sitesummary2ldapdhcp}}} belong to the dynamic IP range. These systems can then be modified to suit your network: rename each new system, activate DHCP and DNS, add it to netgroups if needed, reboot the system afterwards.
  The following screenshots show how this looks in practice:
  
  {{{
@@ -232, +232 @@

   * NFS.
    The home directories are exported by the main-server to be mounted by the workstations and the LTSP servers. For security reasons, only hosts within the workstation-hosts, ltsp-server-hosts and server-hosts {{{NetGroups}}} can mount the exported NFS shares. So it is rather important to remember to configure these kinds of machines properly in the LDAP tree using GOsa² and to configure them to use static IP addresses from LDAP.
  
-   /!\ Remember to configure workstations and ltsp-servers properly with GOsa², or your users won't be able to access their home directories. Diskless workstations and thin clients don't use NFS, so they don't need to be configured.
+   /!\ Remember to configure workstations and LTSP servers properly with GOsa², or your users won't be able to access their home directories. Diskless workstations and thin clients don't use NFS, so they don't need to be configured.
   * fs-autoresize
    Debian Edu machines in this group will automatically resize LVM partitions that run out of space.
   * shutdown at night
@@ -240, +240 @@

   * CUPS (cups-queue-autoflush-hosts and cups-queue-autoreenable-hosts)
    Debian Edu machines in these groups will automatically flush all print queues every night, and re-enable any disabled print queue every hour.
   * netblock-hosts
-   Debian Edu machines in this group will only be allowed to connect to machines on the local network.  Combined with web proxy restrictions this might be used during exams.
+   Debian Edu machines in this group will be allowed to connect to machines only on the local network.  Combined with web proxy restrictions this might be used during exams.
  
  Another important part of machine configuration is the 'Samba host' flag (in the 'Host information' area). If you plan to add existing Windows systems to the Skolelinux Samba domain, you need to add the Windows host to the LDAP tree and set this flag to be able to join the Windows host to the domain. For more information about adding Windows hosts to the Skolelinux network see the [[../HowTo/NetworkClients#Connecting_Windows_machines_to_the_network_.2BAC8_Windows_integration|HowTo/NetworkClients]] chapter of this manual.