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.
1
Installation and Upgrades / Traffic Shaping in Zentyal 5.0
« on: March 20, 2017, 02:41:25 pm »
During installation, I'm not seeing the traffic shaping module I liked so much in previous versions of Zentyal:
Can you please direct me to documentation for how I might set this up in Zentyal 5?
Can you please direct me to documentation for how I might set this up in Zentyal 5?
2
Installation and Upgrades / Can't Access Non-Zentyal Intranet from Open VPN Client
« on: February 15, 2016, 02:16:28 pm »
Through a Zentyal 4.0 gateway, I'm trying to VPN-Access an interanet site located on a Windows Server at 192.168.22.5:80
Even when the windows firewall it turned off, I cannot access ports 443 and 80 via the Open VPN client. What's weird is that I can access all other ports on 192.168.22.5. I can even RDP into this Windows sever via the OpenVPN client, but I cannot directly access the intranet that everyone else on-site can access. I've been getting around the issue by logging into a workstation that can access the intranet directly, but I'd like to figure out why I cannot access the intranet pages directly myself.
Any suggestions?
Even when the windows firewall it turned off, I cannot access ports 443 and 80 via the Open VPN client. What's weird is that I can access all other ports on 192.168.22.5. I can even RDP into this Windows sever via the OpenVPN client, but I cannot directly access the intranet that everyone else on-site can access. I've been getting around the issue by logging into a workstation that can access the intranet directly, but I'd like to figure out why I cannot access the intranet pages directly myself.
Any suggestions?
3
Installation and Upgrades / MySQL password can't be retreived like before - What now?
« on: April 13, 2015, 05:39:04 pm »
Previously, in Zentyal 4.0, I could acquire the mysql password (for the squid database) using this command:
After recent updates, it seems I've lost the ability to query the mysql squid database. I assumed, that somehow, the password got changed. And I've just noticed that the method I used (to retrieve the mysql password initially) no longer works; the path mentioned, in the command above, does not exist now.
Please advise.
Code: [Select]
echo $(sudo cat /var/lib/zentyal/conf/zentyal-mysql.passwd)After recent updates, it seems I've lost the ability to query the mysql squid database. I assumed, that somehow, the password got changed. And I've just noticed that the method I used (to retrieve the mysql password initially) no longer works; the path mentioned, in the command above, does not exist now.
Please advise.
4
Installation and Upgrades / Zentyal 3.5 Installer Hangs While Scanning "CD ROM"
« on: October 15, 2014, 06:58:34 am »
This is an Ubuntu 14.04 bug:
https://bugs.launchpad.net/debian-installer/+bug/1381321
But since Zentyal 3.5 and 4.0 are based on Ubuntu 14.04, it will effect some Zentyal admins too.
The key is to just wait. It will hang between 15 and 20 minutes and then continue.
https://bugs.launchpad.net/debian-installer/+bug/1381321
But since Zentyal 3.5 and 4.0 are based on Ubuntu 14.04, it will effect some Zentyal admins too.
The key is to just wait. It will hang between 15 and 20 minutes and then continue.
5
Installation and Upgrades / Restore Zentyal 3.3 OpenVPN Configuration to Zentyal 3.5
« on: October 10, 2014, 11:12:00 pm »
From Zentyal 3.0 to 3.3.10, version upgrades predominantly succeeded in the Community edition.
Since 3.3.10, I have not been able to succeed in upgrading to 3.4 or 3.5.
I've also attempted installing 3.5 fresh, and restoring the 3.3.10 configuration to it. This is not supported.
This particular Zentyal server is functioning as a Gateway and providing OPEN VPN. Would it be easy to back up and restore just the VPN module protion of Zentyal 3.3 to a freshly installed 3.5?
I'm trying to avoid creating new keys/cert/etc. for all clients.
Since 3.3.10, I have not been able to succeed in upgrading to 3.4 or 3.5.
I've also attempted installing 3.5 fresh, and restoring the 3.3.10 configuration to it. This is not supported.
This particular Zentyal server is functioning as a Gateway and providing OPEN VPN. Would it be easy to back up and restore just the VPN module protion of Zentyal 3.3 to a freshly installed 3.5?
I'm trying to avoid creating new keys/cert/etc. for all clients.
6
Installation and Upgrades / Additional Domain Controller not Providing Fail Over
« on: May 25, 2014, 06:23:59 pm »
I recently upgraded my two zentyal domain controllers to 3.4 from 3.3.10.
I was unable to successfully upgrade by just clicking the "Upgrade to 3.4" button. I upgraded by backing up my configuration and then installing 3.4 onto both servers and then restoring their respective configurations.
Everything works fine when the Additional Domain Controller is turned completely off. But when it is on, some people cannot login to their workstation.
Both of these servers are providing DHCP and DNS. I have two dhcp pools, one on each server.
In 3.3.10, I could turn off either one of these servers and users could function normally as long as one of them is on. With either server on, they could successfully:
1) Log into their workstations
2) Access file shares located on windows servers
3) Received a DHCP issued IP address
4) Access Internet Web Pages
In 3.4.3, if I turn off the Primary Zentyal domain controller (while leaving the additional domain controller on):
1) Some users cannot Login to their workstations, but some can oddly enough.
2) Many users who can login to their workstations cannot access all of the file shares located on windows servers on the LAN
I've confirmed however, that Active Directory replications is occurring, for example
1) If I add a user on the Primary Domain Controller, it promptly appears in the Zentyal Web Interface of the Additional Domain controller
2) If I add a user using the Additional Domain Controller, it promptly appears in the Web Interface of the Primary Domain Controller
3) Same is true when I delete users from either of these servers.
So, the additional domain controller is working to some degree, but when it is turned on it has a negative effect on some user's ability to login to their workstations and those who can have issues accessing certain windows shares.
In 3.3.10, this additional domain controller worked flawlessly as a fail over. I could turn either of my domain controllers off and users would keep accessing every thing they needed to. Since upgrading to 3.4.3, I have to turn this additional domain controller completely off to not experience access problems.
The next thing I'm going to try, is just redoing the additional domain controller from scratch (freshly joining it to the domain).
I'll report back here what that accomplishes.
To me, these services in Zentyal should be priority number one; nothing is more fundamental than having a healthy domain controller and a fail over domain controller (so that the whole LAN doesn't come to a halt if the primary goes down).
I was unable to successfully upgrade by just clicking the "Upgrade to 3.4" button. I upgraded by backing up my configuration and then installing 3.4 onto both servers and then restoring their respective configurations.
Everything works fine when the Additional Domain Controller is turned completely off. But when it is on, some people cannot login to their workstation.
Both of these servers are providing DHCP and DNS. I have two dhcp pools, one on each server.
In 3.3.10, I could turn off either one of these servers and users could function normally as long as one of them is on. With either server on, they could successfully:
1) Log into their workstations
2) Access file shares located on windows servers
3) Received a DHCP issued IP address
4) Access Internet Web Pages
In 3.4.3, if I turn off the Primary Zentyal domain controller (while leaving the additional domain controller on):
1) Some users cannot Login to their workstations, but some can oddly enough.
2) Many users who can login to their workstations cannot access all of the file shares located on windows servers on the LAN
I've confirmed however, that Active Directory replications is occurring, for example
1) If I add a user on the Primary Domain Controller, it promptly appears in the Zentyal Web Interface of the Additional Domain controller
2) If I add a user using the Additional Domain Controller, it promptly appears in the Web Interface of the Primary Domain Controller
3) Same is true when I delete users from either of these servers.
So, the additional domain controller is working to some degree, but when it is turned on it has a negative effect on some user's ability to login to their workstations and those who can have issues accessing certain windows shares.
In 3.3.10, this additional domain controller worked flawlessly as a fail over. I could turn either of my domain controllers off and users would keep accessing every thing they needed to. Since upgrading to 3.4.3, I have to turn this additional domain controller completely off to not experience access problems.
The next thing I'm going to try, is just redoing the additional domain controller from scratch (freshly joining it to the domain).
I'll report back here what that accomplishes.
To me, these services in Zentyal should be priority number one; nothing is more fundamental than having a healthy domain controller and a fail over domain controller (so that the whole LAN doesn't come to a halt if the primary goes down).
7
Installation and Upgrades / Default Domain Policy - 504 Gateway Time-out nginx
« on: May 23, 2014, 06:02:50 pm »
Go here:
Zentyal 3.4.3 Web Interface > Office > Domain > Group Policy Objects > Default Domain Policy
After a very long wait, this what I get:
504 Gateway Time-out
Sometimes, the page actually resolves. When I add a batch script, I will also get this 504 error. I did this 3 times in a row getting this error 3 times. When I finally looked again, the same batch script was added 3 times; apparently, even though nginx was timing out, it was still indeed adding the batch script each time.
Any suggestions?
Zentyal 3.4.3 Web Interface > Office > Domain > Group Policy Objects > Default Domain Policy
After a very long wait, this what I get:
504 Gateway Time-out
Sometimes, the page actually resolves. When I add a batch script, I will also get this 504 error. I did this 3 times in a row getting this error 3 times. When I finally looked again, the same batch script was added 3 times; apparently, even though nginx was timing out, it was still indeed adding the batch script each time.
Any suggestions?
8
Installation and Upgrades / Can't Ping Local computers (by name)
« on: April 24, 2014, 10:53:23 pm »
In an environment where MS Windows is the primary domain controller, I've added Zentyal 3.4 as an additional domain controller.
Also, this same server is successfully providing Jabber service for the LAN, where users are successfully consuming Jabber via Pidgin (where they are logging in successful with their Active Directory user credentials).
For testing, I've manually configured my laptop so that it only uses the Zentyal 3.4 server for DNS. Through Zentyal, my laptop is resolving the IP address of public websites just fine.
However, I can't seem to ping local machines by name, even if I include their fully qualified local domain name.
For example, I have computer named "test" at 192.168.100.5 and its fully qualified domain name would be test.company.local.
If I tried to ping just "test" I get:
If I try to ping test.company.local I get:
This Zentyal Additional Domain controller is located at 192.168.100.3. I'm able to verify that it knows where test.company.local is with this command:
This correctly returns 192.168.100.5.
But yet, if I ping "test" or test.company.local it says it is an unknown host. It's the same for any machine on the LAN. It won't even ping the Zentyal server itself by name.
Why would the dig command prove that this additional domain controller knows the ip of test.company.local, while ping doesn't resolve the host?
Shouldn't LDAP be telling DNS these local machine names and their IPs?
Also, this same server is successfully providing Jabber service for the LAN, where users are successfully consuming Jabber via Pidgin (where they are logging in successful with their Active Directory user credentials).
For testing, I've manually configured my laptop so that it only uses the Zentyal 3.4 server for DNS. Through Zentyal, my laptop is resolving the IP address of public websites just fine.
However, I can't seem to ping local machines by name, even if I include their fully qualified local domain name.
For example, I have computer named "test" at 192.168.100.5 and its fully qualified domain name would be test.company.local.
If I tried to ping just "test" I get:
Code: [Select]
ping: unknown host testIf I try to ping test.company.local I get:
Code: [Select]
ping: unknown host test.company.localThis Zentyal Additional Domain controller is located at 192.168.100.3. I'm able to verify that it knows where test.company.local is with this command:
Code: [Select]
dig @192.168.100.3 test.company.localThis correctly returns 192.168.100.5.
But yet, if I ping "test" or test.company.local it says it is an unknown host. It's the same for any machine on the LAN. It won't even ping the Zentyal server itself by name.
Why would the dig command prove that this additional domain controller knows the ip of test.company.local, while ping doesn't resolve the host?
Shouldn't LDAP be telling DNS these local machine names and their IPs?
9
Installation and Upgrades / Can't boot after upgrade to 3.4: error: file not found. grub rescue>
« on: April 20, 2014, 04:28:24 am »
I upgraded my primary domain controller from to 3.4 from 3.3.9. It may be helpful to know that this server's original install was with Zentyal 3.0 and it had upgraded successfully all the way to 3.3.9, but cannot successfully reboot after upgrading to 3.4.
The upgrade seemed successful at first; I even logged into the 3.4 Web Interface, but after rebooting the server for the first time it would not boot up.
This is as far as it get while trying to boot:
The upgrade seemed successful at first; I even logged into the 3.4 Web Interface, but after rebooting the server for the first time it would not boot up.
This is as far as it get while trying to boot:
Code: [Select]
error: file not found.
grub rescue>
10
Installation and Upgrades / Should Zentyal Have Skipped Ubuntu 13.10 Waiting for 14.04.1 ?
« on: April 17, 2014, 07:12:10 pm »
Steve Langasek Ubuntu Engineering Foundations team manager:
"Upgrades between LTS releases are not enabled by default until the first point release"
This means, that if you are on 12.04, it won't prompt you to upgrade until 14.04.1 is released. From a stability stand point, this makes a lot of sense to me.
Wouldn't it have been wiser to skip Ubuntu 13.10 altogether and instead focus on a distribution upgrade for when 14.04.1 is released?
I have several servers running Zentyal 3.3.9. I attempted to upgrade one of them to Zentyal 3.4 and the upgrade failed causing me to have to reinstall 3.3.9 onto that server.
I'm so disappointed that Zentyal showcased this "upgrade to 3.4" button before having thoroughly tested its ability to succeed. Additionally they even sent me an announcement email provoking me to go ahead and upgrade (without any warning of how risky that might be).
The only service this server was providing was an "Additional Domain Controller". At this point I'm stuck on 3.3.9, until I see proof that others are upgrading from 3.3.9 to 3.4 without issues.
"Upgrades between LTS releases are not enabled by default until the first point release"
This means, that if you are on 12.04, it won't prompt you to upgrade until 14.04.1 is released. From a stability stand point, this makes a lot of sense to me.
Wouldn't it have been wiser to skip Ubuntu 13.10 altogether and instead focus on a distribution upgrade for when 14.04.1 is released?
I have several servers running Zentyal 3.3.9. I attempted to upgrade one of them to Zentyal 3.4 and the upgrade failed causing me to have to reinstall 3.3.9 onto that server.
I'm so disappointed that Zentyal showcased this "upgrade to 3.4" button before having thoroughly tested its ability to succeed. Additionally they even sent me an announcement email provoking me to go ahead and upgrade (without any warning of how risky that might be).
The only service this server was providing was an "Additional Domain Controller". At this point I'm stuck on 3.3.9, until I see proof that others are upgrading from 3.3.9 to 3.4 without issues.
11
Installation and Upgrades / Another Upgrade from 3.3.9 to 3.4 Failure
« on: April 16, 2014, 11:50:01 pm »
The upgrade seemed to be going fine, until this:
After this failure, I had to go manually set my DNS:
Otherwise, I was no longer to do sudo apt-get update (it couldn't resolve domain name's IPs):
Now, when I do sudo apt-get update, I get:
And yes, those urls are really down; try clicking them:
Any advice on how I might complete this corrupted upgrade from the command line?
Code: [Select]
Processing triggers for zentyal-core ...
* Restarting Zentyal module: haproxy
...fail!
* Restarting Zentyal module: webadmin
...fail!
* Restarting Zentyal module: logs
...done.
* Restarting Zentyal module: events
...done.
Processing triggers for ureadahead ...
Errors were encountered while processing:
bind9
zentyal-dns
zentyal-users
zentyal-ftp
zentyal-samba
E: Sub-process /usr/bin/dpkg returned an error code (1)
Forcing pending packages installation...
Reading package lists...
Building dependency tree...
Reading state information...
The following packages were automatically installed and are no longer required:
apache2-mpm-prefork apache2.2-bin cifs-utils cpp-4.6
libapache-singleton-perl libapache2-authcookie-perl libbind9-80
libchart-perl libdconf0 libdm0 libdns81 libfm-gtk1 libfm1 libgconf2-4
libgd-gd2-perl libgd2-xpm libgrail5 libisc83 libisccc80 libisccfg82
libjs-prototype libjs-scriptaculous libkpathsea5
liblaunchpad-integration-3.0-1 liblaunchpad-integration-common libllvm3.0
liblua5.1-0 liblwres80 libmath-round-perl libmenu-cache1 libmpc2
libobrender27 libobt0 libpoppler19 libtiff4 libtommath0
linux-headers-3.5.0-26 linux-headers-3.5.0-26-generic python-apport
python-gi python-gnupginterface python-keyring python-launchpadlib
python-lazr.restfulclient python-lazr.uri python-oauth python-pkg-resources
python-problem-report python-simplejson python-wadllib python-zope.interface
samba4
Use 'apt-get autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
5 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up bind9 (2:9.9.3.dfsg.P2-4ubuntu1.1+zentyal12) ...
* Starting domain name service... bind9
...fail!
invoke-rc.d: initscript bind9, action "start" failed.
dpkg: error processing bind9 (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of zentyal-dns:
zentyal-dns depends on bind9 (>= 1:9.8.1.dfsg.P1-4ubuntu0.7+zentyal1); however:
Package bind9 is not configured yet.
dpkg: error processing zentyal-dns (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of zentyal-users:
zentyal-users depends on zentyal-dns; however:
Package zentyal-dns is not configured yet.
dpkg: error processing zentyal-users (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of zentyal-samba:
zentyal-samba depends on zentyal-users; however:
Package zentyal-users is not configured yet.
zentyal-samba depends on zentyal-dns; however:
Package zentyal-dns is not configured yet.
dpkg: error processing zentyal-samba (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of zentyal-ftp:
zentyal-ftp depends on zentyal-users; however:
Package zentyal-users is not configured yet.
dpkg: error processing zentyal-ftp (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
bind9
zentyal-dns
zentyal-users
zentyal-samba
zentyal-ftp
E: Sub-process /usr/bin/dpkg returned an error code (1)
Setting up bind9 (2:9.9.3.dfsg.P2-4ubuntu1.1+zentyal12) ...
* Starting domain name service... bind9
...fail!
invoke-rc.d: initscript bind9, action "start" failed.
dpkg: error processing bind9 (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of zentyal-dns:
zentyal-dns depends on bind9 (>= 1:9.8.1.dfsg.P1-4ubuntu0.7+zentyal1); however:
Package bind9 is not configured yet.
dpkg: error processing zentyal-dns (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of zentyal-samba:
zentyal-samba depends on zentyal-dns; however:
Package zentyal-dns is not configured yet.
dpkg: error processing zentyal-samba (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of zentyal-users:
zentyal-users depends on zentyal-dns; however:
Package zentyal-dns is not configured yet.
dpkg: error processing zentyal-users (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of zentyal-ftp:
zentyal-ftp depends on zentyal-users; however:
Package zentyal-users is not configured yet.
dpkg: error processing zentyal-ftp (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
bind9
zentyal-dns
zentyal-samba
zentyal-users
zentyal-ftp
Zentyal upgrade failed. Full log at /var/log/zentyal/upgrade.log.
After this failure, I had to go manually set my DNS:
Code: [Select]
sudo nano /etc/resolv.confOtherwise, I was no longer to do sudo apt-get update (it couldn't resolve domain name's IPs):
Now, when I do sudo apt-get update, I get:
Code: [Select]
. . .
Ign http://us.archive.ubuntu.com saucy-backports/multiverse Translation-en_US
Ign http://us.archive.ubuntu.com saucy-backports/restricted Translation-en_US
Ign http://us.archive.ubuntu.com saucy-backports/universe Translation-en_US
Fetched 1,184 kB in 9s (122 kB/s)
W: Failed to fetch http://ppa.launchpad.net/zentyal/3.4/ubuntu/dists/saucy/main/binary-amd64/Packages 404 Not Found
W: Failed to fetch http://ppa.launchpad.net/zentyal/3.4/ubuntu/dists/saucy/main/binary-i386/Packages 404 Not Found
And yes, those urls are really down; try clicking them:
- http://ppa.launchpad.net/zentyal/3.4/ubuntu/dists/saucy/main/binary-amd64/Packages
- http://ppa.launchpad.net/zentyal/3.4/ubuntu/dists/saucy/main/binary-i386/Packages
Any advice on how I might complete this corrupted upgrade from the command line?
12
Installation and Upgrades / apt-get update can't get Zentyal ppa
« on: April 16, 2014, 11:39:16 pm »
W: Failed to fetch http://ppa.launchpad.net/zentyal/3.4/ubuntu/dists/saucy/main/binary-amd64/Packages 404 Not Found
W: Failed to fetch http://ppa.launchpad.net/zentyal/3.4/ubuntu/dists/saucy/main/binary-i386/Packages 404 Not Found
Furthermore, you can see that 3.4 has been taken down:
http://ppa.launchpad.net/zentyal/
This happened to me in the middle of an upgrade!
W: Failed to fetch http://ppa.launchpad.net/zentyal/3.4/ubuntu/dists/saucy/main/binary-i386/Packages 404 Not Found
Furthermore, you can see that 3.4 has been taken down:
http://ppa.launchpad.net/zentyal/
This happened to me in the middle of an upgrade!
13
Installation and Upgrades / Which Virtual Interface's IP Uses the Backup-Gateway During WAN Failover?
« on: April 08, 2014, 12:27:19 am »
I'm using Zentyal 3.3, but the only documentation I could find, regarding WAN Failover, was for 2.2:
http://doc.zentyal.org/2.2/en/routing.html#configuring-wan-failover-in-zentyal
So, I have two internet connections, and I want the second one to only be used when the primary one is down.
Each internet connection obviously has a different set of public IP addresses.
Zentyal allows you to specify one primary IP address for your Zentyal Server and then you can add multiple other IP addresses as "virtual interfaces".
If I have these two gateways:
55.55.55.54
33.33.33.32
and if my Server's IP is 55.55.55.55 and I have the following virtual interface IPs:
55.55.55.56
55.55.55.57
55.55.55.58
33.33.33.33
33.33.33.34
33.33.33.35
If the gateway 55.55.55.54 goes down, I realize that Zentyal will start using 33.33.33.32 as the gateway. However, that's just the gateway, what would the server's IP address be (from the perspective remote machines on the internet)?
For example, when the first gateway (55.55.55.54) is being used, if a user on a workstation goes and googles "show me my ip", they will find out that their IP (from a public perspective) is 55.55.55.55?
So how does Zentyal know which IP it should use when accessing gateway2 (33.33.33.32)? There are multiple to choose from in the virtual interfaces:
33.33.33.33
33.33.33.34
33.33.33.35
and I see no way to specify this in the configuration.
So, am I overlooking something? Or, is this automatically chosen by Zentyal? If so, what criteria is used to choose this?
http://doc.zentyal.org/2.2/en/routing.html#configuring-wan-failover-in-zentyal
So, I have two internet connections, and I want the second one to only be used when the primary one is down.
Each internet connection obviously has a different set of public IP addresses.
Zentyal allows you to specify one primary IP address for your Zentyal Server and then you can add multiple other IP addresses as "virtual interfaces".
If I have these two gateways:
55.55.55.54
33.33.33.32
and if my Server's IP is 55.55.55.55 and I have the following virtual interface IPs:
55.55.55.56
55.55.55.57
55.55.55.58
33.33.33.33
33.33.33.34
33.33.33.35
If the gateway 55.55.55.54 goes down, I realize that Zentyal will start using 33.33.33.32 as the gateway. However, that's just the gateway, what would the server's IP address be (from the perspective remote machines on the internet)?
For example, when the first gateway (55.55.55.54) is being used, if a user on a workstation goes and googles "show me my ip", they will find out that their IP (from a public perspective) is 55.55.55.55?
So how does Zentyal know which IP it should use when accessing gateway2 (33.33.33.32)? There are multiple to choose from in the virtual interfaces:
33.33.33.33
33.33.33.34
33.33.33.35
and I see no way to specify this in the configuration.
So, am I overlooking something? Or, is this automatically chosen by Zentyal? If so, what criteria is used to choose this?
14
Installation and Upgrades / Avoid 2012 Server Essentials
« on: April 03, 2014, 06:08:41 pm »
I just wanted to share that "2012 Server Essentials" requires that itself to be the FSMO domain controller. So you can't join it to a Zentyal domain very long without it automatically shutting itself down:
http://neartalk.com/ss/2014-04-03_001_1866x987.jpg
However, this isn't Zentyal's fault. The same is true if you were to join it to an existing Windows domain. This is edition is extremely restricted (decidedly). These are types of reasons I use Linux for everything I can. You don't run into many things that do not work due to arbitrarily decided restrictions.
I don't think this is true for "2012 Server", but you'll certainly want to avoid the "Essentials" edition of server 2012.
http://neartalk.com/ss/2014-04-03_001_1866x987.jpg
However, this isn't Zentyal's fault. The same is true if you were to join it to an existing Windows domain. This is edition is extremely restricted (decidedly). These are types of reasons I use Linux for everything I can. You don't run into many things that do not work due to arbitrarily decided restrictions.
I don't think this is true for "2012 Server", but you'll certainly want to avoid the "Essentials" edition of server 2012.
15
Installation and Upgrades / Must Zentyal be an additional domain controller for Jabber to run?
« on: March 20, 2014, 06:41:35 pm »
When I try to start the Jabber module, I get this error:
Does this mean that the Zentyal server, that Jabber is running on, must be an "additional domain controller"?
Right now, I've got the server set to use an external Windows Active Directory. I thought this would be enough for Jabber to authenticate domain users. It appears I'm wrong about that. Any advise?
Code: [Select]
Failed to enable: Module Jabber is uncompatible with the
current users operation mode (Use external Active Directory server)Does this mean that the Zentyal server, that Jabber is running on, must be an "additional domain controller"?
Right now, I've got the server set to use an external Windows Active Directory. I thought this would be enough for Jabber to authenticate domain users. It appears I'm wrong about that. Any advise?