"...The little Dell Optiplex GX260 small form that hosted SME server finally died (6 years). The SME server has been reliable as gravity all this time...."
LANMonkey - source
"The major thing I like about SME Server (and have since I worked at Mitel and they bought E-Smith) is that it just works. A very simple installation..."
Ricks1950 - Source
"It has been a long, long time since I posted on this list. I am not a developer. I don't write code but I do stitch , tape and glue systems together so that they work for companies. I have been off in VoIP land for a few years but am retuning to SME.
I am quiet capable ( now) of building any system from scratch but more often that not I throw in an e-smith server
The reason for this is being demonstrated on this list right now. Careful consideration at development level allows ordinary, and lazy, users to throw in an e-smith and be confident that it will work just like it says on the tin.
That is no mean feat and something that has been happening for a long time here. It takes huge effort to maintain that level of quality and consistency.
SME server release cycles make Redhat look like wild mad things. This can be seen as a problem. It can also be seen as a virtue. In over 15 years of e-smithery I have not once had a production system fail due to software error or hacked due to lax security. Isn't that cool?
The server manager is old. It not accurately reflect how much has happened under the hood. It is clunky and ugly but it has one redeeming feature.
It removes almost all technical verbiage from the user interface. Add a user, Add a group, Add an ibay. It just works and the user knows nothing about passwd, shadow and shells. No mention of DHCP, DNS and PPTP. Just "remote access"
Running setprop from the command line enable me to accurately and quietly set-up a major change on the server and then not activate it until it is all done. This is hugely advantageous in a production environment.
From e-smith 4.04 onwards it has kicked bottom.
Will get back on bug tracker.