Moving Messenger and Secondary Domain

Question

I have messenger and a 2ndry Domain running on a VM that will not itself migrate to a new server. So I have created a new VM. I need to manually install Messenger on new VM and install and new secondary domain. Everything is running on CE 24.3. I have reviewed posts from in April when I posed questions about moving primary domain to a VM. Still intend to do it, but as long as hardware is doing well, I just am setting everything up as described here at blog.konecnyconsulting.ca/2024/04/moving-groupwise-system.html which is very complete. I figure if hardware begins to fail, I can quickly move backup data if not live data to new VM. 
 But back to moving Messenger and Secondary domain. Should I first delete the Messenger link and current secondary domain in Admin Console? Install Messenger as a new Messenger link with new name, and install a third domain? Then delete entries for VM which is being retired? I could assign same IP or a new one. Either is easy to do. It should be fairly easy. I saw some old posts referencing ver 18, but quite a few changes since then.

DH2 · Accepted Answer

As a final post, I decided to permit tech support to modify the database file per the TID. Doing so caused no disruption. The bad news is that the Messenger App (MA) was difficult to configure. I installed it on a fresh SLES 15.6 VM with all the features required in the 24.3 online documentation preinstalled. The pre-config install went fine. All DNS features worked fine on the MA and Admin Service (AS) machines. Nslookup worked well, and the hostname reports were correct, etc. However, the AS machine did not like the SSL certificate tendered to it by the MA. [Error communicating with resource &hellip; hostname wrong &hellip; should be ____.] I was pointed to an old TID about how to resolve the issue. It did not help, but it recommended restarting the adminservice between connecting attempts. I followed the recommendation. || Since I was using a self-signed cert on the MA, I created one with the hostname FQDN and another hostname as the IP ADDR of the MA. I tried configuring the MA with FQDN and cert with FQDN. No luck; the same error was issued at the AS. [I tried allowing weak DB certs and not allowing, and allowing weak is what I settled on using.] The only configuration that worked was configuring the MA to use the IP as the hostname, coupled with the cert configured the same. The AS liked that combo, and the errors disappeared. The good news is that the new VM MA machine is very fast now that everything is configured, and the tasks needed to import GroupWise users through the admin console worked extremely well. Since there is no intent to use the MA outside the local network, I will not substitute commercial certs. I set the certs I created to live for 10 years, so hopefully, I will not have to configure for quite some time. Thanks to all who assisted on this project.

pcajka · Answer

However, be aware of this TID: 
 portal.microfocus.com/.../KM000028441

Menu

GroupWise Discussions

Moving Messenger and Secondary Domain

Top Replies

Resources