back for a bit because i can,
i think that with opting for the removal of certian aspecs zentyal might (or might not) grow towards a better solution to its goal,
but at the same time it breaks a lot of essential stuff going on...
the problem here lies with that zentyal is really a verry high level management interface, which for most novice sysadmins is a "good thing
TM".
but there is and always has been a key issue... zentyal for example wants to also do dhcp and other network stuf. where it shouldn't dont mess with my router/firwall/utm gateway servers... by now we should ALL know that zentyal is decent at best if we look at lan / wan management. even in small (less than 10 workstations), setups a dualcore xeon E4xxx had issues routing my 100mbit wan connection, and stuf like youtube online games or torrents would hogg the system down to... well you really dont want to know...
so instead of droping the webserver (whitch should have been improved (like i have said about 200 times), rather than abandoned, and NUT which could also use some work (you really do want to use an Uninteruptible power supply on your office server)
why not instead drop dhcpd and the firewall module...
take pfsence for example
https://www.pfsense.org/about-pfsense/features.html has loads and loads and loads more features than zentyal could ever hope to get... why not just give a screen at the end of your setup wizzard, telling people what settings to choose in there network management tool... rather than doing it yourself poorly...
as for removing webserver, 8 out of every 10 offices run custom software crap on thair windows servers, either build in ms accees or vb or what not, when migrating those offices to linux requires them to also change thos badd build it in exel or access habbits, what better way is there than to offer of the shelve wwwroots where you can host any php app you can get (or build), prefeably with some aditional tooling to supply them with user / group authentication or restriction etc.
the default configs of sutch should probably be a default created /srv/www/dns-name/ folder stucture, with a log folder, a httpdocs root folder and a config file to override apache.conf and php.ini as well as aproprate dns atributes for the domain.
intergrating 3rd party aplications into your user-managment / office email etc infra structure is way more importand and a lot less trivial than managing a nework, withc any soho-router can already do just fine, if need be
if you want to commit zentyal an office server, than make it one, that works, and abandon the right modules