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 - murz

Pages: 1 [2] 3
16
I need to change NetBIOS domain name in Zentyal 4.1 system with already created users.
Before apply changes I see warning:
Quote
Changing the domain name will cause to reprovision the samba database. The users and groups will be imported from Zentyal LDAP, but you will have to rejoin all computers to the new domain.
It's ok that I must rejoin computers, and good that users and groups will be imported.

But when I apply changes, I see empty list in Users!
Why user database is lost? How I can restore users database?

17
If I try to share (create) russian folder via Zentyal in mode "Directory under Zentyal" - it accept Russian symbols normally, and successfully create, share folder. The problem is only with mode "File system path".

18
I want to share folder with non-latin (Russian) symbols via Samba on Zentyal 4.1, but got the error. Folder with English names shares normally. Here is screenshot of problem: http://i.imgur.com/26rJu7Z.png
Same problem is in English interface: http://i.imgur.com/tC9RmcY.png
I try to add folder "/тест" (Russian word "test"), but got the error:
Quote
Path /тест is not a directory
Seems that the problem is with encoding UTF-8 symbols in Zentyal scripts.

Description of problem in Russian for search engines:
Quote
Не работает расшаривание для общего доступа (Шаринг файлов) в "Добавить новый общий ресурс" через Samba если в пути есть папки с символами русских букв в Zentyal 4.1.

How can I fix this problem?

19
Installation and Upgrades / Re: Zentyal MySQL innodb
« on: October 04, 2015, 01:03:55 pm »
We can enable InnoDB for MySQL on Zentyal server without changing Zentyal conf files via creating file like /etc/mysql/conf.d/zzz.cnf with contents:
Code: [Select]
[mysqld]
innodb = on
This will overwrite Zentyal config parameter.

20
Installation and Upgrades / Re: 3.5: Error restarting service mail
« on: October 02, 2015, 08:52:15 am »
I got the same problem with Zentyal 4.0.9 and 4.0.10 versions.
Connecting to ldap via cli (ldapsearch) works normally.
stovesy, EddieA - did you find any fix or workaround for this problem?

21
Installation and Upgrades / Re: Connecting to Zentyal 4.1 LDAP
« on: August 30, 2015, 07:47:07 pm »
Thanks, logging in via username@domain.separated.by.dots login works well on Zentyal 4.0 and 4.1! This is much better and stable that "Name Surname", I will use it. Please document this in manuals.

22
Installation and Upgrades / Re: Connecting to Zentyal 4.1 LDAP
« on: August 26, 2015, 07:05:19 pm »
Yes, the problem is that OpenLDAP and samba uses different fields for login. But using "Name Surname" for login is not so good and stable way (our company use names with Russian letters), use username will be much stable and comfortable.
Is there any option in Samba for change this behavior?

23
Installation and Upgrades / Re: Connecting to Zentyal 4.1 LDAP
« on: August 25, 2015, 01:13:48 pm »
I have create an issue about this problem: https://tracker.zentyal.org/issues/3870

24
Installation and Upgrades / Re: Zentyal 4.1 jabber/xmpp
« on: August 25, 2015, 09:22:00 am »

Thanks for the reply. This is strange that not so complex module like Jabber require much time to maintain for Zentyal developers. As I understant, it work separately from other Zentyal and linux modules. As I see, this module have only configuration page that generating config file, and "User jabber account" checkbox in User page.

Other parts of this module work separately: ejabberd server only get userlist from LDAP and generated by Zentyal config file. All other works independently.

So for update module to new version we must only track ldap query changes and Zentyal API for adding elements in interface.

I'm not good specialist in Perl, but will try to fork Zentyal git and port Jabber module for Zentyal 4.1 by myself, this is easier for our company that changing Zentyal to some other solution. If something happens with my port, I submit pull request to you.

Because removing Jabber support for Zentyal broke good way of IM communication for clients, and not provide any replacement. Let's use Facebook, Skype, Telergram, Viber for corporate talking? :) No, let's restore Jabber support, good opensource solution for corporate IM.

25
Installation and Upgrades / Re: Zentyal 4.1 jabber/xmpp
« on: August 24, 2015, 09:45:51 pm »
Maybe Jabber is available via commercial version of Zentyal?

26
Installation and Upgrades / Re: Zentyal 4.1 jabber/xmpp
« on: August 24, 2015, 08:55:50 pm »
Very bad that ejabberd Jabber XMPP server is removed from Zentyal 4.1  :-[

This is upgrade stopper for our company, so we must stay on Zentyal 4.0 version for keep corporate Jabber server working.

Can you describe why Jabber is removed from new versions of Zentyal?

And what is alternative to jabber for Instant Messaging between users?

27
Installation and Upgrades / Re: Connecting to Zentyal 4.1 LDAP
« on: August 24, 2015, 07:46:56 pm »
Many thanks, using "Name Surname" for login into Zentyal 4.1 LDAP database works well!

But I don't understand why I must connect to Zentyal 4.1 LDAP via "Name Surname" instead of one-word "username" (login) like in Zentyal 4.0 and earlier versions.
Is this Zentyal issue or this is normal to use "Name Surname" as login name for LDAP AD databases?

28
Installation and Upgrades / Re: extra Attribute in user account
« on: June 20, 2015, 05:36:56 pm »
flaxe, did you find any way how to add extra fields to Zentyal LDAP User database?

29
Installation and Upgrades / Re: More fields in LDAP
« on: June 20, 2015, 05:35:30 pm »
christian, did you find any way to show additional LDAP fields in User Edit page of Zentyal interface?
I want store room number, mobile phone and other info for user in single place too, but can't find the way how to do this.

30
Installation and Upgrades / Re: (3.5) Jabber Shared Roster
« on: December 22, 2014, 09:28:26 pm »
Same problem with shared roster on Zentyal 4.0 version. Is anybody find some solution or workaround?

Pages: 1 [2] 3