I suggest to copy certificates too. Then it will be less work!

(/opt/novell/groupwise/certificates).

However you can start before. Create a new sles with temporary ip. Copy all the stuff you want (I prefer rsync). Clean up the original server from DS. Stop GW there, do a final rsync. Change ip addresses on both servers ... and so on.

OK. Noted, but it is not that big a deal to do it all during a weekend. Also note that I run the GW database on NSS, not plain Sles. I'd like to keep it on NSS, unless there is a compelling reason not to.

Rsync does not care. 

Usually I copy more. /etc/opt/novell/groupwise, /var/log/novell/groupwise, /var/opt/novell/groupwise and the whole /optnovell/groupwise.

Despite of copying /opt/novell/groupwise you have to install GW software. use "rpm -qa | grep group" to check which parts you have to install.

Thanks! I have noted those and will copy. As for installing, al my upgrades hav been done with the regular install program.

There is another trick that can be used if only GroupWise has been installed on the source OES and OES does not offer any other services.

Stop GroupWise, than ndsconfig rm on Souce Server . Clean Source Server Objects in NDS. Install the new OES server same name, same ip as usual in the eDir with the necessary services  Install GroupWise, do not make any configuration. Copy the source NSS vmdk form Source Server into Target OES Server VMWare Dir.

Integrate the copied VMDK in the target OES (Attention, this only works in the VCenter Client or in the VM Browser depending on the vmware version). Use NSSMU to search for NSS volumes and integrate them into the target machine. Adjust the rights for NSS GroupWise and configure / Upgrade  GroupWise.

Just done at the weekend because a GroupWise and SLES SP5 --> SP6 update caused Java errors. It was just a plain SLES. By the way, I can advise you to go from OES to plain SLES, there is less stress

George

Unfortunately does this server also host other stuff. So I will start by bringing the server up to 2024, then move over GW files (2018), then upgrade

At this point, the question of migrating GroupWise from OES to SLES really arises. Of course, an additional IP can be run on the OES for GroupWise to avoid port collisions between UMC and GWWeb and agents. From the experience of past migrations from OES versions to newer ones, the separation is really the better way. I have also moved some systems here. A very safe way for the move is actually to set up a SLES next to the OES and set up a secondary domain on the SLES, move the users and then move them piece by piece for the GWIA, agents, then later swap the secondary domain with the primary domain and then dismantle the secondary domain on OES. Before that, recreate and distribute all the certificates for GroupWise after the domain switch.
 The advantage is that almost everything goes online. There are also hints in the forum on how to move users or POs with dbcopy. Please be careful, SUES will move the repos in the next few days, so it can rumble a bit.

George

I will keep what you say in mind, but for now I will embark on the familiar path :)

I wrote up some migration guidance for this earlier this year that may help you.  Something I need to add to our main GW resources page set.

Thanks! I will have a look