Karoshi Client 4.3
Today we are pleased to announce the release of Karoshi Client 4.3! It has many new features, but is designed to work best with Karoshi Server 10.1.
Also please note that the netlogon folder for this version has been changed to karoshi4.3, due to incompatibility with older scripts. If you have any desktop icons in karoshi4, you will want to migrate them over.Interface
XFCE has been updated to 4.12. While this is a new 'major' version since 4.10, not much has changed, but many bugs have been fixed and corner cases improved.
XScreensaver has been replaced with Light Locker. Light Locker uses LightDM as the lock screen, instead of a dedicated application. One known issue with this is that there is no indication that someone is logged into a machine once it is locked. Multiple users can log into a single machine, however.Software controls
Full control of software installation and upgrading is now available. Both whole-domain and location-specific control is possible, controlled from the web management.Firefox and Thunderbird profiles
The whole profile for Firefox and Thunderbird is now saved to the network, rather than just places.sqlite. This means that user preferences will be saved, allowing more flexibility for users that want to tweak their settings. Important preferences, like the homepage or cache size, have been locked down however.Failover and redundancy
This release brings support for failover in case of server failure. The client can switch between domain controllers on the network in case one goes down, improving reliability.
Unbound is installed as a local caching DNS server, which will result in faster, more reliable DNS queries, less load on servers and provides DNS failover.
Network shares are mounted from any available domain controller, if the domain is running Karoshi Server 10.1 with DFS and GlusterFS. This means that even if the main server goes down, client machines can continue running (although access to user files is dependent on the infrastructure configuration).
There is currently one issue with true failover: due to a limitation in the implementation of CIFS within the Linux kernel, only the first referral in a DFS link will be checked. This means that at the moment, failover will be hit and miss, but in the event of a server failure most clients will continue running fine.
Release notes: https://github.com/the-linux-schools-project/karoshi-client/releases/tag/v4.3