Yes, it is. However you can upgrade your GW2014 to 24.4 staying on sles12 (but sp5). Then let it work.

After successful tests you can move your DOM&PO to the new environment (sles15sp5 or sp6).

Be prepared to check your certificates in /opt/novell/groupwise/certificates/<long string>. Start to check ca.crt. It should be SHA256, old systems are on SHA1 in most cases. In case of SHA1 you have to renew it. Nevertheless I assume you have to renew then all, ca, admin.* and more.

There are some TIDs how to do ...

So my message is "don't do to much in one step".

• Upgrade and move then or
• move to the new server staying on GW2014 and upgrade afterwards.

There is a way to migrate from GW14 to GW 24.x. There is a cookbook that describes this. It is not yet finished in English, but is partly available in German.

The most important thing is the first step, change certificates and everything in the configuration of GW 2014 from IP to FQDN. If GWLdap is already present in 2014, e.g. to cover Messenger, it is essential to ensure that the certificate is available as a pem for GWLDAP

Then Ditmar also wrote a top important info regarding SHA256

First check the internal CA with openssl. If there is an IP in the CN, create a new CA for the system and make sure that the server name is the FQDN in the CN.

This is actually just a bit of hard work. Internal CA on FQDN, entries in the configurations of agents GWIA etc on fqdn. Maybe take the change and switch to commercial certificates for (also wildcard).

For the migration from 14 to 24.4 you can use the topic “Move GroupWise system to another server ( KM000012666 ). If you want to proceed very carefully, migrate step by step from 14 to 24.4 including GW Web and then move.
I have already jumped from 2014 to 2018 and then directly to 2024 a few times, in one case I had to skip the step via 2018, but this is also not really recommended.

George

There is a way to migrate from GW14 to GW 24.x. There is a cookbook that describes this. It is not yet finished in English, but is partly available in German.

The most important thing is the first step, change certificates and everything in the configuration of GW 2014 from IP to FQDN. If GWLdap is already present in 2014, e.g. to cover Messenger, it is essential to ensure that the certificate is available as a pem for GWLDAP

Then Ditmar also wrote a top important info regarding SHA256

First check the internal CA with openssl. If there is an IP in the CN, create a new CA for the system and make sure that the server name is the FQDN in the CN.

This is actually just a bit of hard work. Internal CA on FQDN, entries in the configurations of agents GWIA etc on fqdn. Maybe take the change and switch to commercial certificates for (also wildcard).

For the migration from 14 to 24.4 you can use the topic “Move GroupWise system to another server ( KM000012666 ). If you want to proceed very carefully, migrate step by step from 14 to 24.4 including GW Web and then move.
I have already jumped from 2014 to 2018 and then directly to 2024 a few times, in one case I had to skip the step via 2018, but this is also not really recommended.

George