I would like to start a thread were we could discuss Nethserver design layouts for SME or more advanced home users. The all in one server solution is good but not very convenient for SME’s in my opinion.
I’m very interested in productive running Nethserver installations were we could discuss setup combination and learn from each other? Good discussion points would be roundcube vs SoGo (In what scenarios are those used (mobile, PC)) or Owncloud vs Samba shares (Should both be used in 2 different scenarios (tasks, contact, files etc) or combined) and how can those be configured with Nethserver.
I’m working on a base test layout were I want to have a GW running on PFsense (Very good secure and scalable FW/GW were information from different services is reused for easy configuration via the webconsole and this i a must if you made changes in the FW on a daily basis) on a virtualization platform from ProxMox (Very stable KVM virtualization platform and it supports management server, backup and HA out of the box).
When it comes to Nethserver I’m still testing several combinations from having one centralized LDAP server and several decentralized Nethserver installations for Samba (Not easy) and Mail mainly for security reasons, scalability and to keep each server as simple as possible. How can a Nethserver GW installation be competitive with Pfsense (Maybe with a combination of a proxy were firewall settings are static)? I’m still to new to know how stable Nethserver is if you use an all in one installation and how often installation break during upgrade. I’m also still learning the config db settings of Nethserver which are pretty new to me.
Scenario: How does a normal user look like in a SME company? I share and example of my view ** but how does your look SME user look like**?:
- Mobile device with need of secure and encryptet mail, contact, tasks and calender sync
- Laptop roadrunner needs to have secure access via VPN to mail, contacts, tasks and files and offline access without VPN.
- Secure way to chat and use videoconferencing on the road and in the office.
Biggest challenge is to use as few components as possible to achieve the scenario described to keep the installation as simple and secure as possible.