brendon redick wrote: I disagree that AD should be pro only, I have been using active directory at home for over 10 years, roaming profiles are a must in my house, and there is only 2 of us. (unfortunately it broke at some point between 6.5 and 6.6, which has left all of my computers in a bit of a state of limbo on the domain)
Yes, we realize that AD is used as a niche product in homes. We even have some users running their own mail server system at home, but it's a tiny use case of course.
If the underlying mechanism is there in community there is no reason we should be forced to pay a subscription to pro to enable full use of it.
Just to clarify, there's nothing stopping someone from running Samba 4 in Active Directory mode on ClearOS. What was developed for ClearOS is an accounts driver for hooking into the webconfig users/groups system. There's no shenanigans going on with the underlying Samba 4 packages - those will be identical across all editions and users will have full use of it.
It seems with every new version of clearos community since I started using it in 5.1(ish) that there are features that become a premium or completely unavailable in the next version.
I can't think of an app that has gone from free to paid with the exception of Mail Archive. Yes, we have added a whole bunch of apps for Pro only (AD Connector, master/slave, Google Apps, Kaspersky, etc.), but we haven't taken anything away.
Compounding the upgrade or not choice is the lack of clear upgrade paths, having to start from scratch essentially with major version changes was not something I expected when I moved from using SmoothWall community.
Yes, that is a bummer. Going from version 5 to 6 wasn't supported upstream. It's a bit better in the 6 to 7 upgrade, but not exactly user-friendly and seamless (details).
It looks like some updates were unintentionally released to the contribs repo. So far, it looks like ffmpeg and BackupPC are the two big issues. We had scheduled to look at ffmpeg just after the final release of 6.6.0 (tracker), so the package in clearos-test should not have been promoted to the contribs repo.
You're right, of course...managing SSL certificates with websites could certainly be made a lot more user friendly with not having to drop down to the command line being the ultimate goal.
To answer your question on why...it's all a matter of resources and priorities. There's three ways for things to get developed in ClearOS...
1. ClearCenter to invest resources to have paid developers work on the feature
2. Volunteers from the community to commit time to a project
3. 3rd party developers to create apps/extensions that are installed via the Marketplace, with the option to charge for the app to recoup time invested
For what you're describing, only 1 or 2 are really viable since (#3) it's difficult to take a free app, make it better, then charge for the entire app for the new feature.
So now you're down to whether ClearCenter can see an ROI and whether this precedes all other development going on or someone finding time in the community.
At ClearCenter, we've discussed better integration since many don't know that we resell signed certs from providers Thawte, Comodo and GeoTrust, so there is a path to an ROI...just nothing that outweighs some of the other stuff going on.
I've added it to the bug tracker as a feature so it can be commented on and viewed by others...but that's about as far as I can guarantee it goes for the short term.
nashibacker wrote: If you can make samba4 in active directory mode for community with limit of 20-25 users at least will be much useful for small business users.
I hope you can see that we're not too keen on such a scenario. A shop with 20-25 Microsoft access licenses should be willing to part ways with an $80 / year ClearOS Professional subscription to support their open-source Linux server solution. I would hope.
Deploying Samba4 in Active Directory mode is only required by businesses/organizations, so it will only be available in the Professional Edition... sorry. Samba4 is still used in the Community Edition, but not in Active Directory mode.