Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - cdebackere

Pages: [1]
Dutch / Zentyal + aparte samba fileserver
« on: October 03, 2014, 06:34:40 pm »
Ik heb een zentyal draaien als test setup op een HP380 met VMware. (doel is migratie van sbs)
Ik zou liefst alle data appart houden van ZEntyal OS om eventuele problemen later te kunnen ondervangen (en om de transitie te vergemakkelijken).

Ik zie 2 opties:
- een aparte physical disk toevoegen aan de zentyal vm : kan dit? iemand ervaring mee? (is in feite een vmware vraag)
- een aparte samba fileserver (vm) draaien op aparte data disks. Die fileserverver aan de AD van zentyal toevoegen zodat alle permissies via AD/users/groups kan beheerd worden. Heeft hier iemand ervaring mee? Want ik lees veel problemen van Zentyal met samba en ACL's. Een snelle test is alvast mislukt

Ik zou ook de roaming profiles en de user data op die aparte drive/samba willen.
Kan dit? Want zentyal lijkt daar een vaste positie in het FS voor voorzien te hebben.

Alle input/ideeën welkom



I want to keep the data (profiles, file shares, ...-) of the users/project of the ZEntyal domain on a location independant from the ZEntyal server which runs as a virtual machine.
I'm looking to see if I can add a physical drive to the virtual machine and to mount it as drive. If not possible (likely, since it kill the idea of a virtual machine) I will add a ubuntu virtual machine to act purely as fileserver on samba; this fileserver would be joined to the zentyal domain ADC for access control.

Of course I can setup shares for project use on the fileserver etc.
But my question is: how do I assure that the default location for the roaming profiles and user data is also put on the fileserver (or on a separate/different drive that the zentyal virtual drive)?
Can I create a share 'userdate' and 'mount' that fileserver share into the /home/samba ?
Or can I change the default location?

I have basic linux knowledge so some indications of commands to be used would be nice.



In the mean while I got a (commercial) answer from the commercial guy anyway. But that was limited to the typical business model stuff, which I appreciate.

But when he told we that we would pay more than double if we split the functions we need in 3 vm's (1 for infra services, 1 data&mail, 1 DMZ) then he really lost me as a customer. Our servers/OS typically run 8 years. For the 8-year support of 3 zentyal vm's we can get a full MS solution, and get a professional guy to setup & support us with the nasty issues .. and still save money. I've no problem paying support, but the proposed model is completely top-heavy. We have less than 10 users, but really insist in 'no cloud' and segration of services due to bad experiences.

Anyway: your answer helps me on a lot more. Thanks



That means that all (or at least a big part) of the time we'll spend risks to get lost ?!?

I understand the technical issue due to differences in base-and-other-versions, but then I would expect an update path like doing a new install (in a new vm), and then allow the new commercial version to connect to the community version server to retrieve a big part of the config/user profiles/mailfiles/...

Ok then. We'll then first reconsider if we'll even give a full try or not.

Another issue: the guys of are very fast in providing quotations and other commercial info, but when you ask what we'll miss when we would try the community version: absolute silence! We asked it twice without the slightest response.

Can anybody here tell us what we miss out on? (I know about the beta/untested release and updates, but that makes sence)


Installation and Upgrades / Community upgrade path to commercial
« on: May 19, 2014, 10:01:43 am »

I've been using and trying to setup the community edition for a week now, but due to typical SMB time constraints, the evaluation will take some more time in order to conclude we can abbandon our SBS environment altogether.

Eventually we would consider the paid version in order to have better stability (avoiding beta issues etc.). Now I seem to have read 'a rumor' that there would be no upgrade path from the community edition to a commercial edition. Is this correct?

Should we see the community and commercial editions as 2 completely separated products? Or is updrage an easy 'click 'n pay' task?


Pages: [1]