In Debian Edu context the main criticism since the release of Debian Edu / Skolelinux squeeze is: the whole Debian Edu system has become far to complex (LDAP, Kerberos, GOsa², Samba, LTSP, …). The default Skolelinux system has become more complex. If it has become too complex is another discussion.

However, those who feel overwhelmed by its grown complexity, please consider this approach:

• Install ipFire as a Gateway on some minor hardware
  • Red + Green interface
  • let the Red interface connect you to the internet
  • Enable DHCP service on the Green interface

• Assemble an average server box:
  • 4 or 8 CPU cores
  • 16GiB or 32GiB RAM
  • two fast hard drives (SSD)
  • 2 network cards
• Install a Debian Edu / Skolelinux Standalone system (no TJENER!)
• Make sure that your Skolelinux system's hostname can internally be resolved via DNS. Use the ipFire system to configure this.
• Test local login, test DNS, install required (educational) software
• Create more users on the Skolelinux system through the normal Posix tools (adduser) or through some fancy user administration GUI (present in KDE / GNOME)

• Then proceed setting up X2Go Server on the Skolelinux system:
  • Add the X2Go archives for Debian to the Skolelinux system
  • Install the packages x2goserver-xsession and x2goserver-fmbindings on the Skolelinux machine. Optionally, you may want to install the package x2godesktopsharing.
  • Test X2Go access to the Skolelinux system from another client machine that gets hooked up on the Green network interface of the ipFire system

• Then proceeed with setting up the X2Go Thin Client Environment on the Skolelinux system:
  • Install the package x2gothinclient_management on the Skolelinux system
  • Follow the X2Go TCE documentation in this wiki to get the TCE up and running
  • Make sure you serve the X2Go Thin Clients via the second network interface of the Skolelinux system