one week later (and without any complaint about anyone who could probably have sthg to do with anything), again a simple question: are we getting nearer to a solution (pls remark that there is no attack to someone, it is just another try to get some infomation)?
I have installed a test environment with UCS5. Master and Node. I have installed and activated the test app centre on the node. When I try to install Kopano-Core, I get the message that I need an activation key. Where can I get this?
eagerly awaiting a version for UCS5 that isnāt in the test app center⦠so I had a thought and a question for any UCS experts here.
I currently have a 3 node UCS5 system updated to the most current errata. I really want to get Kopano working again and finally shut down my super old existing MTA.
Option #1: Can anyone see a problem adding one more node at 4.4-8 dedicated for Kopano and upgrade to 5 when it becomes available?
Option #2: Add an additional node dedicated for Kopano and enable the test repo on that one only. but if I do enable the test repo does that enable it for all UCS servers in the domain?
Kopano appears to install software on all UCS nodes in the domain so maybe neither of these options are viable?
I think that both options will fail at the same point: installing master packages on the primary and backup systems. So you would need to enable the test app center for that on all primary and backup systems. Which you stated you donāt want, so I donāt see any possible path for you at this point.
Thanks Christian, did you finish your test with MSH Disclaimer and Signature?
Is it a good working alternative?
I need to uninstall Bitbone Maildisclaimer in order to install UCS 5 and I need a positive feedback about MSH Disclaimer and Signature.
Thanks.
Had some time free for testing againā¦
Enabled dev-test-center on Primary (5.0) and designated mailserver (4.4), install of kopano-core 8.7.24.0-1 seemed to work.
BUT joinscript 70kopano4ucs-udm.inst fails with
Waiting for activation of the extension object kopano4ucs: .......................................................ERROR: Master did not mark the extension object active within 180 seconds.
ERROR
ucs_registerLDAPExtension: registraton of /usr/share/kopano4ucs/admin/syntax/kopano4ucs.py failed.
Enabled dev-test-center on Primary (5.0.1) and designated mailserver (5.0.1) install from gui fails with error āThis is the Primary Directory Node. Cannot continue!ā
Log says:
2212 actions.install 22-03-30 10:33:42 [ INFO]: Installing some packages of kopano-core on primary.mydomain.com
2212 actions.install 22-03-30 10:33:42 [CRITICAL]: This is the Primary Directory Node. Cannot continue!
WORKED without any apparent errors that I could detect. Users can take kopano-roles, Webapp loads fine. Canāt test z-push in my closed testing environment though.
NOTE: the installer of kopano-core asked me for password of root@primary.mydomain.com and later for Administrator@mydomain.com⦠very strange. But maybe that is related to the gui install not working⦠Maybe someone can continue work from the info I have provided.
Regarding Kopano, would it make sense to invest the time needed and migrate to a standalone server (e.g. Ubuntu) and connect to Univention āonlyā via OpenLDAP?
For a small number of users it might be worth thinking of. Authentication should work, but user management has to be done on kopano side as wellā¦
(I have chosen Ubuntu as an example, as Kopano can be installed directly via apt, so i expect that most things should work out of the box.)
Last week i phoned with Kopano. The packages are ready for over 8 weeks. And they are waiting for a bugfix from UCS. It is about the new naming of the servers.
Please be assured that work on the Kopano Apps is ongoing on both sides, Kopano and Univention, and took also place within the mentioned 8 weeks. There are regular updates of the App in the UCS Test App Center. Currently there are still issues with the upgrade from UCS 4.4 to UCS 5.0, so please be patient.