Released: 8 October 2015
ClearOS 7.1.0 Final is here!
ClearOS version 7.1 introduces:
ClearOS Home Release Candidate 1
ClearOS Business Release Candidate 1
New Google® Apps Connector
Updated Microsoft Active Directory Connector
IPv6 Ready (requires command line expertise)
Streamlined Theme System
Updated Antispam and Antivirus Engines
Updated IDS and IPS Engines
Event and Alert Notification Framework
Samba 4 BETA, Directory (Microsoft® Active Directory Replacement)
ClearOS Home and ClearOS Business
This release introduces ClearOS Home and ClearOS Business. At the time of release of ClearOS Community, qualified updates start. Meaning, Users of ClearOS Home and ClearOS Business from day one will have the same updates but as the release candidate cycle for Home and Business gets underway, users will have better and better quality assured updates as they are phased in throughout the Release Candidate cycle for Home and Business. Meaning, you can start using ClearOS for Home and Business today!
Samba Directory BETA
We are excited to add Samba Directory to the mix. Samba Directory allows for Active Directory equivalent functionality using ClearOS as your Directory Server. Simple user and group administration is available for Samba Directory in the usual places in ClearOS' Webconfig. If you comply with Microsoft's EULA for the tool, you can use Microsoft®'s Server administration tools to modify additional aspects of your Samba Directory including Group Policy Objects.
New Upstream Features Include
ClearOS 7 will feature a Community, Home, and Business version. All versions of ClearOS will install from the same install image. You will be required to select your version at the time of installation in the wizard.
The full changelog can be found here:
|64-bit Net Install
Virtual Machine and Cloud Images
Virtual Machine and Cloud Images are not yet available for this release.
There is no supported method yet from upgrading from ClearOS 6 to ClearOS 7. Additionally, the layout for ClearOS 7 Beta 3 is different due to the changes in the build system to Beta 2. Upgrades from Beta 2 require changes to the repo content and performance of a dist-upgrade. There may be support for migration of configuration backups.